I have several mainframes in the midwest currently able to connect to an outside ip xxx.xx.xxx.xxx and get a login prompt.
# ftp -n xxx.xx.xxx.xxx
Connected to xxx.xx.xxx.xxx
220-
220-
220 FTP server (Version wu-2.4.1(SecurID cert patch)) ready.
Remote system type is UNIX.
However, I have several mainframes on the pacific coast that cannot connect to the same ip address xxx.xx.xxx.xxx and do not get the login prompt or it just hangs with no response at all.
# ftp -n xxx.xx.xxx.xxx
Connected to xxx.xx.xxx.xxx.
421 Service not available, remote server has closed connection
ftp>
The /etc/hosts file is exactly the same along with all configuration files. The systems on the pacific coast have been allowed access through the firewall to this specific ip. Is there a way to do some kind of "tracert" from this Unix box to the outside IP to see where it's hanging up at? Any suggestions on isolating this problem would be helpful.
Thanks in advance.
# ftp -n xxx.xx.xxx.xxx
Connected to xxx.xx.xxx.xxx
220-
220-
220 FTP server (Version wu-2.4.1(SecurID cert patch)) ready.
Remote system type is UNIX.
However, I have several mainframes on the pacific coast that cannot connect to the same ip address xxx.xx.xxx.xxx and do not get the login prompt or it just hangs with no response at all.
# ftp -n xxx.xx.xxx.xxx
Connected to xxx.xx.xxx.xxx.
421 Service not available, remote server has closed connection
ftp>
The /etc/hosts file is exactly the same along with all configuration files. The systems on the pacific coast have been allowed access through the firewall to this specific ip. Is there a way to do some kind of "tracert" from this Unix box to the outside IP to see where it's hanging up at? Any suggestions on isolating this problem would be helpful.
Thanks in advance.