From: Bezverkhi, Serguei (Serguei.Bezverkhi@xxxxxx)
Date: Sat Jun 15 2002 - 15:27:25 GMT-3
Make sure that on VLAN2 stations are configured with WINS' server IP
address, if there is no WINS configured, stations will use broadcast to
find a domain controller and as we know broadcasts are not propagated by
default. If you use DHCP on VLAN 2, put wins server address there and
make sure that NetBIOS node type is hybrid 0x8.
HTH
Serguei
-----Original Message-----
From: Malcolm Price [mailto:malcolm@lanbase.com]
Sent: June 15, 2002 1:45 PM
To: ccielab@groupstudy.com
Subject: windows nt and vlans
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:33 GMT-3