telnetd - Urgent

[Madhu Sudhan_1]

Friends,
We connect to customer site through Internet. I use Reflection X for this purpose. The problem is if stop working with the x-term after logging into the customer site for a while. It just hangs. I have to kill the session and relogin again.

Any suggestions are helpful.

Regards,

[Wodisch]

Hello Allen,

that's usually DNS timeouts!
Almost all telnetd's today to reverse name lookups about their clients, and if your client station has no DNS name, you will experience the DNS timeouts - 30s or more!

Put that client's hostname and ip-address into the server's "/etc/hosts" and modify its "/etc/nsswitch.conf", to first check locally:

hosts: files[NOTFOUND=continue] dns

HTH,
Wodisch

[Madhu Sudhan_1]

Wodisch:

I have made entries as mentioned. But the problem I see is that it is not using "files" (nsswitch.conf) for hostname resolution.
My hosts entry in nsswitch.conf is as follows.

"hosts: files dns"

It is always referring to DNS Server.

Lokks like the server is using IPV6.

Thanks,

[Madhu Sudhan_1]

Friends,
any other inputs ?

Thanks,

[Francisco J. Soler]

You can run de in.telnetd with -n option and see what happens.

If your configuration is through xinetd, you can put in the telnet file a line with server_args = -n and restart the xinetd.

I hope this helps

Frank.

[ramesh_6]

Hi,
Since you are using Refelction X to connect to the server it may not be a problem with telnet daemon. Why cant we think in the sense of X-windows.

Once you connect to the server if you should get the login screen in ur Reflection X.

If u r getting this screen then x windows login manager is working perfectly and if not restart the login manager "dtlogin"

After successfully logging in to the server your reflection hangs then it can be a problem with Session manager or the Window manager. Try restarting ur session manager "dtsession" and window manager "dtwm"

Hope this helps

Regds
Ramesh

[Christoph Rothe_3]

Hi everyone,

it can also be a firewall which cuts idle connections after some time.

The easiest way would be to send some keep-alive-pakets, but I do not know if Reflection supports that...

Christoph

[Scott Nelson_1]

It sounds like you are going through a NAT firewall, namely the Linux masqueraded firewall.

The firewall has a timer on each connection going out. Whenever there is activity, the timer is reset back up. But when the timer goes away, information about the connection goes away, and you experience the hangups you mentioned.

You you have access to the firewall, you can change the timers, but it will affect all outbound connections.

Another workaround is when you know you will be away for a while, start up a ping.

[Eric Ladner]

Are you connecting through some kind of non-permanent connection (i.e ISDN or something?)

One thing that happens to me at home (through ISDN) is that the router drops the connections after some period of inactivity.

One solution is to start two windows, run your stuff in one, and in the other start this:

ping -i 15

That will ping every 15 seconds (on a Linux box anyway, other vendors ping commands may or may not have the -i option) and keep your connection open.

Something to try...