WINS problem

I have a network with a Windows 2003 Small Business Server on it
(primary) and also a Windows Server 2003 box (secondary).

"primary" runs most of the services, including DHCP, DNS, WINS, and
Domain/Active Directory.

"secondary" is purely for running Terminal Services.

primary and secondary are both configured with static IP addresses.

The odd thing is that when I look in the WINS leases on primary,
secondary always has registered an address of 192.168.1.25 when its
actual address is 192.168.1.4. I have tried shutting down secondary,
deleting the lease, and restarting, and I have tried running "nbtstat
-RR" on secondary, but to no avail. The lease just comes right back!

192.168.1.25 is an unused address. The lease always shows
"Tombstoned" as its status.

As a side note, it is possible that secondary briefly had the address
192.168.1.25 after it was first booted up, as it may have been
assigned this by DHCP before I configured its static address.

The DHCP server on primary does not show any lease for 192.168.1.25.
The DNS records for secondary are correct.

I intend to try getting primary to hand secondary its static IP via
DHCP to see if this makes a difference. If all else fails, I'll
disable WINS (there is only one 9x client on the LAN).

But can anyone explain this strange behaviour?

Many thanks!

Have you checked reservations in the DHCP server for this IP?

"John Carlyle-Clarke" wrote:

> I have a network with a Windows 2003 Small Business Server on it
> (primary) and also a Windows Server 2003 box (secondary).
>
> "primary" runs most of the services, including DHCP, DNS, WINS, and
> Domain/Active Directory.
>
> "secondary" is purely for running Terminal Services.
>
> primary and secondary are both configured with static IP addresses.
>
> The odd thing is that when I look in the WINS leases on primary,
> secondary always has registered an address of 192.168.1.25 when its
> actual address is 192.168.1.4. I have tried shutting down secondary,
> deleting the lease, and restarting, and I have tried running "nbtstat
> -RR" on secondary, but to no avail. The lease just comes right back!
>
> 192.168.1.25 is an unused address. The lease always shows
> "Tombstoned" as its status.
>
> As a side note, it is possible that secondary briefly had the address
> 192.168.1.25 after it was first booted up, as it may have been
> assigned this by DHCP before I configured its static address.
>
> The DHCP server on primary does not show any lease for 192.168.1.25.
> The DNS records for secondary are correct.
>
> I intend to try getting primary to hand secondary its static IP via
> DHCP to see if this makes a difference. If all else fails, I'll
> disable WINS (there is only one 9x client on the LAN).
>
> But can anyone explain this strange behaviour?
>
> Many thanks!
>

"=?Utf-8?B?TWFhbW91bg==?=" <(E-Mail Removed)> wrote
in news:96B6531A-1039-4302-821F-(E-Mail Removed):

That address (192.168.1.4) was originally not included in the address
pool for the DHCP server, since the secondary was not configured to
use DHCP.

I have now set up a reservation for that address in the DHCP server
and set secondary to use DHCP.

Interestingly, that bogus lease (192.168.1.25) has gone, but the less
serious problem now is that the is no lease at all for secondary in
the WINS server. Strange!

> Have you checked reservations in the DHCP server for this IP?
>
> "John Carlyle-Clarke" wrote:
>
>> I have a network with a Windows 2003 Small Business Server on it
>> (primary) and also a Windows Server 2003 box (secondary).
>>
>> "primary" runs most of the services, including DHCP, DNS, WINS,
>> and Domain/Active Directory.
>>
>> "secondary" is purely for running Terminal Services.
>>
>> primary and secondary are both configured with static IP
>> addresses.
>>
>> The odd thing is that when I look in the WINS leases on primary,
>> secondary always has registered an address of 192.168.1.25 when
>> its actual address is 192.168.1.4.

>> 192.168.1.25 is an unused address. The lease always shows
>> "Tombstoned" as its status.
>>
>> The DHCP server on primary does not show any lease for
>> 192.168.1.25. The DNS records for secondary are correct.
>>
>> I intend to try getting primary to hand secondary its static IP
>> via DHCP to see if this makes a difference. If all else fails,
>> I'll disable WINS (there is only one 9x client on the LAN).