General discussion

Locked

Join WinXP Pro to W2K Server Domain

By theclaritygroup ·
As network supervisor I need to join a new WinXP Pro Desktop-usually very easy. Performed usual steps to configure for end user - among other steps, uninstalled Norton, turned off Win Security Center Firewall, entered domain user name and password in Network ID, etc. then plugged in network cable, opened my computer to properties to join domain on server. Surprised to see LAN already connected, and able to ping server and other network machines, can't ping it back. But tried to change from workgroup to domain, and join - mssg - can't detect domain, make sure spelled right. Used other network machine as example to validate names,spellings. Spent two hours on phone with manufacturer techie-stumped. Ran Diagnostics-all okay. Suggestions?

This conversation is currently closed to new comments.

15 total posts (Page 2 of 2)   Prev   01 | 02
Thread display: Collapse - | Expand +

All Comments

Collapse -

by chris In reply to Join WinXP Pro to W2K Se ...

I would also check WINS, W2K and XP are not supposed to rely on WINS, but I have had experience in the past where by entering the server into the lmhosts file and adding the #PRE, I get the desired result.

When you say you can't ping the local host PC, you're pinging the netbios name, and not the IP addr. itself. try that too, as the others mentioned run "ipconfig /all" check DNS and WINS entries, and note host IP addr. then from server ping host IP addr. and netbios name. if no reply to name ping, DNS is not working right. enter server into lmhosts file on local PC, remove .txt extension and reboot. Also verify that the client has an entry in your DNS servers host table.

The commment about the auto-address not being routed is irrelevent, 172. and 192. are non-routed also and they are the most common private subnets in existence, in fact for this reason, I don't want my private net to be routed into public space.

Collapse -

by Ron In reply to Join WinXP Pro to W2K Se ...

This really sounds like a DNS issue. Are you using your domain controller for DNS. Do you have the correct DNS entry in the workstation. I have had the same problem several times, and it was always am incorrect DNS setting.

Collapse -

by plictech In reply to Join WinXP Pro to W2K Se ...

Can you see this machine name in network neighborhood ? Has this machine name been added to the domain ? If not add the machine name, release the ipconfig, power down and up and try again.

Collapse -

by tejas73 In reply to Join WinXP Pro to W2K Se ...

I faces simmilar problem with my laptop and i solves it by removing DNS entry fom the active directory and them rejoining it to the domain

Collapse -

by mcleodcomp In reply to Join WinXP Pro to W2K Se ...

Check your dns entries and make sure they point to the authenticating server.

Back to Windows Forum
15 total posts (Page 2 of 2)   Prev   01 | 02

Related Discussions

Related Forums