A
good cure to solve these DCC problems is to start with
this:
1) Disconnect from
your IRC server.
2) Clear the current
text in the Local Host and IP Address boxes under
File/Setup in the Local_Info dialog.
3) Select both 'On
connect, Always get' Local Host and IP Address options
in the Local_Info dialog.
4) Set 'Method' to
Normal.
5) Leave the
Local_Info dialog and the File/Setup menu both with
'OK'.
6) Reconnect to your
IRC server.
If
this doesn't work experiment with the 'On connect' ..
settings... !! i.e.. For instance, try to set
your Local Host address by hand and let mIRC look for
only the IP Address on each startup. If you still cant
get it to work try to use the 'Server' method instead
of the default Normal one. Eventually clear the Local
Host and IP Address fields first. Then set 'On
connect, always get Local Host and IP Address' to
active and select the 'Server' method. Now re-try to
connect... In the rare occasions even this
method doesn't help you could uncheck "On
connect, always get IP Address and Local Host"
and manually enter your PC's Local Host name and IP
number. If you are using TIA, Twinsock, SLiRP, etc.,
simply enter _your provider's_ local host name and IP,
not your own. (Your provider's IP is not
192.0.2.1 or anything like that! That's a dummy IP
used by these emulators. If you don't know your
provider's local host name and IP, ask them!)
The only known situation where the RECEIVING party
causes a DCC File transfer to fail is when the
receiver did not (properly) set the 'Default get
directory' in the DCC/Options menu under "DCC Get
directories". Make sure to set it to an existing
directory :-)
NOW
FOR SOME OTHER IDEAS .......
*** Everybody... Check
your time-out settings!
Make sure that your time-out values in DCC/Options are
set large enough!! "Get/Chat Dialog time
out after" and "Send/Get Transfer time out
after" are recommended to be set to at least 60
and 120, respectively.
In case you never ever managed to get sending files or
initiating a DCC Chat to work, not even after studying
all these hints, it might be that your provider blocks
these DCC connections by the kind of internet access
they give you. Known to give problems are TIA,
Twinsock, Slipknot and SLiRP. Also the use of a
firewall by your provider will block DCC connections.
*** If you use TIA or
Twinsock or Slipknot ...
If you use TIA (The Internet Adapter) or Twinsock, at
this point you cannot use DCC send or initiate DCC
chat (with any IRC client, not just mIRC). You
may want to try SLiRP or vTCP. SLIRP was the first
SLIP emulator to allow DCC sending and initiating DCC
chat. (As you know DCC get should always work
fine, whatever connection you have. Besides firewall
blocking you that is.) Virtual TCP is tested and
proofed to allow DCC sending and chatting. More info
http://blitzen.canberra.edu.au/slirp and http://www.infoexpress.com/vtcp.html
*** If you use SLiRP ...
With SLiRP (http://blitzen.canberra.edu.au/slirp) set
File/Setup/Local_Info/ 'always get local
host' on connect to Active, IP Address
should be the fake IP used for SLiRP (10.0.2.15
usually). Then DCC Send, Chat, and everything else
should work perfectly fine, even on
Windows95 with the Dial-Up Networking. (thanks
Dave!)
*** If you have Dynamic
IP...
If you have dynamic IP (your IP address is different
each time you log on), make sure that "On
connect, always get:" in the File/Setup/Local_Info
dialog is set to get the Local Host and IP Address. If
these were already set to ON make sure the correct
'local host' name and 'IP Address' are found by mIRC...
on some winsocks this is rather tricky... If you
have a non- compliant stack, mIRC may not be able to
correctly find your local host (domain name) and IP.
With dynamic IP addressing you are in trouble then !!
But, did you try the 'Server' method already? That
should help. DCC file sending and initiating a DCC
Chat (contrary to file getting and accepting a DCC
Chat) requires that mIRC knows your correct IP number.
Even without an IP number at all, mIRC will work as
far as normal chatting is concerned, but won't allow
DCC file sending or initiating a DCC Chat.
***
If you have Static IP...
If you have a non-compliant stack, mIRC may not be
able to correctly find your local host (domain name)
and IP. In the File/Setup/Local_Info dialog,
uncheck the options to "Always get the 'Local
Host' and 'IP Address" and manually enter your
correct Local Host and IP.
*** A known Windows95 bug
causes some people to report that mIRC (and any other
IRC program) gets/finds the old (now wrong) Local Host
name and/or IP Address after switching Internet
provider. This can block your capability to DCC Send
files and Initiating DCC Chats. If, for some reason,
no matter what you do, mIRC picks the user ID (Local
Host name) from the Internet Service Provider that you
no longer wish to use this is fixable by either
editing the registry or using the 'Server' lookup
method. If using the 'Server' method doesn't help
open Regedit and look at MyComputer \HKEY_LOCAL_MACHINE
\System \CurrentControlSet \Services \VxD \MSTCP. You
will most likely see the Domain and NameServer fields
from your old provider. These fields will persist even
if you uninstall Dial- Up Networking and re-install
and go through the TCP/IP settings again ! The best
way to solve the described problem is going to
Start/Settings/Control_Panel/Network/ double click
on TCPIP/ select DNS_Configuration/ and set the HOST
field to the hostname (ID) you have on your new
provider.
***
If you use Windows95 mIRC allows
you to send long file names with spaces in them, but
other IRC programs very often cant handle this. This
might cause your transfers to fail. You might want to
select mIRC's option to fill (up) spaces in such a
long file name by an underscore.
*** Some people experience
DCC File Send problems with mIRC on a windows system
with Norton Desktop installed. mIRC then suddenly
shuts down completely (sometimes with an error
message) as soon as you try to select a file to send.
The problem is that Norton Desktop's feature called
'File Assist' conflicts with mIRC's DCC Send dialog.
If you shut off File Assist entirely it will allow DCC
transfers fine. Even just disabling the "3D look
and feel" in the File Assist options menu helps
already.
*** Another program known
to give DCC Send problems is a software package called
Long File Names by View software. It is something you
might be running in the background and you might never
think of it as the cause of your troubles. The problem
is that when you use the DCC Send option in mIRC, the
dialog that pops-up doesn't allow you to select files
so you can't send anything. Selecting files is blocked
by LFN and if you disable the LFN software all your
DCC problems will be solved.
Original
source: mIRC FAQ
Edited by: Aditya @ DALnet
Special
Thanks to DALnet Network
|
