Slow login using telnet on Windows terminal

[edmb]

New installation SCO Unix 5.0.5. Unix machine is one line on hub managed by Windows 2000 box. Want to log in to Unix box from other Windows computers on network (no internet). When telnet invoked from Windows box, cursor blinks for about 75 seconds before login prompt is displayed. /etc/hosts has IP for computer hub is hooked to.
Internet Configuration on Unix box lists same IP. Unix box not selected as Gateway. Why not instantaneous login response? Ping and tracert from Windows box is immediate.

 

[Annihilannic]

If you do an nslookup 1.2.3.4 from the UNIX box, where 1.2.3.4 is the IP address of the Windows client, does it respond immediately? Annihilannic.

 

[edmb]

Response for annilihannic:
Tried nslookup. After 75 seconds received "can't find 172.16.103.1:No response from server."
More info: unix box and windows 2000 box have same domain name. Windows server box set up as 172.16.10.2. In windows server box (to which hub is connected) "default gateway 172.16.10.1".Get above error using either IP. Windows boxes hooked to hub are "dynamic IP aasignment"./etc/hosts entry is 172.16.10.30 (IP of unix box).
Thanks: edmb

 

[Annihilannic]

172.16.103.1 doesn't sound like it's on your network (since everything else is 172.16.10.x). Do you have a typo in your DNS configuration (check /etc/resolv.conf, or an incorrect default route perhaps?

Anyway, you need to figure out why your DNS server is taking so long to respond, or not respond as seems to be the case. Even it responds with "can't find address" straight away that would be better because the login time would be much quicker. Annihilannic.

 

[edmb]

For annihilanic. 103.1 was typo. Should have been 10.1.
Used your clue and used IP of server (not gateway) in resolv.conf. Log in is immediate. Pings work both ways.
Thanks!