Running a Print Working Directory command from melsys3 (at Southbank) to nursys1 (at Nurioopta)
melsys3 /root #
melsys3 /root #
melsys3 /root # remsh nursys1 -n "pwd" ß 1st attempt of a pwd command was successful
/
melsys3 /root # remsh nursys1 -n "pwd" ß 2nd attempt of a pwd command failed
remshd: connect: Connection timed out
melsys3 /root #
Running a Date command from melsys3 to nursys2 (also at Nurioopta)
melsys3 /root # remsh nursys2 -n "date" ß 1st attempt of a date command was successful
Thu Aug 27 13:02:53 CST 2009
melsys3 /root # remsh nursys2 -n "date" ß 2nd attempt of a date command failed
remshd: connect: Connection timed out
melsys3 /root #
If the commands are executed consecutively, the second one times out.
If you wait for more than 5 seconds or so between commands, they both work.
The Head office has a pair of WAE-7341 and the remote office has a WAE-674.
The customer is using Unix Remote Shell command from a Unix Server in the Head Office to another Unix System in the remote office.
CAn someone point to some links where I can start to learn to troubleshoot these kind of problems and what to look for.
The WAEs are not inline. They use WCCP 61 and 62 at Head office and Remote office.
As a work-around customer has setup an ACL on the routers to bypass the WAEs for Unix Pemote Shell TCP Port Number 514, so that this traffic never hits the WAEs.
