• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 351
  • Last Modified:

connect a client PC to Windows 2003 server

I have a Windows 2003 server which will replace and exisitng NT server on the network. Both servers are currently on the network with a trust between them and data being transferred to the new machine. Network printers have already been added to the new server and now I want to add the client PC's
I have 2 new Win XP PC's and have tried to connect them on to the 2003 domain using the Control Panel,  System, Computer Name, Change, enter the domain enviro.local and it will not connect. but they will easily connect to the NT server domain.

The message it comes up with - ( Ihav etried both enviro and enviro.local as the domain name to connect to....)
Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The domain name enviro might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain enviro:

The error was: "This operation returned because the timeout period expired."
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.enviro

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

192.168.1.200  

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.

For more information on how to correct this problem, click Help.

Whilst I can ping the old server I do not get a response when I ping the new server,although they are both on the network and transferring data across. I used netscan from the new server and can see the  PC's on the network. I tried putting in the machine name in the AD first and then connecting but this did not work as well.
Netscan from the PC's does not see the new server?? I have tried to connect 3 different machines on the network and am getting nowhere, it does not seem to see the AD on the 2003 server. does anyone have any pionters?
thanks, rich

0
richwj
Asked:
richwj
  • 6
  • 6
1 Solution
 
Chris DentPowerShell DeveloperCommented:

It looks like a problem with DNS. Is 192.168.1.200 the Windows 2003 server?

DNS should be set roughly as follows:

2003 Server (AD First DC):

Runs DNS Service
Has AD Integrated Forward Lookup Zone for AD Domain (this should be in the form yourdomain.local, or yourdomain.com, etc)
Has AD Integrated Reverse Lookup Zone for IP Range
Preferred DNS in TCP/IP Configuration is itself

XP Client:

Preferred DNS in TCP/IP Configuration is 2003 Server (AD DC)

Let me know how it's setup anyway, and we can go from there.

HTH

Chris
0
 
richwjAuthor Commented:
Chris, 192.168.1.200 is the 2003 server
Ad has 2 x forward lookup zones:
_msdcs.enviro.local
enviro.local
XP client preferred dns is 192.168.1.200 (2003 server)
rich
0
 
Chris DentPowerShell DeveloperCommented:

DNS looks good :)

When you join the XP client to the domain use the domain name enviro.local.

If Windows 2003 hasn't registered entries in WINS then you won't be able to resolve the domain name enviro.

Windows 2003 not attempting to register in WINS isn't a particularly bad thing though.

Anyway, let me know if it joins with the full domain name?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
richwjAuthor Commented:
I have tried using the full domain name enviro.local and it comes up with exactly the same as above. It does not seem to see the 2003 server.
Is there any reason why I do not get a response from the server when I ping it? Is there some security feature I don't know of in 2003 server?
0
 
richwjAuthor Commented:
just check some error appearing in the dns server event viewer

error 1
The DNS server was unable to complete directory service enumeration of zone Enviro.local.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

error 2
The DNS server was unable to complete directory service enumeration of zone _msdcs.Enviro.local.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

error 3
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

warning
0
 
Chris DentPowerShell DeveloperCommented:

Anything in the Directory Services Log?

Although you should be able to ping the server, I assume you're trying that by IP address?

Is there anything (like a Firewall) sitting between the client and the server?
0
 
richwjAuthor Commented:
I have stopped and started teh dns service and have this information message

he DNS server could not signal the service "NAT". The error was 1168. There  may be interoperability problems between the DNS service and this service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I don't know what this means
0
 
Chris DentPowerShell DeveloperCommented:

You have Internet Connection Sharing running on the 2003 server? Either that or Routing and Remote Access?

If you have either please stop them and try starting DNS again.
0
 
richwjAuthor Commented:
I am trying to ping by IP address and there is no firewall in the network - it's just that the server does not show up on netscan and on ping 192.168.1.200
Is the server itself firewalled? it's quite strange as this is all going on I am still transferring files from the old server(.100) and linked to the router 192.168.1.1
0
 
Chris DentPowerShell DeveloperCommented:
There won't be a Firewall on the server itself unless you've added one.

The network config does seem to be having a few problems though - the NAT error above normally relates to either Internet Connection Sharing or Routing and Remote Access.

Those type of services have to be pretty carefully configured when you need to run DNS on the same server. So it would be a good idea to stop them if they are running.

I take it the server itself can happily ping the default gateway and the client PC?
0
 
richwjAuthor Commented:
Chris, I take my hat off to you - thank you for your help, as soon as I disabled Routing and Remote access the PC's connected right away. The points are your well deserved - I can now continue putting the rest of it together.
richard
0
 
Chris DentPowerShell DeveloperCommented:

Glad I could help out. Good luck with the rest of the migration.

Regards,

Chris
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now