Link to home
Start Free TrialLog in
Avatar of Wataw
WatawFlag for Hong Kong

asked on

Resolve AD Server IP Problem

Dear all,

I have four DCs in my environment which is running Windows Server 2003. And each machine have two NICs, the first one for production (ie. 10.52.x.x) the second one is running on a Giga Network for running backup. (ie. 192.168.0.x).

Unfortunately, the DNS record will automatically add 192.168.0.x on it. Therefore, the client will resolve an 192.168.0.x instead of 10.52.x.x . This make an serious problem when the logon script mounting using the UNC path. For example, \\dc1\share.

Is there any method to avoid this happens again? I have tried manually delete the A record in DNS server, but it will automatically generate it later. Thanks.

Best regards,
Wataw
ASKER CERTIFIED SOLUTION
Avatar of Chris Dent
Chris Dent
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial

The tick-box doesn't always work in my experience, it should, but... The registry entry achieves the same thing hence the statement about it being the most reliable method I've found :)

Chris
Avatar of Wataw

ASKER

Yes, Chris-Dent is right, the tick-box is not working and registry works. Thank you all of you, you both are great.