From: Chris Hugo (chrishugo@xxxxxxxxx)
Date: Sun Jun 16 2002 - 13:27:41 GMT-3
Hi Malcom,
Your right about clients broadcasting traffic for their domain controller. You
should not have to configure helper addresses unless you are using DHCP which u
tilizes broadcast packets.
WINS request from workstations does not utilize broadcast packets. They are uni
cast packets. The trick is to configure the clients TCP/IP setting to include t
he WINS server on VLAN 3. If you don't configure the (NT, 98, etc.) client to t
he WINS server, all the client can do is broadcast for a domain controller. And
of course if your network has multiple VLANs=Logical Subnets the broadcast pac
kets generated by clients will be LIMITED within that VLAN.
Have some troubleshooting steps for you.
1. Make sure all workstation and server can ping each other.
1a. Make sure the WINS server has it's own resource records in it's own databas
e.Use WINS Administrator.
*Also make sure the primary and secondary sections of the WINS field is filled
in the IP Address of itself. This is a little known problem with Winnt 4. Win
2K does not seem to have this problem
2. Get the Client working on the same subnet as your WINS server. You can check
this out by looking at the WINS database on your WINS server. Use WINS Adminis
trator.
3. Configure a client on VLAN 2 to point to the WINS server on VLAN 3 and see
if the clients registered their name record on the WINS database on VLAN 3.
*Sometimes a restart of the workstation will help the name registration process
on the WINS server register faster.
4. Finally, test the WINS resolution by pinging your WINS server on VLAN 3 by N
AME from a workstation on VLAN 2.
HTH,
Chris Hugo
ps. Mastering Windows NT Server 4 (7th Edition) from Mark Minasi is good read f
or NT 4 networks.
Malcolm Price <malcolm@lanbase.com> wrote: Hi Chris, We have wins setup and i
t looks good. I was wondering, do I need to use the ip helper-address on vlan
2? How does the client logon work, i.e. does the local client on vlan 2 broadca
st for a domain controller and could this be why it sometimes fails as the rout
er (RSM) is not forwarding udp broadcasts ?. I think the wins side of things is
OK. Any thoughts..? Best Regards,Malcolm-----Original Message-----
From: Chris Hugo [mailto:chrishugo@yahoo.com]
Sent: Sunday, June 16, 2002 4:08 AM
To: Malcolm Price; ccielab@groupstudy.com
Subject: Re: windows nt and vlans
Hi,
Make sure your workstations on VLAN 2 is pointing to a WINS server on VLANS 3.
WINS must be enabled on a server in VLAN 3. Make sure your domain controller on
VLAN 3 also has the pointer to the WINS server also. Here is a article from Mi
crosoft on the subject of WINS
http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/
winntas/tips/techrep/wins.asp
hth,
chris hugo
Malcolm Price <malcolm@lanbase.com> wrote: Guys,
I have an interesting problem..
We have some users in a vlan who logon to a microsoft windows nt 4 domain.
There is no domain controller in their vlan (vlan 2) to validate their
logon, but the domain controller lives in vlan 3.
The users in vlan 2 often (but not always) get the message "a domain
controller could not be found". However, this rarley happens for local users
in vlan 3 where a domain controller is present.
The users are all connected to 10/100 switch ports on a catalyst 5500 with a
RSM layer 3 switch blade doing the vlan routing.
I've checked the cisco site but they all say to check the NT side of things
(as you do if you were cisco...).
Any ideas anyone..?
Best Regards,
Malcolm
Malcolm Price M.Phil. MBCS C.Eng.
Technical Director
LanBase Technologies
www.lanbase.com
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:34 GMT-3