The format of the specified network name is invalid

Hi,

I am trying to add a new Windows XP Pro machine to my network (SBS 2003)

I am getting the following message when I triy to add it to the domain: The format of the specified network name is invalid

Can anyone help?
edli83Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Danny ChildIT ManagerCommented:
would you be using any illegal characters as per this? -

http://support.microsoft.com/kb/909264
0
Brian PiercePhotographerCommented:
and the domain name is ?

It should be a two part name eg mydomain.suffix

To be safe make sure its only got alphanumeric characters (no spaces or punctuation other thasn the one period)
0
edli83Author Commented:
client computer name: np02
server domain name: nextpart.local
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

edli83Author Commented:
I guess it must be the way SBS is setup?
0
B HCommented:
there's nothing wrong with the domain name

check the dns settings on the workstation
the ONLY dns that should be there, is the inside ip address of the sbs server
0
edli83Author Commented:
can you explain in more detail bryon?
0
B HCommented:
if the workstation has random dns settings on it's network card properties, like those of your internet provider, it will not properly find the domain you want.

to verify:
start > run > cmd
ipconfig /all
what does it say for "dns servers" ?  it should ONLY have the ip address of your server.

if it has anything else at all, do this:
start > control panel > network connections
right-click local area connection, properties
double click TCP/IP
specify the dns servers at the bottom, have the top one be your server, and the bottom one be blank
0
edli83Author Commented:
this is what i am getting at the moment, it looks fine?
Screen-shot-2010-04-28-at-15.22..png
0
B HCommented:
um not really

why is your primary wins server an outside ip address, remove that
also enable netbios over tcpip

both can be done in the same place i mentioned above, tcpip properties, advanced
there's various tabs at the top, 2 have the settings you need to change
0
B HCommented:
wait one more thing....

you have this machine 192.168.2.2
and you have it's dns server as 192.168.2.2

it can't be its own dns server unless it IS the server... if that screenshot is from a workstation, you have the wrong dns in there
0
B HCommented:
if that screenshot is from the server, you still need to enable netbios and get rid of the random wins address...
but on the xp workstation, that's where you need to check the dns settings
0
edli83Author Commented:
oops my mistake, i thought u asked me to check the server, let me check the workstation.
Apologies, this has been driving me mad today!
workstation.JPG
0
B HCommented:
yep the workstation has what it needs...  how about the netbios/wins settings on the server?
0
edli83Author Commented:
Ok so I've removed the WINS and also enabled netbios

When trying to join now i get the following.
namechanges.JPG
0
B HCommented:
ok so on the workstation, when you do this:
start > run >  \\nextpart.local
what happens?

in dos,
ping nextpart.local
what happens?  it should resolve to 192.168.2.2
ping nextpart.local
what happens?  it should resolve to 192.168.2.2

is there some computer called NEXTPART  (just like that?)
if you have a computer called nextpart, and a domain called nextpart.local, all kinds of bad things happen
0
edli83Author Commented:
im getting Network path not found and ping request could not find host

The computer is called NEXTPART, i've attached another screenie of the server.
Screen-shot-2010-04-28-at-16.07..png
0
B HCommented:
oh wow - have you added any workstations to this domain?

see, the netbios name of the domain is "nextpart"... and the server's name is "nextpart"... that might cause some trouble there...

on the workstation, do this
start > run > notepad c:\windows\system32\drivers\etc\hosts

add a line at the bottom that says these things:

192.168.2.2   nextpart
192.168.2.2.  nextpart.nextpart.local
192.168.2.2   nextpart.local

file, save

start > run > cmd
ipconfig /flushdns
ipconfig /registerdns

try again

if you're just starting this whole thing, and nothing has been set up yet, you might consider blowing it up and renaming the server to something like nextpartsrv or nextsrv... so it's different than the domain name
0
edli83Author Commented:
This is the first workstation, before this we were predominantly using RDP via laptops.

start > run >  \\nextpart.local - network path not found
ping nextpart.local - resolves to 192.168.2.2

I still cant join the domain.

What are your thoughts? Shall I just rename it? Is that most likely the problem?
0
Brian PiercePhotographerCommented:
I think the problem here is that the name of the machine and the name of the domain are the same in netbios terms. NETBIOS is refering to them both at NEXTPART, that explains why you can't browse to \\NEXTPART\share

Simplest thing to do is to rename the computer
0
edli83Author Commented:
i've just renamed and restarted the server but I am getting the same results.... what else can we try?
0
B HCommented:
what is the exact error message you're getting after the rename?
0
B HCommented:
please also do this as i asked above:

ok so on the workstation, when you do this:
start > run >  \\nextpart.local
what happens?

in dos,
ping nextpart.local
what happens?  it should resolve to 192.168.2.2
ping nextpart
what happens?  it should resolve to 192.168.2.2
ping thenewnameoftheserver
what happens?  it should resolve to 192.168.2.2
0
edli83Author Commented:
I am getting the same error message as before: "cannot find the network path"

start > run >  \\nextpart.local - network path not found

ping nextpart.local - resolves to 192.168.2.2

ping nextpartsvr - resolves to 192.168.2.2
0
Brian PiercePhotographerCommented:
\\nextpart.local is the domain -  so network path not found is to be expected

Remove the stuff that you were sdvised to add to the hosts file ie

192.168.2.2   nextpart
192.168.2.2.  nextpart.nextpart.local
192.168.2.2   nextpart.local

YOU DONT NEED THESE IN THE HOST FILE

0
B HCommented:
@kcts - the hosts file was for troubleshooting, obviously his netbios names and resolution are screwed up, a local hosts file ensures (for pinpointing) that he's talking to the domain controller

any workstation in a domain which has the dns server of the domain controller SHOULD be able to resolve the network path \\domain.name
it should resolve to the domain controller, and if it doesn't, i need to know that so we can go that route and find out why.

0
B HCommented:
@author, as it stands now, what happens when you try to join this workstation to the domain?

right-click my computer
properties
computer name
change
domain = your full domain (nextpart.local?)
ok
domain\administrator username and password if prompted

if you get an error message, can you post that screenshot?
0
edli83Author Commented:
I will try your suggesstions tomorrow when I get back into the office.
I appreciate the help so far, thanks!
0
edli83Author Commented:
so i've just tried to join the domain and I get the following:
namechanges2.JPG
0
B HCommented:
is there a firewall on the server, which might interfere with your workstation talking to it?

go to the server, and do start > run > \\localhost

do you see a SYSVOL share there?
0
Brian PiercePhotographerCommented:
Have you removed the stuff from the hosts file ?
0
edli83Author Commented:
@KCTS - i have tried both ways, should i leave it out from now on?

@bryon4403 - I only have Windows Firewall which I have turned off on both, the router has a firewall though....
0
edli83Author Commented:
dont know if this helps?
dcdiag.txt
0
B HCommented:
how about the sysvol share when doing \\localhost
on the server itself.  seems like at this point we might be facing an active directory issue
0
B HCommented:
hmm, nevermind that, AD appears to be fine (i posted that at the same time before i saw your dcdiag)

so......... is this workstation joined to a different domain, possibly one that doesn't exist anymore?

can you join it to the WORKGROUP workgroup, reboot, and try to join it to the domain?
0
edli83Author Commented:
the workstation is brand new and has never been joined to any other domain that I know of.

When you say join it to the WORKGROUP, is it not part of WORKGROUP already? what do you mean?
0
B HCommented:
i thought by your ipconfig /all above, you may have had it joined already to this domain, or another domain of the same name :/

in active directory users and computers on the server, in the computers OU, do you see this computer name in there?

0
edli83Author Commented:
i dont see any objects in the computer tab...
0
edli83Author Commented:
again i dont know if this helps...
logfile.txt
0
B HCommented:
yeah that for sure helps...

your dns settings for active directory are non-existent, and you're not sharing anything from the server (dont have the ability to)

on the server, can you do this:

control panel, network connections
right-click local area connection, properties
screenshot that please
0

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
edli83Author Commented:
i've reformatted and it now joins the domain instantly.
i do have some other problems though....
thanks for the help
0
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 Networking

From novice to tech pro — start learning today.