Typical problem on HP servers!!!

[Subhash Pippala]

Hi all,

Recently, I have observed a typical problem with our HP-UX servers , we have Xonnet software installed on Windows NT 4.0 clients and HP servers are restricting some of the IP addresses to get connected to it but the same clients get connected without any problem to SUN servers. We have checked and tried all the options but so far there is no break through and could not able to isolate the problem.

Problem description :-

IP address 10.184.8.2 is able to connect using Xonnet but 10.184.8.4 fails, so in the same subnet few IP's work and few fails, this is only one instance, similarly we have some other subnets with similar problems. But all the clients are able to get connected via Telnet. And there is no restriction whatsoever on the network equipments as we have tested by connecting to the HP server directly by laptop using cross cable but the response is same so this eliminates any network equipment related problem also.

Hardware/ OS details of HP servers :

Hardware Model : 9000/820/D280 and 9000/800/L3000-5x
OS version : HP-UX B. 11.00 U

Please do let me know the solution for resolving the above problem or any patch requirement on HP servers.

Thanks & Regards.
Subhash

[Ron Irving]

I had a similar problem with my app on our server. Some were able to access the app, some were not. What I did was to ping the affected users, and had them try again. Lo and behold, they were able to get to work. I have no idea what caused this problem.

Hope this helps

Ron

[Santosh Nair_1]

This is just a guess but it sounds like the arp cache is messed up. Can you try deleteing the arp cache on the server for 10.184.8.4 and then try to connect to the application again.

-Santosh

[Subhash Pippala]

Hi Ron/Santosh,

Thanks for your suggestions.

Good news is my problem got resolved. We found some important entry missing in our Secondary DNS server, after making that entry, everything is fine.

Thanks once again for the help extended by you.

Regards,
Subhash Pippala

[Marcus Höfner]

Hi,
i had similar a problem. The reason was that the name resolution doesn't work correct for the hosts, because the XServer try to get the hostname by the IP-Address. In my case the entry of the client in DNS reverse lookup zone was not correct.

Marcus