Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 342
  • Last Modified:

Connection Problem (HP-UNIX_ WIN98)

We have 5 NT Servers and 1 HP-UNIX box. 125+ users running Win98 with 3 remote locations using T1 and Frame Relay. When there is a "Hicup" in the Frame or T1 and connection is lost, the users who were conected to an application running on the HP-UNIX box, are then "Blind" to the UNIX box, meaning can't even ping the IP of the UNIX. All of the servers and other workstations can be pinged. Connectivity can be restored by either rebooting the HP-UNIX box or letting it time out (3 hours). Is this problem inherant with UNIX connecting with Win98 and is there a fix for it.

Thanks
0
WorthIS
Asked:
WorthIS
  • 4
  • 3
1 Solution
 
chris_calabreseCommented:
Is the HP-UX box running 11.x?  And is the 'hicup' causing the HP box not to be able to ping the gateway to some of your nets?  If so, this may be cause by HP's "dead gateway detection mechanism".  I can't remember how to turn this off, but a quick call to HP support will do the trick (you do have a support contract...)

The only other thing I can think of is that it's some other type of routing problem like one of your routers sending route updates when the link is down, but not sending subsequent updates when the link comes back up.
0
 
WorthISAuthor Commented:
Chris,

We are running Ver 10.2 ,this problem is quirky because anyone remote who was not connected to the HP during the down-time (Hicup), but yet still logged into the network is able to connect to the app. w/ no prob. So that really leaves out the routing problem right?

0
 
chris_calabreseCommented:
That definitely leaves out the routing problem, at least on the HP-UX side.

Are you guys using proxy ARP?  Maybe the machines talking to the HP-UX box during the hiccup are getting bad ARP cache entries.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
chris_calabreseCommented:
Or perhaps they are getting ICMP destination unreachable's and their stacks are setting these routes as down until the route entries time out.  Search the MS knowledge base for a bug of this type (or the ARP timeout type).
0
 
WorthISAuthor Commented:
Chris,

Thanks....I think that you kinda hit the jackpot....

Once again thanks and have a safe and happy 4th
0
 
WorthISAuthor Commented:
Great help.....
0
 
chris_calabreseCommented:
Glad I could help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now