fresh install 2K pro client't can't join 2K Domain 1

[hmunster]

Second effort...

I had to reinstall 2K Pro on a client and now it won't join the Domain. Server is 2000 Server with 2 NICs, one of which is for DSL from the DSL modem. RASPPPoE protocol. The LAN is a mix of 98, ME and 2K Pro machines. The pre-2K boxes have no problems, and the 2K client has internet/email connectivity and can ping the server from the command line, but no connection in graphical mode. Says the path to the Domain cannot be found. Can't join the domain, in other words. I'm sure its a DNS issue, but I don't even know how to find the DNS address; DNS is not configured on the Server - something about not working with ICS. I need a wizard or a tranquilizer. Thank you!

 

[butchrecon]

The other Win2K pro machines join the domain ok? James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[maverick]

Try this;

1: check if you can ping server, for faulty nic driver
2: check for a conflicting account on server
3: join domain with admin account

HTH "Hacker by Heart"
saenzinc@email.com

 

[jaeddy]

Maverick's third point is where I would start. When you reinstalled the 2K Pro box did you delete the "old" 2K box from Active Directory on the DC? The reinstall assigns a fresh SID to the box- even if you use the old name there will be a conflict with the old account due to mismatched SID's.

 

[hmunster]

No other 2K Pro machines... Maverick, yes I can ping server from 2K Pro client. This 2K client has internet connection pretty as you please. Just can't join the domain. I did delete the previous account, though I am using the same NetBIOS name. I'm getting "Path to Domain not found" or something close to that. Remember, the 2K Server is the DSL router, so to speak, running ICS. ICS is the DHCP server, and the instructions say to disable any other DHCP and DNS servers. DNS! So how is the 2K Pro client supposed to join an AD without DNS? Last night I switched it to joining a workgroup, named the workgroup the same as the domain, and now I have access to server resources, but it still is not joining the domain. No logon option for the domain at boot.

The '98, ME and NT clients, including an NT server, are all just happy as pigs in the mud with this arrangement.

 

[butchrecon]

Are you using Active Directory? You are useing a DOMAIN admin account (With local admin privlages) to join the Win2K machine to the domain correct? James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[tlcscousin]

Now try rejoining the domain.
I did have this happen once to me and a switch to workgroup and back to domain worked.

 

[hmunster]

Shovel, I hoped for that fix, but no. When changing to the domain name in Network and Dialup connections, it prompts for the account with rights to add a machine, but then says "...error occurred when attempting to join domain... Network path was not found." It's gotta be DNS, but I can't figure out what to do about it. DNS is supposed to be handled by ICS, I don't even know how to find the DNS server address in use.

 

[a073235]

Just a quick note re: deleting previous machine accounts in AD before you rejoin with the same name - it's no longer necessary in Win2K like it was in NT4. Not sure how/why, but the new security info gets propogated properly and everyone gets along?! Maverick / jaeddy have you folks seen otherwise? Our group does it weekly as we continuuously build out machines with the same names over and over - it's great! Heath
Principal Systems Engineer
Desktop and Mobile Platforms

 

[tlcscousin]

Just another thought do you have a firewall and/or anti-virus running? If so try shutting them off temporarily and see if this solves the problem.
My W2K machine wont access the server but it pings ok. I shut the two down and it worked so now I have to figure out what settings to adjust to get the thing working properly.

 

[butchrecon]

If you change the netbios name and give the Win2K machine a new account, can you now join the domain? I dont think it is DNS. It has to be the account you are trying to join. You may have deleted the old account, but you are still using the same computer name. try changing the name and then rejoin the domain. Get back to us. James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[tlcscousin]

I found this in another forum and was wondering if it might help.
If you have drives already mapped to a share on the server, the credentials (SID,
access token) provided are from the workgroup you are in at the moment. You can't connect to the domain because there is already
the connection from the workgroup!
In simple words: you can't log on twice (workgroup and domain) to the same server from the same machine.
So if you want to join the domain kill all drive mappings.
There is an article in the MS knowledgebase concerning this problem.

 

[butchrecon]

Also if you go to START>RUN and type:
ipconfig /all

This should give you all the network ID info you need (IP address, DNS, WINS ect..) James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[butchrecon]

You did not state you had mapped drives. Did that help you? James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[jrdebug]

first things first. if you do not have DNS and you have all servers running Win2K, then you do not have a domain! it's as simple as that. for you to have a domain, you must have one domain controller. for you to have a domain controller, you must have DNS running in at least one server. so, if you do not have DNS and a domain, you cannot join any. do i get you right?


Jeffrey Rebong
Computer Engineer/Network Administrator
jrdebug@yahoo.com

 

[hmunster]

Shovel, now I think we're on to something with the drive mappings. I'll check that tonite. JRDEBUG, I know you're right, but ICS is supposedly supplying the DNS service. That's why I shut down the DNS server that was running on the AD controller. As I've said so many times before, this ICS vs DNS/DHCP business is over my head no matter what I stand on. What really swamps me is that this was working before. What I'd like to do is buy a DSL router and turn off ICS, but I think there's still be DNS issues. The Internet is a pain...

Anyway, thanks a million to you all for the tips. I'm paying attention, keep it up!

munster