IP address is already assigned to another adaptor (legacy one)

[BertieBigBollox]

Get this message when assigning an IP address to a network adaptor.
The error message says it could be due to a legacy adaptor or one that
is not phyically present.

I've got a feeling this may have been a previous network adaptor. It
looks like windows still has some remnants of this in there.

Been having serious problems trying to use lanman to mount shares on
this machine. Its absoultely refusing to allow server validation as a
PDC. I'm wondering if its connected to this.

Theres nothing in device manager for this network adaptor. How do I
clear out any old stuff that is possibly causing confusion here?

 

[Pegasus [MVP]]

"(e-mail address removed)" <[email protected]> said this in news
item

Get this message when assigning an IP address to a network adaptor.
The error message says it could be due to a legacy adaptor or one that
is not phyically present.

I've got a feeling this may have been a previous network adaptor. It
looks like windows still has some remnants of this in there.

Been having serious problems trying to use lanman to mount shares on
this machine. Its absoultely refusing to allow server validation as a
PDC. I'm wondering if its connected to this.

Theres nothing in device manager for this network adaptor. How do I
clear out any old stuff that is possibly causing confusion here?

Sorry, your problem is not caused by this particular issue. I've had
deactivated or non-present adapters for years and I see this message
frequently while performing some tests. I has no ill effects.

How exactly to you mount shares? What OS do you run? What OS does the
machine run that hosts the shared folder? What is the error message you see?
Verbatim, please!

 

[pimpom]

Get this message when assigning an IP address to a network
adaptor.
The error message says it could be due to a legacy adaptor or
one that
is not phyically present.

I've got a feeling this may have been a previous network
adaptor. It
looks like windows still has some remnants of this in there.

Been having serious problems trying to use lanman to mount
shares on
this machine. Its absoultely refusing to allow server
validation as a
PDC. I'm wondering if its connected to this.

Theres nothing in device manager for this network adaptor. How
do I
clear out any old stuff that is possibly causing confusion
here?

I'd like to know about this too because I encountered a similar
problem some time ago. In my case, it was only a minor annoyance
as it's a simple P2P home network, and I solved the problem
simply by assigning a different IP address.

I installed a 10/100 mbps card in addition to the onboard one and
assigned a static IP address, but the computer remembered that
address even after I'd physically removed the card and wouldn't
let me use it for the onboard unit.

It may come in handy in the future to know how to free up the
previous IP address. Edit registry? Can't try that now as I
reinstalled my OS some time ago.

 

[John Holmes]

(e-mail address removed) "contributed" in 24hoursupport.helpdesk:

Get this message when assigning an IP address to a network adaptor.
The error message says it could be due to a legacy adaptor or one that
is not phyically present.

I've got a feeling this may have been a previous network adaptor. It
looks like windows still has some remnants of this in there.

Been having serious problems trying to use lanman to mount shares on
this machine. Its absoultely refusing to allow server validation as a
PDC. I'm wondering if its connected to this.

Theres nothing in device manager for this network adaptor. How do I
clear out any old stuff that is possibly causing confusion here?

Assuming you are running a server OS (you mentioned a PDC), read this:

http://support.microsoft.com/kb/325356

 

[BertieBigBollox]

Sorry, your problem is not caused by this particular issue. I've had
deactivated or non-present adapters for years and I see this message
frequently while performing some tests. I has no ill effects.

How exactly to you mount shares? What OS do you run? What OS does the
machine run that hosts the shared folder? What is the error message you see?
Verbatim, please!

Boot laptop from DOS floppy. Server is running Windows 2000 server
SP4. Folders are shared.

Error message I get is - You are logged on but have not been validated
by a server. etc etc.

Then a net use of \\servername\share fails.

I've got another server which is identical (but different hardware).
What we are in the process of doing is moving the server and config
etc onto newer hardware. We've achieved this so far using ghost,
replacing default ide drivers etc.Its worked for the most part apart
from this problem.

And, before you ask, there is a reason we didnt just do a fresh
install . These are old legacy servers with applications loaded
with certain settings, os clamped down a certain way etc (and all
undocumented) so we really want to preserve what we had.

With regards to the IP address clash - are you saying that its ok to
ignore this and that it wont make any difference?

 

[BertieBigBollox]

(e-mail address removed) "contributed" in 24hoursupport.helpdesk:





Assuming you are running a server OS (you mentioned a PDC), read this:

http://support.microsoft.com/kb/325356

Hmmm. Interesting...

 

[Tim Jackson]

Get this message when assigning an IP address to a network adaptor.
The error message says it could be due to a legacy adaptor or one that
is not phyically present.

I've got a feeling this may have been a previous network adaptor. It
looks like windows still has some remnants of this in there.

Been having serious problems trying to use lanman to mount shares on
this machine. Its absoultely refusing to allow server validation as a
PDC. I'm wondering if its connected to this.

Theres nothing in device manager for this network adaptor. How do I
clear out any old stuff that is possibly causing confusion here?

For your IP address problem, have a look at this KB article

http://support.microsoft.com/kb/269155/en-us

 

[BertieBigBollox]

For your IP address problem, have a look at this KB article

http://support.microsoft.com/kb/269155/en-us

WIndows 2000 not 2003.

 

[BertieBigBollox]

Sorry, your problem is not caused by this particular issue. I've had
deactivated or non-present adapters for years and I see this message
frequently while performing some tests. I has no ill effects.

How exactly to you mount shares? What OS do you run? What OS does the
machine run that hosts the shared folder? What is the error message you see?
Verbatim, please!

Error message when attempting access shares (NET USE) is
Error 53: The computer name specified in the network path cannot be
located

 

[Tim Jackson]

WIndows 2000 not 2003.

This KB article is valid for 2000, 2003, XP and 2008.

 

[Pegasus [MVP]]

"(e-mail address removed)" <[email protected]> said this in news
item

Error message when attempting access shares (NET USE) is
Error 53: The computer name specified in the network path cannot be
located

You now need to perform the usual tests:
- Can you ping the machine by name? by IP address?
- Can you connect to the share by IP address?
- Are your IP settings correct? Did you examine the output of ipconfig /all
in detail?
- Does the problem persist while in Safe Mode with networking?
- Are these ordinary shares or administrative shares, e.g. c$?
- Does the problem persist while your firewalls are deactivated?

 

[BertieBigBollox]

"(e-mail address removed)" <[email protected]> said this in news
item






You now need to perform the usual tests:
- Can you ping the machine by name? by IP address?

By name - NO, By IP - YES

- Can you connect to the share by IP address?

NO, same error.

- Are your IP settings correct? Did you examine the output of ipconfig /all
in detail?

YES. Works fine on other server.

- Does the problem persist while in Safe Mode with networking?

Will try this.

- Are these ordinary shares or administrative shares, e.g. c$? ORDINARY.

- Does the problem persist while your firewalls are deactivated?- Hide quoted text -

Will try this.

 

[BertieBigBollox]

Further detailed info:

IP address is 10.1.99.7 (255.255.255.192) and gateway is 10.1.99.10.
10.1.99.10 is windows 2000 server with shares on.

From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.

However, if I do :-
NET USE \\PXE-SERVER\SHARE1
or NET USE \\10.1.99.10\SHARE1

I get ERROR 53-Computer name specified in the network path cannot be
found.

How can this be? I've specified an IP address?

 

[BertieBigBollox]

"(e-mail address removed)" <[email protected]> said this in news
item






You now need to perform the usual tests:
- Can you ping the machine by name? by IP address?
- Can you connect to the share by IP address?
- Are your IP settings correct? Did you examine the output of ipconfig /all
in detail?
- Does the problem persist while in Safe Mode with networking?
- Are these ordinary shares or administrative shares, e.g. c$?
- Does the problem persist while your firewalls are deactivated?- Hide quoted text -

- Show quoted text -

No firewall and Safe mode with networking is same.

It looks like the requests are not even getting to the file server.
When I net logon I get loggesd but not authenticated which implies it
cant contact a server.

Also, net view etc gives me nothing. Even though I can ping the ip
address.

I'm beginning to wonder if its a network card problem? (our other
server uses an older network card which works ok).

 

[Pegasus [MVP]]

"(e-mail address removed)" <[email protected]> said this in news
item

Further detailed info:

IP address is 10.1.99.7 (255.255.255.192) and gateway is 10.1.99.10.
10.1.99.10 is windows 2000 server with shares on.

From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.

However, if I do :-
NET USE \\PXE-SERVER\SHARE1
or NET USE \\10.1.99.10\SHARE1

I get ERROR 53-Computer name specified in the network path cannot be
found.

How can this be? I've specified an IP address?

My knowledge about the more involved details of networking does not go very
deep but here are a few notes that should explain the apparent discrepancy
you observe:

DNS and WINS are really two completely different name resolution methods.
DNS (Domain Name System) "maps" host names to IP Addresses. This allows you
to ping yahoo.com as opposed to its IP Address.

WINS (Windows Internet Naming Service) "maps" Netbios names to IP Addresses.
This allows you to type "net use \\server\c$".

Each name resolution methods can utilize a static text file: lmhosts for
WINS and hosts for DNS. Both reside in c:\Windows\System32\drivers\etc.

I would highly reccomend that you search through technet on Microsoft's
website. You should find numerous white papers that explain the differences
between WINS and DNS, e.g. this one: Setting up a Win2000 DNS Server:
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

 

[BertieBigBollox]

My knowledge about the more involved details of networking does not go very
deep but here are a few notes that should explain the apparent discrepancy
you observe:

DNS and WINS are really two completely different name resolution methods.
DNS (Domain Name System) "maps" host names to IP Addresses. This allows you
to ping yahoo.com as opposed to its IP Address.

WINS (Windows Internet Naming Service) "maps" Netbios names to IP Addresses.
This allows you to type "net use \\server\c$".

Each name resolution methods can utilize a static text file: lmhosts for
WINS and hosts for DNS. Both reside in c:\Windows\System32\drivers\etc.

I would highly reccomend that you search through technet on Microsoft's
website. You should find numerous white papers that explain the differences
between WINS and DNS, e.g. this one: Setting up a Win2000 DNS Server:http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Had Netbios over TCP/IP enabled before.

However, just installed Netbeui on server and set client to run
netbeui and it now works?

Weird. Is it possible the new server ethernet card just doesnt like
netbios over tcpip?