[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::windows-nt

Title:Windows NT
Notice:See note 15.0 for HCL location
Moderator:TARKIN::LIN.com::FOLEY
Created:Thu Oct 31 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6086
Total number of notes:31449

5964.0. "Server 'forgetting' its IP Gateway" by RINGSS::WALES (David from Down-Under) Mon Apr 28 1997 16:52

G'Day,

	I have a real strange problem with one of our servers.  The system is a
Prioris ZX 5166MP2 running Windows NT Server 3.51 SP5.

	The machine has two network cards with no routing between them.  One is
connected to the DIGITAL internal network and has a registered IP address.  The
other is using 10.x.x.x addresses.  As there is no routing this is fine.

	The problem is with the EASYnet adaptor.  When I reboot the system
everything works fine.  I can see systems outside of our subnet and they can see
us.  This works for a while (can be up to a few days) and then the only traffic
that works is within our own subnet.  We can't see out and nobody outside the
subnet can see us.  All traffic within the subnet works fine like share access,
web page access etc.

	The fault is exactly as if you didn't have an IP gateway defined
(although I'm not sure if that would also stop incoming IP traffic) but it
definitely is defined and it works fine after a reboot so it just seems to be
'forgetting' about the gateway.  When the fault exists I can ping the gateway
but I cannot ping anything that has to go through it.

	We've had the gateway (a DECnis) rebooted without effect and it's hard
to believe that it would be the gateway as all other systems using it continue
to work fine.

	This has got me stumped but I need to sort it out quickly as without the
IP connectivity our trust of the DIGITAL3 domain is down so any resources shared
using the trust are inaccessible to the users.

	Any help would be *greatly* appreciated!

David.


T.RTitleUserPersonal
Name
DateLines