invalid source IP on WINS
I have a NT server 4.0 SP3 installed.
IP of this machine is 172.10.23.33
but on WINS admin I see allways a server with IP 1.10.0.184!!!
ok I can't reach this address but after add server and correct IP i can connect to this service and read out content of WINS database.
All i can see at this place is one owner (1.10..0.184) with all informations about my domain (172.10.23.xx). all replication partners of this WINS server receives also this invalid informations.
where is this wrong address stored? I've already removed WINS service and all entries about WINS removed from registry. but after a reinstallation of this i found WINS on the old place!!
I cannot install entire machine!! but i must correct this problem.
has anybody seen this?
IP of this machine is 172.10.23.33
but on WINS admin I see allways a server with IP 1.10.0.184!!!
ok I can't reach this address but after add server and correct IP i can connect to this service and read out content of WINS database.
All i can see at this place is one owner (1.10..0.184) with all informations about my domain (172.10.23.xx). all replication partners of this WINS server receives also this invalid informations.
where is this wrong address stored? I've already removed WINS service and all entries about WINS removed from registry. but after a reinstallation of this i found WINS on the old place!!
I cannot install entire machine!! but i must correct this problem.
has anybody seen this?
Another option is to search the registry for the ip address.
Post where ever you come across it then I'll be able to tel if you should delete it or replace it with something else
Post where ever you come across it then I'll be able to tel if you should delete it or replace it with something else
ASKER
bbao,
I'm sure about advanced settings. there are many IP's configured to interfaces but no one at this address.
biyiadeniran,
how you can search an IP inside the registry? IP's are stored as binary! not as ascii.
I'm sure about advanced settings. there are many IP's configured to interfaces but no one at this address.
biyiadeniran,
how you can search an IP inside the registry? IP's are stored as binary! not as ascii.
Hi heiko,
Try do the folowing...
- go to ms-dos prompt
- type ipconfig /release
if you see the address 1.10.0.184 so you are attached to a server with this address
- if you are attached to a server NT, give the IP addreess to this server
- disconnect the network cable
- type ipconfig /renew (you must see your local IP address 172.10.23.33)
PLEASE LET ME KNOS HOW IT GOES
GOOD LUCK
Try do the folowing...
- go to ms-dos prompt
- type ipconfig /release
if you see the address 1.10.0.184 so you are attached to a server with this address
- if you are attached to a server NT, give the IP addreess to this server
- disconnect the network cable
- type ipconfig /renew (you must see your local IP address 172.10.23.33)
PLEASE LET ME KNOS HOW IT GOES
GOOD LUCK
ASKER
Hi arados,
this is a server not using DHCP and there is also no DHCP server inside my network.
IPCONFIG /release has no changes because IP is static
IPCONFIG /renew also makes nothing because there is no DHCP server.
sorry
this is a server not using DHCP and there is also no DHCP server inside my network.
IPCONFIG /release has no changes because IP is static
IPCONFIG /renew also makes nothing because there is no DHCP server.
sorry
Here's a different angle to think about - maybe the strange address isn't stored on your machine, but is being discovered dynamically by your WINS service.
-could 1.10.0.184 have your system named as a replication partner by accident?
-do you use Microsoft DNS with internal WINS lookup enabled?
Some ideas for investigation:
-look in event log for WINS events that mention 1.10.0.184.
-put a datascope on the LAN you're on, and watch for traffic
from 1.10.0.184
-could 1.10.0.184 have your system named as a replication partner by accident?
-do you use Microsoft DNS with internal WINS lookup enabled?
Some ideas for investigation:
-look in event log for WINS events that mention 1.10.0.184.
-put a datascope on the LAN you're on, and watch for traffic
from 1.10.0.184
I agree - if the Server itself has no bindings to that address , it must be coming from an external client trying to register with the WINS server. Watch for the traffic coming in.
If you sort by name , is there another with the same name on the 172.10 network?
if you run NETSTAT -R from DOS, have you even got a route to 1.10.0.184? - just our of curiosity
If you sort by name , is there another with the same name on the 172.10 network?
if you run NETSTAT -R from DOS, have you even got a route to 1.10.0.184? - just our of curiosity
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 think your answer is right. But the server with problem is already replaced. I will test this scenario by a new one. (hope it's reproducable)
thanks
thanks
Good luck!