asked on

Connecting PC to Server 2003 domain

Just setup a new server with SBS 2003 and we're trying to connect PC's to the domain. When trying to connect we get a login prompt to connect to the domain and login as administrator (or any user for sake of argument). When it tries to connect to the domain we get the following error message "The format of the specified network name is invalid". We're moving from a workgroup to a domain and the PC's have never been connected to another domain. We're using the fully qualified domain name and the computer name has no special characters (I.E. glentry). I can communicate (ping) the domain with no problems. There's no computers currently setup on the domain so there's no chance for duplicate computer names. The computer in question is XP SP2, however I've tried the same thing on a Win2000 box with similiar results. I found one other response online which suggestions I've followed with no luck. Not sure what's going on...

Ron Malmstead

When you attempt to join the domain name ...try using the netbios domain name....instead of yourdomain.com...that's the name in the drop down box when you logon to the server.

Login with this format: Domain\administrator
Password

If that doesn't work you may have a dns problem.

2hype

Ensure your DNS IP address on your clients are set to your SBS Server. Otherwise you will have problems joining the domain and login's will be slow.

ctfisher

was going to make 2hype's point, what is the fully qualified domain name in question?

119support

what is your domain name?
SBS is a huge pain in the butt as everything has to be configured a specific way.

CSTRAUGHN

ASKER

domain name is formatted as follows:

headquarters.<8 chars>.com (I.E. headquarters.companyx.com).

Will try the netbios domain name...Thanks

119support

i think, the ".com" is causing your problem especially if your DNS is AD integrated.

ctfisher

Tip: NEVER use *.com as your FQDN as it will cause you all manner of troubles resolving it (eg subdomains of it, such as www. are somewhere else on the internet, so despite the fact your AD controller believes it can name serve in the companyx.com domain, it actually can't (you'll need to set an A-Name entry in DNS if you want users within your domain to access something.yourdomain.com if it's located outside your network (like 3rd party hosted web server, etc..)

yourdomain.local is far, far easier..

beaconlightboy

we use .org and have no problems with it. Our internal DNS servers think they are the primaries for the domain, which they are, for the inside, but outside they are not, and we don't allow DNS in thru the firewall. It does make those external DNS servers a bit cranky when they try to sync, but oh well.

just setup your domain controller as a DNS server for your companyname.com and point your workstations DNS settings to that server. that should do it. just make sure you install root hints on that internal DNS server so your stations can get to the internet.

ctfisher

Or that of course...

CSTRAUGHN

ASKER

I did some more research on this one based off the information you guys provided. We're setting this up similiar to another site that we setup a while back and trying to mirror the sites a close as possible. Here's what I've found:

1. Tried netbois name, couldn't connect using netbios name at all. Can ping the NETBIOS name with no problem.

2. Domain controller is setup as the DNS server and the workstations are pointing to it.

2. I'm now able to get PC's to connect (using FQDN) to the domain but only if I reboot the server (maybe a service going down)? I can get PC's to connect to the domain, come back the next day and get the same error message as before? I looked in the event viewer and didn't see an services that had stopped? Any Ideas what could be causing an intermitent problem like that? If it were DNS wouldn't it be a consistant problem? Also once I'm initially connected to the domain on a computer I can login to it with no problem even if I can't connect to the domain from another PC.

3. Just a note when the problem occurs and I'm trying to connect from a Win2K machine I get one of the following messages:

"The network path was not found"
"The remote computer is not available"

Again once I reboot the server I'm able to connect to the domain.

beaconlightboy

Ok, lets check something else. does your 2003 server have SP1 installed. There are known issues with SP1 and client connectivity. I'm not at my office so i can't get you the article number. if you do have SP1, i'll look up the article that solved a similar problem for me.

CSTRAUGHN

ASKER

I do have SP1 installed, I'll search as well...Thanks

SOLUTION

2hype

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CSTRAUGHN

ASKER

Should I uninstlall Server 2003 SP1 and wait for SBS 2003 SP1 to come out? Does it cause enough issues where it's not worth having it on there?

ASKER CERTIFIED SOLUTION

beaconlightboy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CSTRAUGHN

ASKER

I believe I know what the problem was, I'll follow-up this afternoon after I verify...Thanks

beaconlightboy

interested to find out what the culprut is.

CSTRAUGHN

ASKER

I'm almost embarrased to say what the problem was, "File and Print Sharing" on the network interface was turned off. I'm not sure why the problem only presented itself after the server had been up for 15 to 20 minutes? I do know that as soon as I turned "File and Print Sharing" on all the problems went away. I really appreciate all of your helpful suggestions/comments. "beaconlightboy" and "2hype" really stuck in their and gave some great suggestsions/answers, I rewarded the points to them.

God Bless