edli83
asked on
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?
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?
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)
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)
ASKER
client computer name: np02
server domain name: nextpart.local
server domain name: nextpart.local
ASKER
I guess it must be the way SBS is setup?
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
check the dns settings on the workstation
the ONLY dns that should be there, is the inside ip address of the sbs server
ASKER
can you explain in more detail bryon?
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
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
ASKER
this is what i am getting at the moment, it looks fine?
Screen-shot-2010-04-28-at-15.22..png
Screen-shot-2010-04-28-at-15.22..png
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
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
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
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
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
but on the xp workstation, that's where you need to check the dns settings
ASKER
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
Apologies, this has been driving me mad today!
workstation.JPG
yep the workstation has what it needs... how about the netbios/wins settings on the server?
ASKER
Ok so I've removed the WINS and also enabled netbios
When trying to join now i get the following.
namechanges.JPG
When trying to join now i get the following.
namechanges.JPG
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
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
ASKER
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
The computer is called NEXTPART, i've attached another screenie of the server.
Screen-shot-2010-04-28-at-16.07..png
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\driver s\etc\host s
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
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\driver
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
ASKER
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?
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?
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
Simplest thing to do is to rename the computer
ASKER
i've just renamed and restarted the server but I am getting the same results.... what else can we try?
what is the exact error message you're getting after the rename?
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
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
ASKER
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
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
\\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
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
@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.
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.
@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?
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?
ASKER
I will try your suggesstions tomorrow when I get back into the office.
I appreciate the help so far, thanks!
I appreciate the help so far, thanks!
ASKER
so i've just tried to join the domain and I get the following:
namechanges2.JPG
namechanges2.JPG
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?
go to the server, and do start > run > \\localhost
do you see a SYSVOL share there?
Have you removed the stuff from the hosts file ?
ASKER
@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....
@bryon4403 - I only have Windows Firewall which I have turned off on both, the router has a firewall though....
ASKER
dont know if this helps?
dcdiag.txt
dcdiag.txt
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
on the server itself. seems like at this point we might be facing an active directory issue
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?
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?
ASKER
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?
When you say join it to the WORKGROUP, is it not part of WORKGROUP already? what do you mean?
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?
in active directory users and computers on the server, in the computers OU, do you see this computer name in there?
ASKER
i dont see any objects in the computer tab...
ASKER
again i dont know if this helps...
logfile.txt
logfile.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i've reformatted and it now joins the domain instantly.
i do have some other problems though....
thanks for the help
i do have some other problems though....
thanks for the help
http://support.microsoft.com/kb/909264