Adding to domain with a different subnet

You could temporarily add a lmhosts entry for the PDC, on the machine in question. See MS Q163949 for details.

Hi,
You could solve the problem with a LMHOSTS file,with a #PRE #DOM:domain entry.

Regds
anoop

Make sure your subnet mask is correct and gateway address. Incorrect numbers could cause this problem.

Had this problem recently, with a NT 4 PDC and a WIN 2k workstation. Had a good LMHOST file and still couldn't join the domain.

1. Good LMHOST entry on the workstation, or WINS.
2. Verify that NETBIOS over TCP/IP is enabled on both machines.
If that doesn't fix it.
3. I enabled Netbui on the server and the machine long enough for them to find each other and join the domain, then I disabled it. Recommended via Microsoft article Q258832.

Good Luck
0bytes

If you use DHCP server add an new scope with this different subnet mask.

Point value changed by question poster.

If you don't give us more detail about posted answers you will not receive more answers. You can add comments to your question. You can rate the answers when you will have the good answer.
Other posibilities is to reauthenticate your machine on domain:
For that remove from Server Manager the workstation name from list. Log on workstation with local with local admin rights and in network properties set as member of workgroup. Reboot computer. Log on again as local admin and set as member of domain and set the option . Give the information about name and password of the Domain Admin. Reboot computer.

I have tried to reauthenticate on the domain by deleing the account and then trying to rejoin, this is the issue , it will not rejoin the domain!
I have added the lm host file with pdc name, ip and domain, have added netbui and still am having the same issue.
any more ideas anyone??
Thanks!

Depending on the number of hosts on your subnet, you could consider putting a BDC on the subnet in question.

Adding an entry to your PDC in the LMHOST file with x.x.x.x pdcservername #PRE #DOM:domain, also ensuring that your default gateway is set correctly should work ok.

Can you ping the PDC from the other subnet and get a reply, is there any port filtering taking place between subnets, do you have the same problem with other hosts on this subnet?

Hi,
Once I'd the same issue,due to wrong ip entry
in the LMHOSTS file.You 'll get the same error if your wks thinks some other PC as PDC.Verify that your WKS is connecting to PDC itself.There is no subnet related issue since you are able to communicate with server.

Have you tried manually adding an account for this PC at the domain controller and then trying to logon. Also when you ping do you ping using the ip address or the name of the PDC. If you can ping using IP address and not the name you have a Net Bios problem. (No name resolution) I have to assume that you have other PC's in this subnet joined to the domain. If this is the first you want to make sure you are running the DHCP relay agent on your router or have a DHCP server on the subnet.

Thanks for all the suggestions , all of which I have tried but no joy!
The machine in question is the only machine on that subnet.
The default gateway address is correct as are all the other Ip addresses and I can ping the PDC from the machine ...... not sure how long it should take both machines with NETbui to see each other but I guess they should have by now.

Sounds like your SID could be messed up. I would start new and log in as admin and rename the PC. Reboot PC and then trying to join domain under new name. If you have name resolution (Wins or LM Hosts) and can ping the PDC from the client using the name of the PDC (not the IP address) and have admin. rights on the PDC it should work. If you are crossing a router NetBeui will not work. It is a non-routable protocol.

any more ideas?
I have tried all the ones listed and am really at a loss now?
any ideas, no matter how wacky would be appreciated!

Install a WINS server on either subnet. Configure both the DC and the client computer to use that WINS server.

Should take care of the problem.

This question was auto closed due to inactivity