-
Posted to
Publishing
by
imprezacs
on
01-10-2009, 6:02 AM
I did netstat -an (so it didn't resolve addresses) and there was no listener on the specified port, until I turned off the firewall. That is the problem as I now see it. With the firewall on the listener fails to start.
-
Posted to
Publishing
by
imprezacs
on
01-09-2009, 4:52 AM
I have now found the reason, but still need a solution!!
The server has Windows Firewall enabled, but with the FTP Server allowed access using the Advanced Firewall Settings and allowing FTP server through. When I turn off the firewall, the FTP server behaves normally. I have tried changing the IP address of the listening server as defined in the ...
-
Posted to
Publishing
by
imprezacs
on
01-09-2009, 4:35 AM
This is getting more bizarre. I see what you are asking so have done some tests.
When I make the initial FTP connection the netstat looks like this
TCP 127.0.0.1:1034 217.*.103.170:39515 ESTABLISHED
TCP ...
-
Posted to
Publishing
by
imprezacs
on
01-09-2009, 3:35 AM
No, netstat just shows the 213 address as listening on port 21.
I'm obviously not the only one who is baffled then!
-
Posted to
Publishing
by
imprezacs
on
01-08-2009, 3:34 AM
Here is a segment from the log file after enabling server ip logging:
#Fields: time c-ip s-ip cs-method cs-uri-stem sc-status sc-win32-status
08:28:46 82.34.95.232 213.*.*.220 [421]USER XXX 331 0
08:28:48 82.34.95.232 213.*.*.220 [421]PASS - 230 0
08:28:52 82.34.95.232 213.*.*.220 [421]QUIT - 226 0
entered passive mode here...
08:32:01 ...
-
Posted to
Publishing
by
imprezacs
on
01-07-2009, 3:35 AM
We are using IIS 6 on Windows 2003 Server. This is a transcript of an FTP session which shows the session connects to the 213 address OK, but as soon as I switch to passive mode, the 94 address opens the session. This doesn't get back to a client behind a firewall.
C:\>ftp 213.***.***.220
Connected to 213.***.***.220.
220-Microsoft FTP ...
-
Posted to
Publishing
by
imprezacs
on
01-06-2009, 12:51 PM
I have a server with 5 IP addresses and have FTP binding to one of them. This all works fine except when a user connects using passive FTP. The server sends a passive connection from the server's default IP address rather than the FTP address, so it doesn't get through the client firewall.
How can I change the default address used for ...