Cannot Rename Client Machines... locally or remotely (on domain)

[AdamD.]

Hello,

Got a strange issue:

The company where I work had no consistent naming scheme before I got
here, so as part of a hardware audit I'm also renaming all of the PCs. There
are a few machines who refuse to be renamed either locally, or remotely
through netdom. When trying to do it remotely I get:

"Unable to connect to the computer [computer-name]
The error code is 51.
Windows cannot find the network path. Verify that the network path is
correct and the destination computer is not busy or turned off. If Windows
still cannot find the network path, contact your network administrator.
The command failed to complete successfully."

If I try to rename it locally, I get:

"Multiple connections to a server or shared resource, by more than one
user, are not allowed. Please disconnect..."

I thought it might be DCOM or RPC services not running, but that is not
case, both and dependencies are up and running. Windows Firewall is not
turned on. In addition, I can't browse to their machines and view any shares
when connecting with \\computername\, I get:

"\\computername
The network path was not found."

I'm pulling my hair out, and I can't figure this out. Anyone have any
suggestions?


Thanks in advance,

AdamD.

[Pegasus \(MVP\)]

"AdamD." <adam.difrischia@forms-surfaces(dot).com> wrote in message
news:el%236Fi9HJHA.4240@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> Got a strange issue:
>
> The company where I work had no consistent naming scheme before I got
> here, so as part of a hardware audit I'm also renaming all of the PCs.
> There are a few machines who refuse to be renamed either locally, or
> remotely through netdom. When trying to do it remotely I get:
>
> "Unable to connect to the computer [computer-name]
> The error code is 51.
> Windows cannot find the network path. Verify that the network path is
> correct and the destination computer is not busy or turned off. If Windows
> still cannot find the network path, contact your network administrator.
> The command failed to complete successfully."
>
> If I try to rename it locally, I get:
>
> "Multiple connections to a server or shared resource, by more than one
> user, are not allowed. Please disconnect..."
>
> I thought it might be DCOM or RPC services not running, but that is not
> case, both and dependencies are up and running. Windows Firewall is not
> turned on. In addition, I can't browse to their machines and view any
> shares when connecting with \\computername\, I get:
>
> "\\computername
> The network path was not found."
>
> I'm pulling my hair out, and I can't figure this out. Anyone have any
> suggestions?
>
>
> Thanks in advance,
>
> AdamD.

When you rename a machine locally then you MUST disconnect all existing
network connections. This is what the message "Multiple connections to a
server or shared resource, by more than one user, are not allowed. Please
disconnect..." is trying to tell you. Run "net use" from the Command Prompt
to view your existing connections.

[Mike Cordares]

Hello Adam,


AdamD. wrote:

> "Unable to connect to the computer [computer-name]
> The error code is 51.

Double check DNS and/or WINS. Most common this is a name resolution issue.

>
> If I try to rename it locally, I get:
>
> "Multiple connections to a server or shared resource, by more than one
> user, are not allowed. Please disconnect..."

You are alreday connected to the Server with anouther username.
Check the output of "net use".

If there are already connected ressources, you can delete them with
"net use /delete *"
Then you schould be able to rename the computer locally.

Mike

[AdamD.]

I think this goes way beyond any of those; I renamed about 99% of the
computers just fine with the same mapped network drives.

Name resolution isn't an issue, all 3 DNS servers resolve the computer just
fine to IP, and back again.

Another thing I could mention that I forgot to, is that I'm also unable to
connect to the machine to launch a program like PSExec. I thought it might
be lack of Domain Admins as local Administrators, but that is intact.

Thanks for the suggestions though, much appreciated. Those were suggested
yesterday in IRC and that didn't work.

I was successfully able to rename one of the machines by dropping it off of
the domain, renaming it, and then rejoining it. However, it's still suspect
to the same issues - I tried renaming it with netdom, and I get the same
errors, still can't browse shares, etc.

I'm thinking something may be corrupted on their end... with networking
perhaps?

-- AdamD.


"Mike Cordares" <Mike_Cordares@abando.de> wrote in message
news:gbinfa$2dh$03$1@news.t-online.com...
> Hello Adam,
>
>
> AdamD. wrote:
>
>> "Unable to connect to the computer [computer-name]
>> The error code is 51.
>
> Double check DNS and/or WINS. Most common this is a name resolution issue.
>
>>
>> If I try to rename it locally, I get:
>>
>> "Multiple connections to a server or shared resource, by more than
>> one
>> user, are not allowed. Please disconnect..."
>
> You are alreday connected to the Server with anouther username.
> Check the output of "net use".
>
> If there are already connected ressources, you can delete them with
> "net use /delete *"
> Then you schould be able to rename the computer locally.
>
> Mike

[Lanwench [MVP - Exchange]]

AdamD. <adam.difrischia@forms-surfaces(dot).com> wrote:
> I think this goes way beyond any of those; I renamed about 99% of the
> computers just fine with the same mapped network drives.

Regardless, that's the meaning of the message you quoted. Have you tried net
use * /del ?
>
> Name resolution isn't an issue, all 3 DNS servers resolve the
> computer just fine to IP, and back again.

You might post an unedited ipconfig /all from a problem client & from a DC.
>
> Another thing I could mention that I forgot to, is that I'm also
> unable to connect to the machine to launch a program like PSExec. I
> thought it might be lack of Domain Admins as local Administrators,
> but that is intact.

What security software/firewall apps are running?
>
> Thanks for the suggestions though, much appreciated. Those were
> suggested yesterday in IRC and that didn't work.
>
> I was successfully able to rename one of the machines by dropping it
> off of the domain, renaming it, and then rejoining it. However, it's
> still suspect to the same issues - I tried renaming it with netdom,
> and I get the same errors, still can't browse shares, etc.
>
> I'm thinking something may be corrupted on their end... with
> networking perhaps?

Event logs should help you sort that out...
>
> -- AdamD.
>
>
> "Mike Cordares" <Mike_Cordares@abando.de> wrote in message
> news:gbinfa$2dh$03$1@news.t-online.com...
>> Hello Adam,
>>
>>
>> AdamD. wrote:
>>
>>> "Unable to connect to the computer [computer-name]
>>> The error code is 51.
>>
>> Double check DNS and/or WINS. Most common this is a name resolution
>> issue.
>>>
>>> If I try to rename it locally, I get:
>>>
>>> "Multiple connections to a server or shared resource, by more
>>> than one
>>> user, are not allowed. Please disconnect..."
>>
>> You are alreday connected to the Server with anouther username.
>> Check the output of "net use".
>>
>> If there are already connected ressources, you can delete them with
>> "net use /delete *"
>> Then you schould be able to rename the computer locally.
>>
>> Mike

[AdamD.]

In-line below

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:usDI099HJHA.4600@TK2MSFTNGP06.phx.gbl...
> AdamD. <adam.difrischia@forms-surfaces(dot).com> wrote:
>> I think this goes way beyond any of those; I renamed about 99% of the
>> computers just fine with the same mapped network drives.
>
> Regardless, that's the meaning of the message you quoted. Have you tried
> net use * /del ?

Yes, that was suggested yesterday in IRC, and since nothing else had worked,
I tried it, to no avail.

>>
>> Name resolution isn't an issue, all 3 DNS servers resolve the
>> computer just fine to IP, and back again.
>
> You might post an unedited ipconfig /all from a problem client & from a
> DC.

From computer (only edited to remove names):
Windows IP Configuration

Host Name . . . . . . . . . . . . : COMPUTER-NAME
Primary Dns Suffix . . . . . . . : domain-name.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain-name.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain-name.local
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
Controller
Physical Address. . . . . . . . . : 00-13-72-19-6A-A0
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.12.86
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.12.1
DHCP Server . . . . . . . . . . . : 10.10.10.31
DNS Servers . . . . . . . . . . . : 10.10.10.31
10.10.10.32
Lease Obtained. . . . . . . . . . : Friday, September 26, 2008
6:51:31 AM
Lease Expires . . . . . . . . . . : Saturday, October 04, 2008
6:51:31 AM

From DC (same editing):
Windows IP Configuration

Host Name . . . . . . . . . . . . : dcname
Primary Dns Suffix . . . . . . . : domain-name.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain-name.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE
(NDIS
VBD Client)
Physical Address. . . . . . . . . : 00-1D-09-6A-39-D3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.31
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.1
DNS Servers . . . . . . . . . . . : 10.10.10.31
10.10.10.32

>>
>> Another thing I could mention that I forgot to, is that I'm also
>> unable to connect to the machine to launch a program like PSExec. I
>> thought it might be lack of Domain Admins as local Administrators,
>> but that is intact.
>
> What security software/firewall apps are running?

There are none that I am aware of; Windows Firewall is not enabled on either
machine, and there are no hardware firewalls that sit between them.

>>
>> Thanks for the suggestions though, much appreciated. Those were
>> suggested yesterday in IRC and that didn't work.
>>
>> I was successfully able to rename one of the machines by dropping it
>> off of the domain, renaming it, and then rejoining it. However, it's
>> still suspect to the same issues - I tried renaming it with netdom,
>> and I get the same errors, still can't browse shares, etc.
>>
>> I'm thinking something may be corrupted on their end... with
>> networking perhaps?
>
> Event logs should help you sort that out...
>>
>> -- AdamD.
>>
>>
>> "Mike Cordares" <Mike_Cordares@abando.de> wrote in message
>> news:gbinfa$2dh$03$1@news.t-online.com...
>>> Hello Adam,
>>>
>>>
>>> AdamD. wrote:
>>>
>>>> "Unable to connect to the computer [computer-name]
>>>> The error code is 51.
>>>
>>> Double check DNS and/or WINS. Most common this is a name resolution
>>> issue.
>>>>
>>>> If I try to rename it locally, I get:
>>>>
>>>> "Multiple connections to a server or shared resource, by more
>>>> than one
>>>> user, are not allowed. Please disconnect..."
>>>
>>> You are alreday connected to the Server with anouther username.
>>> Check the output of "net use".
>>>
>>> If there are already connected ressources, you can delete them with
>>> "net use /delete *"
>>> Then you schould be able to rename the computer locally.
>>>
>>> Mike
>
>
>

[Pegasus \(MVP\)]

"AdamD." <adam.difrischia@forms-surfaces(dot).com> wrote in message
news:e3FNgb%23HJHA.2580@TK2MSFTNGP05.phx.gbl...
> In-line below
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
> message news:usDI099HJHA.4600@TK2MSFTNGP06.phx.gbl...
>> AdamD. <adam.difrischia@forms-surfaces(dot).com> wrote:
>>> I think this goes way beyond any of those; I renamed about 99% of the
>>> computers just fine with the same mapped network drives.
>>
>> Regardless, that's the meaning of the message you quoted. Have you tried
>> net use * /del ?
>
> Yes, that was suggested yesterday in IRC, and since nothing else had
> worked, I tried it, to no avail.

It is not sufficient to just knock out all existing connections - you must
then check if any of them still hang about. This command will tell you:

net use

[AdamD.]

I still don't get it... went down to that machine today that was giving me
trouble. Was going to try the net use /delete * command and make sure no
lingering connects. Before trying that just to make sure it wouldn't rename
I tried it... dang thing renamed no problem, mapped drives and all.

I don't get it, but thanks anyways for your suggestions.

AD

"AdamD." <adam.difrischia@forms-surfaces(dot).com> wrote in message
news:el%236Fi9HJHA.4240@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> Got a strange issue:
>
> The company where I work had no consistent naming scheme before I got
> here, so as part of a hardware audit I'm also renaming all of the PCs.
> There are a few machines who refuse to be renamed either locally, or
> remotely through netdom. When trying to do it remotely I get:
>
> "Unable to connect to the computer [computer-name]
> The error code is 51.
> Windows cannot find the network path. Verify that the network path is
> correct and the destination computer is not busy or turned off. If Windows
> still cannot find the network path, contact your network administrator.
> The command failed to complete successfully."
>
> If I try to rename it locally, I get:
>
> "Multiple connections to a server or shared resource, by more than one
> user, are not allowed. Please disconnect..."
>
> I thought it might be DCOM or RPC services not running, but that is not
> case, both and dependencies are up and running. Windows Firewall is not
> turned on. In addition, I can't browse to their machines and view any
> shares when connecting with \\computername\, I get:
>
> "\\computername
> The network path was not found."
>
> I'm pulling my hair out, and I can't figure this out. Anyone have any
> suggestions?
>
>
> Thanks in advance,
>
> AdamD.
>

[Pegasus \(MVP\)]

"AdamD." <adam.difrischia@forms-surfaces(dot).com> wrote in message
news:OReCTUBIJHA.788@TK2MSFTNGP06.phx.gbl...
>I still don't get it... went down to that machine today that was giving me
>trouble. Was going to try the net use /delete * command and make sure no
>lingering connects. Before trying that just to make sure it wouldn't rename
>I tried it... dang thing renamed no problem, mapped drives and all.
>
> I don't get it, but thanks anyways for your suggestions.
>
> AD
>

This happened because the drives were mapped under the same credentials as
the ones you used to change the machine name.

[AdamD.]

Actually, no. When I did change the computers name, all the mapped drives
were still there. And, you're insinuating that the drives are mapped using
my credentials, since those are what I was using to change the name. This is
incorrect; the drives are mapped via login script using the local
credentials of the user logging in. Ergo, the drives were mapped under that
users username, and I was changing them with mine. Two different names.

This is still an issue on a few other machines and I still can't figure it
out. We've got an asset scanning script that also has trouble gathering
remote WMI information or accessing their registries remotely on the same
machines, so I'm beginning to think it's something to do with some
underlying Microsoft networking thing, but I have no idea what it could be.

AD


"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:eLbzflBIJHA.788@TK2MSFTNGP06.phx.gbl...
>
> "AdamD." <adam.difrischia@forms-surfaces(dot).com> wrote in message
> news:OReCTUBIJHA.788@TK2MSFTNGP06.phx.gbl...
>>I still don't get it... went down to that machine today that was giving me
>>trouble. Was going to try the net use /delete * command and make sure no
>>lingering connects. Before trying that just to make sure it wouldn't
>>rename I tried it... dang thing renamed no problem, mapped drives and all.
>>
>> I don't get it, but thanks anyways for your suggestions.
>>
>> AD
>>
>
> This happened because the drives were mapped under the same credentials as
> the ones you used to change the machine name.
>