Hello. We have a client with openserver 5.0.5 with 2 NIC's, one is local on 192.168.x.x and the other is public on 12.98.x.x, the server is accessed from home via internet using a third party telnet program. Everything was working just fine untill today; for no obvious reason telnet no longer works from home, but works localy. No stream failures, no error messages in /usr/adm/messages, and the only error message in syslog was: telnetd[xxxx] can't find user entry in protected database. I can't ping or telnet the server from the outside but can do that from the server to anywhere. I know this is bad, but the IP is direct on the server, the only router is the DSL router(gateway). Any help is appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Telnet problem
- Thread starter spddmon
- Start date
Annihilannic
MIS
It sounds to me like the DSL router is not routing incoming connections to the server. Can you reset it somehow, or verify its configuration. Annihilannic.
drtrinidad
MIS
Could it be that your DNS server was unavailable for a while? I usually get the message "telnetd[xxxx]: can't find user in protected password database" if a telnet connection is made then dropped without a login, so I think the telnet session IS being routed.
Whenever you telnet to OpenServer it tries to resolve the client ip address, which can cause a long delay if DNS is not available (and the client isn't listed in /etc/hosts). Maybe the third party telnet program times out too soon. It always seems to work (eventually) with SCO Termlite.
Whenever you telnet to OpenServer it tries to resolve the client ip address, which can cause a long delay if DNS is not available (and the client isn't listed in /etc/hosts). Maybe the third party telnet program times out too soon. It always seems to work (eventually) with SCO Termlite.
The error is reporting that the user that you tryed to login as was not a valid user, thats it, plain and simple.
( Unless you have a freaky weird problem )
If the third party telnet program logs in for you, then its probably got the wrong username in it.
Eliminate it quickly by using the telnet in windows on the remote machine and manually logging in as the same user that you tryed successfully, locally.
I suspect it will work, then check the settings in the 3rd party software.
if it was a routing issue, as mentioned above, you will not even get a "logon" prompt message when you run either telnet software.
Regards
UkWizard
- Status