Link to home
Start Free TrialLog in
Avatar of STS-Tech
STS-TechFlag for United States of America

asked on

Can't join XP mode to domain

Ok so we are setting up XP Mode for some clients. I have been able to join XP mode to my domain, in fact i'm logged in one now. First things first the network is on the 192.168.1.x, so naturally i try to hardcode the ip, found a spare slot (192.168.1.45) left the dns blank because i don't really need it at this time, then try to join the domain. It prompts me for credentials, i enter them, then i get an error that it can't find the network. I double check with the hose machine, same default gateway, tried entering my host machines dns, nothing. I loose internet upon changing ip (obviously). I can't ping anywhere, not the router, the host computer, nothing. I can't ping the VM. I'm really at a loss now, i had no problem with my VM here at the shop, any ideas?
Avatar of STS-Tech
STS-Tech
Flag of United States of America image

ASKER

An added note, whenever i change the IP address to the same network as out network (192.168.1.x) i am not prompted for credentials when tring to join the domain. Instead i get the cannot find the domain controller error. If i click details, it claims the problem is within DNS, this happens both if left blank, or pointing to my DC.
ASKER CERTIFIED SOLUTION
Avatar of Abdul Jalil Abou Alzahab
Abdul Jalil Abou Alzahab
Flag of Canada 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
> left the dns blank because i don't really need
> it at this time, then try to join the domain.

In other words, Active Directory is not your specialty.  Active directory NEEDS DNS.  DNS is how it finds domain controllers and other network resources.  Without CORRECTLY entering DNS, you cannot join a domain.

IF you want a static IP, that's fine, but it needs to be in a network with a route to your DC's network AND it needs to use your DCs (and only your DCs) for DNS resolution.
A-J : I will try

leew : You got it, not my specialty, i'm not that kinda guy, that would be my partners. It looks like i messed up my working, i apologize, i ment that at this time dns doesn't matter, because i can't even ping anywhere.
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
Pacific -

At this moment i am following A-J's steps and just switched the nic from NAT to the nic card itself. The VM is rebooting now to see the results (VM through RDP is slow as hell).

Everything is all on the same network. I have already disabled the Win 7 firewall, and the kaspersky internet security we use is not set up on the machine yet for it is a test.
Guys -

After changing adapters i was able to ping, and just joined the domain. I did notice, although the kaspersky wasn't active yet, the client still existed, I'd immagine the firewall would be off, i closed it anyway, not sure if that had to do with it but i'll find out next reboot.

Thanks everyone!