DNS troubles - possibly

  • Thread starter Thread starter SAKWOYA
  • Start date Start date
S

SAKWOYA

Hi all

I'd appreciate any pointers on the following:

Small network of around twenty WinXP clients running on a Server 2000
with Active Directory. Recently we have been getting delays in logging
on. Event viewer on both the server and the clients is thowing up Event
ID 3034 and 3029 MRxSmb errors - also folder reidrection sometime fails
and Event Id 4 - Kerberos Client recieves KRB_AP_ERR_Modified (this
last one sometimes names another client machine as the server - not the
real server name). Also a few other Event Ids being recorded.

I figure that this mish mash may be due to either a DNS or IP number
problem. I can find no duplicated IP numbers or machine names on the
netrwork.

The DNS *seems* to be correctly setup on the server and I've burrowed
through Micorsoft KB and other websites to no avail.

Any help appreciated.

Bob
 
Make sure each DC has itself as well as peer DCs in its own TCP/IP dns
properties.

Make sure all clients have ONLY the DC's (both or all) IP in their TCP/IP
dns properties.

Note: The dns assigned to you by your ISP should not appear in the client's
or the server's dns client. Typically it is only entered into the router.

-Frank
 
Frankster said:
Make sure each DC has itself as well as peer DCs in its own TCP/IP dns
properties.

Make sure all clients have ONLY the DC's (both or all) IP in their TCP/IP
dns properties.

Note: The dns assigned to you by your ISP should not appear in the client's
or the server's dns client. Typically it is only entered into the router.

-Frank
Click to expand...
Hi Frank

Only a single DC and he's setup OK - the clients are set to the
internal IP number of the server only.

Still getting slow logons but resinstalling XP SP2 seems to be
helping?? Weird...

Bob
 
BobT said:
Hi Frank

Only a single DC and he's setup OK - the clients are set to the
internal IP number of the server only.

Still getting slow logons but resinstalling XP SP2 seems to be
helping?? Weird...

Bob
Click to expand...

Possible bad NIC? Or... misconfigured? You might try setting the NIC to
auto-negotiation if it is presently hardcoded to 100/100.

-Frank
 
Back
Top