From: carl.newman@xxxxxxxxxxxxx
Date: Sun Jun 16 2002 - 00:48:29 GMT-3
Malcom:
You may need to look at this MS TechNet note. It has to do with STP running
on a port connected to a MS host. There is an issue with MS host trying to
pass login and master browser messages during the STP processes on the
switch.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q202840
Carl
-----Original Message-----
From: Chris Hugo [mailto:chrishugo@yahoo.com]
Sent: Saturday, June 15, 2002 10:08 PM
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 Microsoft on the subject of WINS
http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechn
ol/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:33 GMT-3