J
Jay Chan
We have been able to FTP from a Windows-2000 server to a SCO server
for at least a year. Today, it stops working for no apparent reason.
When I use the following command in command line, it will fail:
ftp <IP-address-of-the-SCO-Server>
It says:
Connected to <IP-address-of-the-SCO-Server>
... one minute of hanging ...
Connection closed by remote host.
How can I get this to start working again?
The following information may be useful for solving this problem:
- I can use other Windows-2000 servers to FTP to that SCO server.
I just cannot FTP from that particular Windows-2000 server to that
SCO server.
- I can use that particular Windows-2000 server to FTP to other
Windows-2000 servers and a Sun Solaris Unix server. I just cannot
FTP from that Windows-2000 server to all SCO servers in our
company.
- Seem like the combination of that particular Windows-2000 and SCO
server suddenly starts failing (even though this combination has
worked for at least a year).
- Both the Windows-2000 server and the SCO server are in the same
sub-net.
- There is another SCO server that is in a different sub-net. The
Windows-2000 server cannot FTP to that SCO server either.
- According to the Services files in both
C:\WinNT\System32\Drivers\Etc\
and in /etc/services file in SCO, the data-port and control-port
for
FTP are 20 and 21 respectively. I believe these are standard
configuration.
- I thought FTP may be waiting for me to enter something when it
shows
the message "Connected <IP-address-of-the-SCO-Server>". But this
is
not the case. Whatever that I entered would be dumped back to
command
prompt.
- That Windows-2000 server doesn't have "FTP Publishing Service"
installed. I believe this is OK, right?
- That Windows-2000 server doesn't have "Internet Service Manager"
installed. I believe this is OK, right?
- I have asked many people who have access to the Windows-2000
server
and the SCO server. They all say that they haven't changed
anything
on those servers.
- I have rebooted both servers. But that doesn't help.
Thanks in advance for any information on this problem.
Jay Chan
for at least a year. Today, it stops working for no apparent reason.
When I use the following command in command line, it will fail:
ftp <IP-address-of-the-SCO-Server>
It says:
Connected to <IP-address-of-the-SCO-Server>
... one minute of hanging ...
Connection closed by remote host.
How can I get this to start working again?
The following information may be useful for solving this problem:
- I can use other Windows-2000 servers to FTP to that SCO server.
I just cannot FTP from that particular Windows-2000 server to that
SCO server.
- I can use that particular Windows-2000 server to FTP to other
Windows-2000 servers and a Sun Solaris Unix server. I just cannot
FTP from that Windows-2000 server to all SCO servers in our
company.
- Seem like the combination of that particular Windows-2000 and SCO
server suddenly starts failing (even though this combination has
worked for at least a year).
- Both the Windows-2000 server and the SCO server are in the same
sub-net.
- There is another SCO server that is in a different sub-net. The
Windows-2000 server cannot FTP to that SCO server either.
- According to the Services files in both
C:\WinNT\System32\Drivers\Etc\
and in /etc/services file in SCO, the data-port and control-port
for
FTP are 20 and 21 respectively. I believe these are standard
configuration.
- I thought FTP may be waiting for me to enter something when it
shows
the message "Connected <IP-address-of-the-SCO-Server>". But this
is
not the case. Whatever that I entered would be dumped back to
command
prompt.
- That Windows-2000 server doesn't have "FTP Publishing Service"
installed. I believe this is OK, right?
- That Windows-2000 server doesn't have "Internet Service Manager"
installed. I believe this is OK, right?
- I have asked many people who have access to the Windows-2000
server
and the SCO server. They all say that they haven't changed
anything
on those servers.
- I have rebooted both servers. But that doesn't help.
Thanks in advance for any information on this problem.
Jay Chan