A
ANIT
I have a laptop running Windows Vista Ultimate and am having trouble connecting
to my company's W2k3 domain. When I try to change from a workgroup to a domain,
it immediately asks me for a domain user account that is authorized to add
accounts to AD. I provide the account/password and about 20 seconds in I
receive an error stating 'the network path can not be found'. When I try
to use the 'join a domain' wizard, I am told that "a computer account for
the computer name of my laptop has been found, do I want to use it" - I say
yes (this is the case because after it didnt work the first time I manually
added a 'computer' to AD identical to my laptop's computer name). If I remain
logged in locally, I can see all network shares (granted I provide my domain
credentials), access the internet, RDC to servers and print to network printers,
as well as successfully ping both our DCs. I've tried explicitly providing
the IPs of our DNS servers and disabling IPv6 as suggested by others but
with no success. I've searched on the internet and I've seen at least one
post explaining the same exact issue but the suggestions did not work in
my case - so I know it's not just me. Any help would be greatly appreciated.
Thank you in advance!
- Chase
to my company's W2k3 domain. When I try to change from a workgroup to a domain,
it immediately asks me for a domain user account that is authorized to add
accounts to AD. I provide the account/password and about 20 seconds in I
receive an error stating 'the network path can not be found'. When I try
to use the 'join a domain' wizard, I am told that "a computer account for
the computer name of my laptop has been found, do I want to use it" - I say
yes (this is the case because after it didnt work the first time I manually
added a 'computer' to AD identical to my laptop's computer name). If I remain
logged in locally, I can see all network shares (granted I provide my domain
credentials), access the internet, RDC to servers and print to network printers,
as well as successfully ping both our DCs. I've tried explicitly providing
the IPs of our DNS servers and disabling IPv6 as suggested by others but
with no success. I've searched on the internet and I've seen at least one
post explaining the same exact issue but the suggestions did not work in
my case - so I know it's not just me. Any help would be greatly appreciated.
Thank you in advance!
- Chase