Telnet/Termlite IP Range Problems

[Guest_imported]

I cannot obtain a login on my sco server using telnet/Termlite when using some IP address ranges.

Static address set on PC then added to /etc/host file on server. Some IP's will allow login and some will not.

Anyone had this problem? Can you help.

pete.

 

[abovebrd]

I have seen a simular problem in that past. I was never able to pin point the problem. It was apperant that it was some sort of local resloution problem.

The work around that I came up with was to edit this file on the client computer (win9x)
c:\windows\hosts

#102.54.94.97 rhino.acme.com # source server
#138.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
192.168.30.1 mysever


So now instead of telneting to 192.168.30.1 I would simply use the name "myserver"

telnet myserver

This is a work around for this type of problem. In my case I only experienced this problem when using a specific model of IBM thinkpad laptops when using TinyTerm.




-Danny

 

[stanhubble]

check your netmask on the server, which should be 255.255.0.0 for the class b address range you are using.

since you are not using dns then the server should be listed in each clients hosts file.

can you ping myserver from each of the clients?
can you ping each of the clients from the server?

make sure ping will work in both directions first then see if the telnet problem still exists.