Windows 2003 SP 1 with Windows XP SP2 workstation, No shares appearing yet Internet (DHCP) is Working

We have about 7 computers on a Windows domain with a Windows 2003 PDC.  We recently upgraded the Windows 2003 PDC to Service Pack 1.  All of the computers appear to be fine except one.  They are all running wireless NICs to connect to the server through a Belkin Pre-N unit.

We at first thought something must have happened due to the server service pack update but soon discovered that that this was isolated and that when we changed NICs it helped out and it was able to get back on the domain.  We finally splurged and bought an actual Pre-N NIC to go with the Pre-N router and signal strength is much better, we get a dhcp lease and consequently can use the Internet, yet the unit will not join the domain now.  This has really got us baffled.

What could be going on here?  We need this to work immediately as we are in a time critical situation.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Where do they get the DHCP lease from? If from the Belkin, it's likely that it hands out its own or your ISP's DNS server. That way, you won't be able to join the domain, because the client can't find the necessary DNS records to locate the DC.
You have to make sure that *all* your domain members (including the server itself) use your DC *only* as DNS. On your DNS server, you can then configure forwarders to point to your ISP's DNS for external lookups.

10 DNS Errors That Will Kill Your Network

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

How to Verify the Creation of SRV Records for a Domain Controller

How Domain Controllers Are Located in Windows

How Domain Controllers Are Located in Windows XP

SRV Resource Records May Not Be Created on Domain Controller

HOW TO: Configure DNS for Internet Access in Windows Server 2003

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows Server 2003

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gpsocsAuthor Commented:
The DHCP lease is coming from the belkin router, yes, however I have static domains assigned so that it points to the Windows 2003 PDC first since it is running DNS.  Perhaps I need to remove the secondary ISP NS server though from that?  Are one of the links that you posted inclusive of fowarder setup?
You definitely need to remove the ISP's address from any domain member.
For the forwarder setup, just right-click your DNS server in the DNS MMC, open the Properties, and enter your ISP's DNS(s) in the forwarders tab.
If you can't access anything in the Forwarders tab, go to your forward lookup zones and delete the root zone (the single dot, "."). The forwarders will then be available.
Exploring SharePoint 2016

Explore SharePoint 2016, the web-based, collaborative platform that integrates with Microsoft Office to provide intranets, secure document management, and collaboration so you can develop your online and offline capabilities.

Right best way to do this is have your ISP DNS addresses setup in DNS on your server as forwarders.
Then only have the network servers DNS IP address on your network, this means they look at the server for everything and no confusion with other DNS.
If you still have problems try deleting the computer from the domain and re-joining, could be a problem with the computer account
gpsocsAuthor Commented:
Thanks much to the both of you.  I think that that will do the trick.  I am not at the site at the moment to actually do this, but went ahead and accepted it as it appears to be in the right vein.  I will reply if there are more issues or create a new question so that I can award points again and link it to this.

We did get it back up earlier but authentication is taking a long time so I think that the fellow who was doing the work simply forgot to assign static dns server entries for the workstations plus the above sounds like it will get things working "properly."

Long logon times are another symptom of an incorrect DNS configuration. These should disappear as well once you're only using your internal DNS.
Windows 2000 and later will register themselves in DNS by default, so there's nothing to be done there.
And just to be sure, check whether your forward (and reverse) lookup zones allow dynamic updates; if not, enable it (right-click the zone, choose Properties).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.