The Sun servers were slow to respond to new X connection request because it was trying to do a reverse lookup of the IP address of the PC. Removing DNS from the nsswitch.conf didn't stop this undesirable response because the NIS servers were running ypserv with a "-d" option. "-d" means it will search DNS for hosts if not found locally. Moving "/etc/resolv.conf" and restarting ypserv (it won't start with -d) was the temporary solution, while finding the configuration problems in my DNS tables was the other half. Of course a reboot probably would have cleared this problem, but was not an option.
Many thanks for the quick late night (at least here in PST) response I received from :
Eric van de Meerakker <Eric.van.de.Meerakker@asml.nl
His response pointed me in the right to the fix!
Also got helpful info from :
Merrell, Vince [IT]" <email@example.com
On Fri, 22 December 2000, Earl Cooke wrote:
> I support a small group of Sun w/s ( < 15 ) U/2's, U/60's, U/80's, & 450's, all running Sol 2.6 or 2.8.
> The w/s are usually accessed via remote X from PC's, some using X-win32, others using Chameleon's X server.
> Recently this customer switched ISP's and all the systems had to be readdressed.
> Since the address change, the time required to establish a connection from PC to Sun, and get the CDE splash screen back has gone from several seconds, to several minutes.
> There is an internal DNS server that was also readdressed, so I feared a DNS / name-resolution problem at first. So, I removed DNS from nssswitch.conf, leaving "files nis", I also added the IP address of all the PC's to NIS. This did improve things some. But, users that use "XDMCP broadcast" as a connection protocol, then select a host from the list, are still getting the slow response .... from some of the Suns, resonable response from others.
> I think my problem is still name-resolution related, because if I run a "netstat -r" or "arp -a" the system gets lost looking up names, and takes minutes to return a response. But if I run "netstat -rn" (n-meaning don't return name, just addresses) I get an immediate response. This on a system that's not configured for DNS!!!
> OK, I think I'll stop talking before you all get as confused as I am.
> Does anyone have an suggestions regarding the XDMCP response times, or better yet, how do I stop the system from going to DNS, and waiting several minutes before timing out. Example: if I telnet to an unknown host, the system takes several minutes to timeout with "unknown hosts"
> I'm all ears.
> Earl Cooke
> Find the best deals on the web at AltaVista Shopping!
Find the best deals on the web at AltaVista Shopping!
sunmanagers mailing list
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:25 CDT