> -----Original Message----- > From: Lee Allen [mailto:[EMAIL PROTECTED]] > I have been using Xvnc for some time now, in inetd mode. It > is running > on a Linux server (RedHat 6.2). The clients are various > Windows systems > running the viewer. We primarily use TightVNC but I have tested the > standard AT&T distribution and I see the problem there, too. > > The problem is this: occassionally the viewer will fail to connect to > the server. If it fails once, it may fail multiple times. > It may take > several seconds to a minute to get a good connection. > > During this time I can only find one "clue" on the server: > "netstat -an" > shows this: > > Active Internet connections (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 192.168.0.110:5900 192.168.0.3:2064 > TIME_WAIT
Are you sure you are running in inetd mode? As far as I know inetd, the communication is not on the requested port. IF the connection goes away by itself in a reasonable time (up to several minutes) then you are just waiting for an other session to be setup. If you use the setup as on http://www.sourcecodecorner.com/articles/vnc/linux.asp, the ports for inetd usage are from 5950 upwards to avoid collisions with plain vncserver sessions. > > the first IP address is the Linux server, the second IP address is the > Windows client. The Windows client port number varies. > > I must wait for this connection to disappear before I can successfully > establish a connection again. > > Does anybody have any idea what's going on here? > > Using TightVNC 1.2.4 1.2.6 is out (however, that should not be the problem here) CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
