Windows 2003 WINS Migration

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am in the process of a 2003 upgrade from NT. In preperation for this I
needed to replace servers. This network relies heavily on WINS. I have
moved the WINS database from NT to a 2003 server and converted successfully.
Now with the new 2003 WINS server I cannot see all of the computers or
servers in "My Network Places". I can resolve them fine and even "UNC" to
them, but I cannot see them. The other wierd thing is that the new WINS
server cannot even see itself.

Any suggestions would be apprecitated.

Thanks,

Mike B.
 
Make sure that the new wins server is a wins client to itself. Windows 2003
also requires smb signing which can cause problems with downlevel clients. I
would disable it at least temporally in Local Security Policy security
settings/local policies/security options. Set Microsoft network
server:digitally sign communications(always) to DISABLED. Also run
nbtstat -n on the new Windows 2003 Server to make sure then netbios over
tcp/ip is working and that at least three names are registered. Double check
that the built in ICF firewall is also disabled on the new server. Verify
that client computers can ping the wins server. The link below will also be
helpful. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;300986
 
Steven,

I have check all your suggestions and everything is okay, except for the
nbtstat -n command which I have pasted the output below. There seems to be
only two entries listed. Which one am I missing?
Clients can ping and UNC to anything without problem. Only problem is that
only some of the servers/computers are listed in "network neighborhood" are
not listed.

Thanks,

Mike B.

C:\Documents and Settings\Administrator>nbtstat -n

Broadcom NetXtreme Dual Port Gigabit Ethernet Adapter - Onboard - Link A:
Node IpAddress: [x.x.x.x] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
CAIADC-DC02 <00> UNIQUE Registered
CAIADC-DC02 <20> UNIQUE Registered
CAIADC <00> GROUP Registered
CAIADC <1E> GROUP Registered

C:\Documents and Settings\Administrator>
 
Hi Mike.

Your nbtstat -n looks fine as it actually is four entries.First is
workstation service, second is server service, third is domain name, and
fourth is something to do with browser elections. That and more info that
may help you troubleshoot is in the link below.

http://support.microsoft.com/Default.aspx?kbid=830578

If your browse list is incomplete it could mean that the missing
servers/computers are not enabled with file and print sharing, have netbios
over tcp/ip disabled as shown via Ipconfig /all command, are configured to
be hidden from the browse list as shown via net config server command, have
the built in ICF firewall enabled or ipsec policy assigned, are not a wins
client, browsing is not enabled across subnets via wins servers as
replication partners, have computer names longer than 15 characters, OR more
likely you have an incomplete browse list due to master browsers being multi
homed or also a rras server. The pdc fsmo will by default be the domain
master browser. The links below explain more and may help. Browsing problems
can be a real pain [since it is done behind the scenes] but hopefully some
of this will help. --- Steve

http://support.microsoft.com/?kbid=191611
http://support.microsoft.com/kb/135404/EN-US/
http://support.microsoft.com/default.aspx?scid=kb;EN-US;102878
http://support.microsoft.com/default.aspx?scid=kb;EN-US;188305

Mike B. said:
Steven,

I have check all your suggestions and everything is okay, except for the
nbtstat -n command which I have pasted the output below. There seems to
be
only two entries listed. Which one am I missing?
Clients can ping and UNC to anything without problem. Only problem is
that
only some of the servers/computers are listed in "network neighborhood"
are
not listed.

Thanks,

Mike B.

C:\Documents and Settings\Administrator>nbtstat -n

Broadcom NetXtreme Dual Port Gigabit Ethernet Adapter - Onboard - Link A:
Node IpAddress: [x.x.x.x] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
CAIADC-DC02 <00> UNIQUE Registered
CAIADC-DC02 <20> UNIQUE Registered
CAIADC <00> GROUP Registered
CAIADC <1E> GROUP Registered

C:\Documents and Settings\Administrator>

Steven L Umbach said:
Make sure that the new wins server is a wins client to itself. Windows
2003
also requires smb signing which can cause problems with downlevel
clients. I
would disable it at least temporally in Local Security Policy security
settings/local policies/security options. Set Microsoft network
server:digitally sign communications(always) to DISABLED. Also run
nbtstat -n on the new Windows 2003 Server to make sure then netbios over
tcp/ip is working and that at least three names are registered. Double
check
that the built in ICF firewall is also disabled on the new server. Verify
that client computers can ping the wins server. The link below will also
be
helpful. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;300986
Click to expand...
Click to expand...
 
Back
Top