Duplicate IP Windows NT Server

I installed a new network card and switch on my server about 8 months
ago and since then I have been having problems with duplicate IP names.
There is no WINS manager on the server, although it is listed in
bindings and adapters etc under network properties. I rebooted one of
my workstations and it will not allow it on the server now. The
workstation says that the it cannot find the domain server or the
computer is now allowed access or some thing similiar. The event log on
the server says that the computer was not allowed on because of
duplicate ip addresses. The network is set up on static ip, so Iknow
what every computer's IP address is... That is why I said it is almost
like the IP address is cached on the server somewhere and it won't let
it on. How do I clear it or fix my problem?

What are the IP addresses? Please post the result of ipconfig /all.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
I installed a new network card and switch on my server about 8 months
ago and since then I have been having problems with duplicate IP names.
There is no WINS manager on the server, although it is listed in
bindings and adapters etc under network properties. I rebooted one of
my workstations and it will not allow it on the server now. The
workstation says that the it cannot find the domain server or the
computer is now allowed access or some thing similiar. The event log on
the server says that the computer was not allowed on because of
duplicate ip addresses. The network is set up on static ip, so Iknow
what every computer's IP address is... That is why I said it is almost
like the IP address is cached on the server somewhere and it won't let
it on. How do I clear it or fix my problem?

They are all static on my network. The IP address of the machine I am
having problems relogging onto the network is

IP Addy: 10.0.0.153
Subnet: Class C

and of course the gateway is 10.0.0.254 (internet gateway is primary
gateway) and server is 10.0.0.1 or 10.0.0.2.

I have started having these problems since I installed a new network
card and switch onto the server. I had to reinstall the card a few
times because it was not taking properly. From what I understand
clearing because the card was reinstalled I should clear the WINS to
fix it per most forums I have looked through, but I do not appear to
have WINS on this server.

I either need to figure out how to get this computer back onto the
network, OR I need to figure out how to be able to remote admin onto
another computer. I did the port forwarding on the router identical to
the ones that were working, but I cannot get any of the new computers I
added to the remote admin to be able to connect. I opened the proper
ports on the computers in question (winxp) turned off the firewalls and
tried again but the router is not sending it properly to the computer.
I know it works because I can remote admin into the computer if I'm
bypassing the router, but that doesnt help those who need to dial in.

Thanks, I'm just stumped at this point and we have several people who
rely on being able to remote into these stations and I'm now down to
zero machines that make it past the router AND connect properly to the
server

Misty


Robert L [MVP - Networking] wrote:
> What are the IP addresses? Please post the result of ipconfig /all.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
> I installed a new network card and switch on my server about 8 months
> ago and since then I have been having problems with duplicate IP names.
> There is no WINS manager on the server, although it is listed in
> bindings and adapters etc under network properties. I rebooted one of
> my workstations and it will not allow it on the server now. The
> workstation says that the it cannot find the domain server or the
> computer is now allowed access or some thing similiar. The event log on
> the server says that the computer was not allowed on because of
> duplicate ip addresses. The network is set up on static ip, so Iknow
> what every computer's IP address is... That is why I said it is almost
> like the IP address is cached on the server somewhere and it won't let
> it on. How do I clear it or fix my problem?

In news:(E-Mail Removed) ups.com,
(E-Mail Removed) <(E-Mail Removed)> typed:
> I installed a new network card and switch on my server about 8 months
> ago and since then I have been having problems with duplicate IP
> names. There is no WINS manager on the server, although it is listed
> in bindings and adapters etc under network properties. I rebooted one
> of my workstations and it will not allow it on the server now. The
> workstation says that the it cannot find the domain server or the
> computer is now allowed access or some thing similiar. The event log
> on the server says that the computer was not allowed on because of
> duplicate ip addresses. The network is set up on static ip, so Iknow
> what every computer's IP address is... That is why I said it is almost
> like the IP address is cached on the server somewhere and it won't let
> it on. How do I clear it or fix my problem?

You didn't post the ipconfig /all results as Robert asked, which would help
us diagnose the problem.

Since you're using static IPs, it's going to be a huge PITA to manage them -
why are you not using DHCP? Also - unless you're going to disable NetBIOS
over TCP/IP on all your machines, install and configure WINS.

We use static because there are only 30 clients, and it makes it easier
to remote into specific computers. Also I have very little time I can
have the server down so installing WINS on a server that has alot of
issues already I'm scared to damage what is left. Our controller won't
let me upgrade (I'm using NT that should explain alot there, as well as
an old old telrad server for phones). I'm trying to change little of
what was preset when I started here a year ago because they use a TON
of legacy software and equipment.

Here is the IP config all
Host Name . . . . . . . . . : remote1.ntdomain
DNS Servers . . . . . . . . : 64.89.74.2
64.89.70.2
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : Yes

0 Ethernet adapter :

Description . . . . . . . . : DAVICOM DM9102/A PCI Fast
Ethernet
dapter
Physical Address. . . . . . : 00-D0-09-06-BB-C1
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 10.0.0.153
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 10.0.0.254
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

Lanwench [MVP - Exchange] wrote:
> In news:(E-Mail Removed) ups.com,
> (E-Mail Removed) <(E-Mail Removed)> typed:
> > I installed a new network card and switch on my server about 8 months
> > ago and since then I have been having problems with duplicate IP
> > names. There is no WINS manager on the server, although it is listed
> > in bindings and adapters etc under network properties. I rebooted one
> > of my workstations and it will not allow it on the server now. The
> > workstation says that the it cannot find the domain server or the
> > computer is now allowed access or some thing similiar. The event log
> > on the server says that the computer was not allowed on because of
> > duplicate ip addresses. The network is set up on static ip, so Iknow
> > what every computer's IP address is... That is why I said it is almost
> > like the IP address is cached on the server somewhere and it won't let
> > it on. How do I clear it or fix my problem?
>
> You didn't post the ipconfig /all results as Robert asked, which would help
> us diagnose the problem.
>
> Since you're using static IPs, it's going to be a huge PITA to manage them -
> why are you not using DHCP? Also - unless you're going to disable NetBIOS
> over TCP/IP on all your machines, install and configure WINS.

Without the new NIC IP information, it is hard for us to determine the issue. Assuming this is multihomed computer, is it possible you have assign the same IP range in the new NIC?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Prov2" <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
They are all static on my network. The IP address of the machine I am
having problems relogging onto the network is

IP Addy: 10.0.0.153
Subnet: Class C

and of course the gateway is 10.0.0.254 (internet gateway is primary
gateway) and server is 10.0.0.1 or 10.0.0.2.

I have started having these problems since I installed a new network
card and switch onto the server. I had to reinstall the card a few
times because it was not taking properly. From what I understand
clearing because the card was reinstalled I should clear the WINS to
fix it per most forums I have looked through, but I do not appear to
have WINS on this server.

I either need to figure out how to get this computer back onto the
network, OR I need to figure out how to be able to remote admin onto
another computer. I did the port forwarding on the router identical to
the ones that were working, but I cannot get any of the new computers I
added to the remote admin to be able to connect. I opened the proper
ports on the computers in question (winxp) turned off the firewalls and
tried again but the router is not sending it properly to the computer.
I know it works because I can remote admin into the computer if I'm
bypassing the router, but that doesnt help those who need to dial in.

Thanks, I'm just stumped at this point and we have several people who
rely on being able to remote into these stations and I'm now down to
zero machines that make it past the router AND connect properly to the
server

Misty


Robert L [MVP - Networking] wrote:
> What are the IP addresses? Please post the result of ipconfig /all.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
> I installed a new network card and switch on my server about 8 months
> ago and since then I have been having problems with duplicate IP names.
> There is no WINS manager on the server, although it is listed in
> bindings and adapters etc under network properties. I rebooted one of
> my workstations and it will not allow it on the server now. The
> workstation says that the it cannot find the domain server or the
> computer is now allowed access or some thing similiar. The event log on
> the server says that the computer was not allowed on because of
> duplicate ip addresses. The network is set up on static ip, so Iknow
> what every computer's IP address is... That is why I said it is almost
> like the IP address is cached on the server somewhere and it won't let
> it on. How do I clear it or fix my problem?

In news:(E-Mail Removed) ups.com,
Prov2 <(E-Mail Removed)> typed:
> We use static because there are only 30 clients, and it makes it
> easier to remote into specific computers.

Can't you just use the computer's name? If your internal name resolution is
working right, that's all you should need.

You could use DHCP reservations, too, if you absolutely must have
non-changing IPs.

I don't use static IP addresses even on networks far smaller than yours - I
hate doing desk visits when I can avoid it. I see no value in using static
IPs on workstations - even on network printers, I use reservations.

> Also I have very little
> time I can have the server down so installing WINS on a server that
> has alot of issues already I'm scared to damage what is left.

It shouldn't require a reboot - but I'm also assuming you're doing regular
full backups. And maybe you could do this over a weekend, or after hours.
You have to be able to take your servers down sometimes; when are you
supposed to be doing patching/updates?

> Our
> controller

I presume you mean, your company controller, not your domain controller

> won't let me upgrade (I'm using NT that should explain
> alot there,

Can't you get rid of that? It's old, unsupported, blahblahblah.

> as well as an old old telrad server for phones). I'm
> trying to change little of what was preset when I started here a year
> ago because they use a TON of legacy software and equipment.
>
> Here is the IP config all
> Host Name . . . . . . . . . : remote1.ntdomain
> DNS Servers . . . . . . . . : 64.89.74.2
> 64.89.70.2

This is a problem - you can't use public DNS server IP addresses on your LAN
machines if you want AD to work correctly. You have to use an internal
(usually AD-integrated) DNS server, which itself has forwarders (and/or uses
root hints) to resolve external names. All clients and servers point at the
internal DNS server IP. All clients and servers should show up as registered
in the forward lookup zone therein.

> Node Type . . . . . . . . . : Broadcast
> NetBIOS Scope ID. . . . . . :
> IP Routing Enabled. . . . . : No
> WINS Proxy Enabled. . . . . : No
> NetBIOS Resolution Uses DNS : Yes
>
> 0 Ethernet adapter :
>
> Description . . . . . . . . : DAVICOM DM9102/A PCI Fast
> Ethernet
> dapter
> Physical Address. . . . . . : 00-D0-09-06-BB-C1
> DHCP Enabled. . . . . . . . : No
> IP Address. . . . . . . . . : 10.0.0.153
> Subnet Mask . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . : 10.0.0.254
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . :
> Lease Expires . . . . . . . :

And what about one of the clients? If you have the same (incorrect) DNS
server IPs there, that would explain why they aren't working right. AD
requires that your DNS config be perfect.....right now, sounds like your
clients are resolving the DC name by broadcast (NetBIOS).

>
>
> Lanwench [MVP - Exchange] wrote:
>> In news:(E-Mail Removed) ups.com,
>> (E-Mail Removed) <(E-Mail Removed)> typed:
>>> I installed a new network card and switch on my server about 8
>>> months ago and since then I have been having problems with
>>> duplicate IP names. There is no WINS manager on the server,
>>> although it is listed in bindings and adapters etc under network
>>> properties. I rebooted one of my workstations and it will not allow
>>> it on the server now. The workstation says that the it cannot find
>>> the domain server or the computer is now allowed access or some
>>> thing similiar. The event log on the server says that the computer
>>> was not allowed on because of duplicate ip addresses. The network
>>> is set up on static ip, so Iknow what every computer's IP address
>>> is... That is why I said it is almost like the IP address is cached
>>> on the server somewhere and it won't let it on. How do I clear it
>>> or fix my problem?
>>
>> You didn't post the ipconfig /all results as Robert asked, which
>> would help us diagnose the problem.
>>
>> Since you're using static IPs, it's going to be a huge PITA to
>> manage them - why are you not using DHCP? Also - unless you're going
>> to disable NetBIOS over TCP/IP on all your machines, install and
>> configure WINS.