TCP lost over time

  • Thread starter Thread starter Chuck
  • Start date Start date
C

Chuck

Having an interesting problem. Dell poweredge 2600, dual
3.06, 2GB of RAM, Windows 2000 server, active directory,
terminal services, DNS, running Citrix MetaFrame 1.8 for
Win2k, and using Pervasive SQL 2000i. Running NAV Corp
server 8.1. I have check every service that loads and
religously check the windows/run rection under HKLM and
HKLU in regedit to make sure nothing is loading.

Server runs for about 10 hours, then can no longer contact
the internet. At about 12 or 13 hours, it loses network
shares. I find this interesting because 3 of its shares
point to directories on it's own physcial drives. Also at
this point I can not open any Active Directory admin
tools, it says it cannot contact the AD server, which is
itself. Anyone have an idea?
 
Is there anything in the EventLog on the server?
Which NIC do you have? Have you downloaded the latest driver updates
from Dell? If you have dual NICs, do you use adapter teaming for load
balancing? If so, try to turn that of (switch to fail-over).
 
Using onboard intel pro/1000 xt. Driver is the latest on
dell website. Server has been inplace and rinning for 6
months. This problem started last week.
 
OK, so the NIC does not seem to be the problem.
Surely, there must be *something* in the EventLog?
What's the first event that is logged when problems start?

Can I assume that a reboot of the server fixes the problem,
temporarily?
Does the problem always start at the same time every day, or
always after 10-12 hours of runtime, irrespective of the time of
day?
And does it make a difference if the server is used or not? What
happens if you reboot on friday night, does it survive the
weekend, assuming that you don't have users in during the weekend?
 
It seems to be doing it from the time thw server is
rebooted. Which does fix the problems temporarily. Doesn't
matter if anyone is on or not. The only messages in the
event logs that I can find that are unusual are 1 that
says "Time out (3000 milliseconds) waiting for IPsecurtiy
dervice to connect". There are also 1 that says it "connot
connect to yahnis.local with (0x2747)" and one that
says "connot queary for group objects". That is because
after internet access goes the DNS and Active directory go
soon after. There are severl entries after that that
say "windows cannot determine the user or computer name.
Return 14".
 
Back
Top