Connecting to NETServer A from NETServer B
When a user on LAN2 tries to connect with a host on LAN1, NETServerB dials NETServerA and establishes a
After the initial connection, traffic will flow freely and any user on either network can use the connection to telnet, ftp, and so on back and forth. If there is no activity on the connection for 30 minutes, NETServerB hangs up.
If the destination is set to 255.255.255.255 for PPP connections, the NETServer will try to negotiate the local IP Address. If set to 0.0.0.0, the port will be disabled for PPP connections.
What If I Don’t Want to Use CHAP Authentication?
If you don’t want to go to the trouble of creating the extra user table entry, using the same passwords for both systems and using the NETServer’s Sysname as its User Name, you can have it log in to the remote system as a regular network user by adding a few lines to the dial script. In the example above, you could have added the following lines to NETServer B’s dial script configuration rather than adding a User Table entry for NETServer A.
set location nsa script 2 “\r” “Login:”
(Line 2 - Send a carriage return and wait for “Login:”)
set location nsa script 3 “nsa\r” “Password:”
(Line 3 - Reply to Login Prompt and wait for “Password:”)
set location nsa script 4 “xyzabc\r” (Line 4 - Reply to password prompt)
