XP Pro connecting To NT 4.0 Domain Server

Hi

I have a NT4 server running with Workstations running NT Workstation and Win 2000 Pro. This runs no problems.

Problems now start we have just purchased 5 new workstations with XP Pro preinstalled. When I try to conect them to the server they all come back saying they cannot connect to the domain.

We have fixed Ip's and I now the DNS server is running Ok as all other workstations are running fine. Help

Is XP pro compatable with NT?
I have configured XP Pro as I would win2000 leaving the 1394 bridge alone is this correct?
I am soon going to install a new server to replace the existing one, this will be running 2003 server standard edition will there be any problems with XPPro and this as we are going to upgrade all workstations to XP Pro.

thanks

JFK

I have no problems connecting to my NT4 domain with XP Pro

Do you get the problems when you are in the System applet in the Control Panel and in the Computer Name tab trying to connect to the domain?

Do the XP machines have the correct DNS servers set up. If you are using DHCP, they probably do. Otherwise, open up the Local Area Connection properties and check that the DNS server address points to the local DNS server. You can confirm changes by typing "ipconfig /all" (without quotes) from the Command Prompt.

Can you ping the NT4 domain controllers? Can you ping the domain name (ping domain.com)? Do the XP computers have a firewall running (Internet Connection Firewall, or ZoneAlarm, etc.)?

HTH,

Edwin

Edwin

Yes I do get the error message in the Control panel System Tab. I now the DNS server IP is correct as I have Win2K Workstations connecting no probs at all. I cannot ping the domain name (timeout) and there are no firewalls running.

any other suggestions would be appreciated. Do oyu have to be running a particular service pack to enable XP pro to connect? Trying to find this out on microsft site but I only have ISDN connection and microsoft site reaalllyyyyy ssssllllllooooowwww.

thanks for your efforts

JFK

OK Guys

My mistake we are running on fixed Ip's not DHCP and I had put in an invalid Ip

Thanks for your efforts.

JFK

PS Can anyone suggest a good source of info on setting up remote access.

Glad it's working



Slightly off topic (create a new topic for more replies), but do you want something like Virtual Private Networking? A good place to start is probably: http://compnetworking.about.com/cs/vpn/