Losing connection to W2K Server

  • Thread starter Thread starter George Jew
  • Start date Start date
G

George Jew

I have a W2K server network with six PCs. (1 98, 3 W2K,
and 2 XP Pro) The XP pro PCs would have problems
throughout the day losing connection to the server. The
logins on the XPPro PCs seem to take longer then the W2K
and 98 PCs. No problems with the W2K and 98 PCs. I switch
the network cable with one of the XP Pro PCs as a test.
Still the same problem. Help please?

Thanks
George
..
 
George,

I am having EXACTLY the same problem with a brand new XP
Pro pc and W2K server - lost connection to the domain
controller and slow login. Here's what I've tried so far:

- turning off feature that allows pc to power down NIC
- installing latest driver for NIC

Neither of these has helped.

Have you noticed periodic Event ID 15 and Event ID 1054
error messages in your event log on the XP Pro machines?
Both of these refer to actions that could not take place
because "the specified domain either does not exist or
could not be contacted." I suspect this is another symptom
of whatever problem we are having.

I believe that we must have our basic settings correctly
configured since we are able to connect W2k machines
similarly with no problems AND because we are able to
login to the domain and operate successfully for a period
of time.

My next attempt at a fix may be to try a different NIC.

Could someone PLEASE help us!

-- Kathy
 
I'm having the same issue. I also get a LASRV event in
the event log. I'm going to try and turn off the
autodisconnect feature to see if this resolves my
problems. I sure wish some one at microsoft would chime
in and let us know what the problem is.
 
George Jew said:
I have a W2K server network with six PCs. (1 98, 3 W2K,
and 2 XP Pro) The XP pro PCs would have problems
throughout the day losing connection to the server. The
logins on the XPPro PCs seem to take longer then the W2K
and 98 PCs. No problems with the W2K and 98 PCs. I switch
the network cable with one of the XP Pro PCs as a test.
Still the same problem. Help please?

Thanks
George
.
Click to expand...


This smells a bit like a DNS problem.

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers.
Accept any nags etc, and let it delete any corresponding reverse lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
 
Ron,

You hit it right on the head. These Windows xp machines I
have are setup with Static IP addresses. The DNS server
was not setup in the TCP/IP settings. The majority of the
computers on my network use DHCP which will automatically
grap the dns server. I put in the Primary DNS server
address and haven't had any problems since. Thanks for
taking the time to answer our questions. This has been a
real thorn in my side for a couple of weeks.

TJ
 
Ron,

I've been going through your checklist and have some
questions.

First, here's our setup:
1 W2K server w/ 2 NICs (I realize this may be a
complication and honestly, can't remember why 2 were
necessary - had help configuring server - I think it had
to do with allowing VPN connections)
2 W2K Pro workstations that work fine!
1 new XP Pro workstations with the lost DC issue
all machines connected through Dlink Cable router

From the server and the W2k workstations I can ping all
other computers by IP, name, and can access all computers
via RUN command by both IP and name.

From the XP machine, I can ping all other computers by IP
and name, but I can only access the server and the XP
machine itself via RUN and name, and I can't access
ANYTHING by RUN and ip address!

I currently have static IP addresses and TCP/IP DNS server
points to router (per instructions in router docs) from
all adapters. On the server's 2 adapters, each also
points to itself as the alternate DNS server.

I know you recommend using DHCP from the router rather
than static addresses, but how will this allow me to
ensure that the server points to itself as the DNS server
as you recommended, since the ip address can change?
Also, will DHCP work with the 2 adapters on the server.

If I keep the static ip addresses on the server, should I
point the primary DNS address to themselves and the
secondary address to the router?

I know our setup is strange, but at least it worked for
our application for the last 2.5 years and now this new XP
machine won't cooperate!

Thanks for your help
 
Back
Top