Yes, but really what I was referring to was that the port will not pass
traffic when it's trying to figure out the spanning-tree. Since you're set
to portfast, the port should immediately go to forwarding.
Since this is affecting only a few users on the network, I really can't see
that STP is the issue.
My instincts say that this is probably not a network issue; that it's more
likely a Windows issue. However, there are some tests you can do to
determine the point of failure:
1) Hookup a sniffer to the switch in question, mirror the problem port(s),
fire up the workstations, and watch the traffic. Do you see the
workstation trying to authenticate? Do you see responses from the DC?
2) If the DC is trying to respond, but the workstation isn't receiving the
messages, look for errors on the switch ports.
3) If all traffic looks normal and you're not seeing any errors, start
looking at your Windows configuration and/or logins. Make sure the users
aren't selecting a domain that is no longer available on your network or
something like that.
Thanks,
Craig
At 01:43 PM 5/21/2001 -0400, you wrote:
>Yes and it just started last week, so according to what you have said,
>spanning tree is ruled out. Now when you say the port is blocking, are you
>referring to the port that station is connected to?
>
>-----Original Message-----
>From: Craig Columbus [mailto:[EMAIL PROTECTED]]
>Sent: Monday, May 21, 2001 1:18 PM
>To: Robert Perez
>Cc: [EMAIL PROTECTED]
>Subject: Re: "network logon problems" [7:5271]
>
>
>Has this ever worked? Did the problem just recently occur?
>If the user logs in with the cached credentials, verifies that he is able
>to access the correct network resources, logs off, logs back in, and still
>can't connect to the domain, then you can rule out spanning-tree
>calculations as the problem.
>Is the domain in which the user accounts reside available and properly
>configured on each of the problem workstations?
>I can only think of a few things that would cause this problem:
>1) The correct domain is not available, or does not (or is unable to)
>respond within the time-out for some reason.
>2) The correct domain is not configured properly in Windows.
>3) The switch port is blocking for some reason.
>
>Craig
>
>At 01:01 PM 5/21/2001 -0400, you wrote:
> >HELP!!
> >I have an issue where it appears that multiple users cannot login. I
> >receive the error "you will be logged on using a cached account" and once
> >logged on, all network devices are available. I have ensured that on the
> >catalyst 3548XL, all ports have Port fast enabled and I have also enabled
> >STP to try and overcome the problem with no success. I have also moved
the
> >users to switches that have no issues and I still have the same problem.
I
> >also did a ipconfig /release renew and replaced the nic card and did a
cold
> >boot and warm boot on the machines with no success. All other user are
>fine
> >and it is only affecting like 3 people. I even set them to auto, auto and
> >the switch to auto,auto and this did not work either. I then tried 100
>full
> >and half and that did not work either. I also do not have port security
> >enabled. It appears to be a network issue with the catalystr switches,
but
> >I am unsure as to the root of the problem. Don't know if this would do
> >anything, but I did a NBTSTAT -RR from the command line as well. Any help
> >would be greatly appreciated.Thank you.
> >FAQ, list archives, and subscription info:
> >http://www.groupstudy.com/list/cisco.html
> >Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=5293&t=5271
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
