Rogue IP address

[richiep]

I have a Windows 2000 server that seems to be creating a rogue IP address by itself.
The fixed address on the NIC is 192.168.0.1, however suddenly workstations will be unable to login and when we ping the server by UNC name it resolves to 192.168.0.129 !!

We have found this address in the registry in the following location;
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
DhcpIPAddress
Key: Adapter Name\Parameters\Tcpip

If we manually change this address it works fine for a while but then reappears as the 129 address and everything stops again.

The W2K is running as DHCP server so therefore should only know about the fixed 192.169.0.1 address.

Any ideas/help I would be grateful

 

[gurner]

Do you have a RAS Modem on this machine?

 

[richiep]

Yes it does have a RAS modem, possibly 2 (it is on a customer site)
Is this likely to be an issue/cause of my problem?

 

[gurner]

Is the RAS connection for incoming dialups from laptops or is it a dial out connection to an ISP?

I saw a similar problem when a server dialled an ISP to collect emails, it had an internal IP of 10.0.0.11 but when it dialled up it was leased an IP of approx 195.168.2.15 (or what ever) by the ISP

I didn't have time to fix the problem on the machine so i moved the RAS off onto a member server and it runs lovely now.

I know it can be configured to work but i took the belt and braces route.

 

[richiep]

The RAS modem is set up for dial in access only and as far as I am aware uses the DHCP to grant IP addresses for the remote users.

They are using a Proxy server for Web browsing traffic only. However the rogue IP address is an internal address of 192.168.0.129 not an external address.

We have no idea where this address is coming from.