Timeout error o wsa error: 183
Andre Boudreault
We are experiencing a strange situation. When certain
computers try to access our FTP server we get the
following error in our FTP logs:
02/26/04 12:46:46 714 [J:] 150 Opening ASCII mode data
connection for /bin/ls.
02/26/04 12:46:51 714 [J:] Timeout waiting for data
connection
02/26/04 12:46:51 714 [J:] Winsock Error: 0
02/26/04 12:46:51 714 [J:] WSA Error: 183
02/26/04 12:46:51 714 [J:] Timeout waiting for data
connection
We have researched the problem and I have found the
following document that relates in part to the problem
that we are experiencing.
See link:
http://www.angelfire.com/space/netcensus/tcpping.html
We have had this problem only under our W2k server. Our
Unix servers do not have this problem. Is this a W2k
issue and if so has it been addressed in W2003.
Thank you in advance for any help
Bernard
server, have you try ftp.exe command line utility to connect locally at the
server ? login, do a dir listing ? any problems ?
--
Regards,
Bernard Cheah
http://support.microsoft.com/
Please respond to newsgroups only ...
"Andre Boudreault" <aboud...@guillevin.com> wrote in message
news:9b4901c40604$310ba8a0$a501...@phx.gbl...
Paul Lynch
There's a firewall between the clients and the IIS server.
Regards,
Paul Lynch
MCSE
Andre Boudreault
We have 80 locations accessing the FTP server. Only 8 of these are
experiencing the problem. Therefore I do not believe that it is a
firewall issue. I have found a similar issue on the newsgroup. The dir
or ls command hangs. We have applied the solution that was proposed in
article 283679 without any success. An example of the port on which it
hangs would be:
03/08/04 07:13:09 55C [H:] NT Platform
03/08/04 07:13:09 55C [H:] Version 6.0 (build 715)
03/08/04 07:13:09 55C [H:] Connecting to 216.226.49.170 ...
03/08/04 07:13:10 55C [H:] 220 GICFTP01 Microsoft FTP Service (Version
5.0).
03/08/04 07:13:10 55C [H:] USER edixchg
03/08/04 07:13:10 55C [H:] 331 Password required for edixchg.
03/08/04 07:13:10 55C [H:] PASS *******
03/08/04 07:13:10 55C [H:] 230 User edixchg logged in.
03/08/04 07:13:10 55C [H:] PWD
03/08/04 07:13:10 55C [H:] 257 "/" is current directory.
03/08/04 07:13:10 55C [H:] Root Dir /
03/08/04 07:13:10 55C [H:] File Transfer: Default Mode: BINARY
03/08/04 07:13:10 55C [H:] Connected to 216.226.49.170
03/08/04 07:13:11 55C [H:] CWD /
03/08/04 07:13:11 55C [H:] 250 CWD command successful.
03/08/04 07:13:11 55C [H:] PWD
03/08/04 07:13:11 55C [H:] 257 "/" is current directory.
03/08/04 07:13:11 55C [H:] TYPE A
03/08/04 07:13:12 55C [H:] 200 Type set to A.
03/08/04 07:13:12 55C [H:] PASV
03/08/04 07:13:13 55C [H:] 227 Entering Passive Mode
(216,226,49,170,12,86).
03/08/04 07:13:13 55C [H:] Connect PASV to 216.226.49.170 12,86
03/08/04 07:13:34 55C [H:] Winsock Error: 0
03/08/04 07:13:34 55C [H:] WSA Error: 183
03/08/04 07:13:34 55C [H:] Can't connect to PASV address
Any help would be appreciated.
Thank you
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Andre Boudreault
Thank you for your response. The dir ls command seems to hang. We have
applied the registry change as indicated in article 283679 and no change
was noticed. We have 80 locations accessing the FTP server and only 8
of them are experiencing the problem. Therefore we do not believe that
it is a firewall issue. Here is a latest example of the log.
Thank you in advance for any help.
Paul Lynch
Can you get access to the firewall logs and check if any packets are
being dropped either to or from the 8 location's source IP addresses ?
I think you'll find that they are.
What ports are you actually allowing through your firewall ?
My 'guess' is that the 8 locations are the only ones attempting a
passive (PASV) connection and that the rest are all using active
(PORT) mode.
You don't say what resolution you've implemented from the KB article
you referenced but I'm assuming its this :
http://support.microsoft.com/default.aspx?scid=kb;EN-US;196271
But that only changes the behaviour of your IIS server - if there is a
firewall which is not allowing those ports through then any changes to
your IIS server will be irrelevant.
My suggestion is that you speak to the person who manages the firewall
and ask them to scan the logs for you.
Regards,
Paul Lynch
MCSE
Bernard
such traffic is block at your side or client ftp site. review any firewall
policies or router access list.
--
Regards,
Bernard Cheah
http://support.microsoft.com/
Please respond to newsgroups only ...
"Andre Boudreault" <aboud...@guillevin.com> wrote in message
news:eo6GhOqB...@tk2msftngp13.phx.gbl...