WINS acting strangly upon install on a BDC

[Drew Sweeney]

I have a small domain with a PDC, a BDC, and 4 workstations in my home office network.

- I was recently re-installing NT 4.0 on the BDC.

- This server is also the home of my WINS server.

- The server is named "BACKOFFICE", because it is a DEC Alpha XL 300 with all the disk space and processing power. It is the home of most of my BackOffice applications.

- I installed WINS as part of the original networking options during the NT's setup.

- Once the system came up, it appeared WINS was running, but no IP name resolution was occuring within my subnet (192.168.100.xxx). I could ping the IP address of the server (192.168.100.254) but not it's name (BACKOFFICE).

- I went into the WINS manager and it looked like it was collecting information within its database that was correct; but it didn't appear to be sharing that information with the rest of the network.

- I then selected the option within the WINS manager that would show the NAME with the IP following it, rather than the name only.

- In the left pane of the WINS manager, the default server showed as "BACKOFFICE (1.10.0.184)" rather than with the IP of the server itself, (192.168.100.254).

- I'm not sure where this IP came from, but if that is what the WINS server thought it's IP address was then it explains why my subnet's PC's can't hear the response of the WINS server if they were looking for 192.168.100.254.

- I tried deleting that server and entering my server's IP, and the original wouldn't go away.

- When I deleted all WINS servers from the WINS manager and re-booted, then the WINS server manager showed BACKOFFICE as the WINS server with a completely different IP.

I know this sounds weird, but it really happened. Does any one have a clue? Any knowledge would be helpful.

Thanks in advance

drew sweeney
sr. consultant
basupport, inc.
(303) 668-1100

[Brandon Banis]

Try installing WINS again, make users are using the wins server.


------------
Drew Sweeney at 7/13/99 12:29:50 AM

I have a small domain with a PDC, a BDC, and 4 workstations in my home office network.

- I was recently re-installing NT 4.0 on the BDC.

- This server is also the home of my WINS server.

- The server is named "BACKOFFICE", because it is a DEC Alpha XL 300 with all the disk space and processing power. It is the home of most of my BackOffice applications.

- I installed WINS as part of the original networking options during the NT's setup.

- Once the system came up, it appeared WINS was running, but no IP name resolution was occuring within my subnet (192.168.100.xxx). I could ping the IP address of the server (192.168.100.254) but not it's name (BACKOFFICE).

- I went into the WINS manager and it looked like it was collecting information within its database that was correct; but it didn't appear to be sharing that information with the rest of the network.

- I then selected the option within the WINS manager that would show the NAME with the IP following it, rather than the name only.

- In the left pane of the WINS manager, the default server showed as "BACKOFFICE (1.10.0.184)" rather than with the IP of the server itself, (192.168.100.254).

- I'm not sure where this IP came from, but if that is what the WINS server thought it's IP address was then it explains why my subnet's PC's can't hear the response of the WINS server if they were looking for 192.168.100.254.

- I tried deleting that server and entering my server's IP, and the original wouldn't go away.

- When I deleted all WINS servers from the WINS manager and re-booted, then the WINS server manager showed BACKOFFICE as the WINS server with a completely different IP.

I know this sounds weird, but it really happened. Does any one have a clue? Any knowledge would be helpful.

Thanks in advance

drew sweeney
sr. consultant
basupport, inc.
(303) 668-1100

[James Gregg]

Here is the article that references the same thing on the MS site.

http://support.microsoft.com/support/kb/articles/Q156/2/04.asp?LN=EN-US&SD=gn&FR=0

------------
Brandon Banis at 8/11/99 7:51:23 PM

Try installing WINS again, make users are using the wins server.


------------
Drew Sweeney at 7/13/99 12:29:50 AM

I have a small domain with a PDC, a BDC, and 4 workstations in my home office network.

- I was recently re-installing NT 4.0 on the BDC.

- This server is also the home of my WINS server.

- The server is named "BACKOFFICE", because it is a DEC Alpha XL 300 with all the disk space and processing power. It is the home of most of my BackOffice applications.

- I installed WINS as part of the original networking options during the NT's setup.

- Once the system came up, it appeared WINS was running, but no IP name resolution was occuring within my subnet (192.168.100.xxx). I could ping the IP address of the server (192.168.100.254) but not it's name (BACKOFFICE).

- I went into the WINS manager and it looked like it was collecting information within its database that was correct; but it didn't appear to be sharing that information with the rest of the network.

- I then selected the option within the WINS manager that would show the NAME with the IP following it, rather than the name only.

- In the left pane of the WINS manager, the default server showed as "BACKOFFICE (1.10.0.184)" rather than with the IP of the server itself, (192.168.100.254).

- I'm not sure where this IP came from, but if that is what the WINS server thought it's IP address was then it explains why my subnet's PC's can't hear the response of the WINS server if they were looking for 192.168.100.254.

- I tried deleting that server and entering my server's IP, and the original wouldn't go away.

- When I deleted all WINS servers from the WINS manager and re-booted, then the WINS server manager showed BACKOFFICE as the WINS server with a completely different IP.

I know this sounds weird, but it really happened. Does any one have a clue? Any knowledge would be helpful.

Thanks in advance

drew sweeney
sr. consultant
basupport, inc.
(303) 668-1100