General discussion

Locked

WINS not seeing client reg. or resloving

By aglenoir ·
I have 3 NT Servers SPK4 running in a ethernet switch inviroment. The PDC on one side of the switch and the remaing 2 are on the other side. I'm using DCHP & WINs Hnode.
the network setup is as follows: the PDC is on vlan 1 the 2 BDC are on Vlan 104 & 105
also the PDC is multihomed. The Wins serve on vlan 104 & 105 can see the PDC and the PDC can see them. but the BDC's do not see the client workstation on there segment thus they are not resloving netbios info. the workstations can ping the PDC & BDC's but fail to see the accross vlans. Network naborhood only shows what is on that stations vlan and can not find the othen vlan or the PDC. Any help would be greatly appercated.!!

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

WINS not seeing client reg. or resloving

by moflic In reply to WINS not seeing client re ...

I don't quite understand the network topology, but is the multihomed system forwarding packets? And WINS and DHCP do resolve names and respectively assign addresses for each network numbers? I mean each NIC on multihomed should have a different network number (by subnetting) or another range of IPs. Try posting more detailed info if you can

Collapse -

WINS not seeing client reg. or resloving

by aglenoir In reply to WINS not seeing client re ...

The question was auto-closed by TechRepublic

Collapse -

WINS not seeing client reg. or resloving

Hi!

What you need to do in order for the computers on one network to see the others in network neighbourhood and get the WINS netbios names resolved is to setup the two wins servers as push/pull partners.

This you can do with the WINS admin tool that should be installed on the two WINS servers under administrative tools.

So check into that and it should start working as you want.

You can also set how often the databases should get new info from each other.

/Hasse

Collapse -

WINS not seeing client reg. or resloving

by aglenoir In reply to WINS not seeing client re ...

The question was auto-closed by TechRepublic

Collapse -

WINS not seeing client reg. or resloving

by joseph.sgandurra In reply to WINS not seeing client re ...

Assuming that IP is functioning (as indicated by ping) then your problems sounds more like netbios resolution.
Ensure the clients are given the IP address of the WINS server either via DHCP or by using an LMHOSTS file.
The lmhosts file should alsoresolve the browsing issue (unless restricted by a policy (ntconfig.pol).

Try adding this line to the lmhosts file on the workstation having the WINS and browsing problems:

<PDC ip address> <PDC netbios name> #PRE #DOM
<BDC ip address> <BDC netbios name> #PRE #DOM
<BDC ip address> <BDC netbios name> #PRE #DOM

It tells the workstation to search for domain related information from the domain controllers.
This of course assumes that the domain controllers can find the WINS servers as well as the PDC.

If the BDC's are having problems, add a lmhosts file to them.

The directory for this file <systemroot>\system32\drivers\etc
Hope this helps.

Collapse -

WINS not seeing client reg. or resloving

by aglenoir In reply to WINS not seeing client re ...

The question was auto-closed by TechRepublic

Collapse -

WINS not seeing client reg. or resloving

by aglenoir In reply to WINS not seeing client re ...

This question was auto closed due to inactivity

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums