From: Minihane Kevin-kminih01 (Kevin.Minihane@xxxxxxxxxxxx)
Date: Sat Jun 15 2002 - 15:35:26 GMT-3
Hi
I'd check the WINS address on the NT clients which are having the problems.
Usually, all NT machines register themselves with the local WINS server wheneve
r they boot up. This includes servers, as well as workstations. When a workst
ation boots up, it will send a message to the local WINS server looking for it'
s PDC. If the PDC has already registered with the WINS server, the WINS server
will return the IP address of the PDC to the workstation.
HTH
Kevin
-----Original Message-----
From: Lance [mailto:lance@advnetech.com]
Sent: 15 June 2002 19:25
To: Malcolm Price; ccielab@groupstudy.com
Subject: Re: windows nt and vlans
Malcolm,
Try enabling portfast on all ports that the clients are pluged into on the
cat 5500. The command is:
set spantree portfast mod/port enable
----- Original Message -----
From: "Malcolm Price" <malcolm@lanbase.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, June 15, 2002 1:44 PM
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