Network Connection takes too long to initialize

[scott.hawks]

I have 2 3560 switches. currently, the both run the native vlan 1. i am in the process of setting up vlans and moving over computers and servers to them. i have one particular user that upon starting his computer and logging in to our domain, it takes over 3 minutes to connect to the domain controller and process the startup script. i have checked and double checked to be sure the port is set to spanning-tree portfast. any ideas as to what else i may look at. i also checked the wiring itself to make sure that wasn't the problem.

thanks in advance for your advice.

[bjw]

Try a trace route/ping from the subject PC along the switch/router path to the AD server and see if there's an obvious bottle necks.

Also check affected interfaces for duplex matches, error counts etc.

Is the ip default gateway correct, can you see it cleanly in show Arp?

[scott.hawks]

here is output from interface:

FastEthernet0/1 is up, line protocol is up (connected)

Hardware is Fast Ethernet, address is 0014.6a97.d803 (bia 0014.6a97.d803)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, media type is 10/100BaseTX

input flow-control is off, output flow-control is unsupported

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 00:00:01, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

243181 packets input, 38716397 bytes, 0 no buffer

Received 41422 broadcasts (0 multicast)

0 runts, 0 giants, 0 throttles

1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 151 multicast, 0 pause input

0 input packets with dribble condition detected

2972864 packets output, 423672959 bytes, 0 underruns

0 output errors, 0 collisions, 3 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

0 output buffer failures, 0 output buffers swapped out

do i need to have switport mode access on this port? would it make a difference?

Thanks.

[Jon Marshall]

Hi

There are a multitude of things that could explain this.

Are you saying that this user was okay before you moved him into a new vlan ?

If so have you tried moving him back ?

If he is in a new vlan are there any other users in that vlan and what is their performance like.

What is his PC performance like once he has logged in.

A lot happens when a user logs in, does the computer have enough memory/cpu power.

Slow logins can often be related to name lookups whether that be WINS or DNS.

Jon

[glen.grant]

On the user port do a "switchport host" command , this turns on portfast but also turns off trunking and channeling . The port should be an access port and a non routed port , use the switchport command on the interface . Do an extended ping from both the user pc and the switch itself to the domain controller and see how the response is and if any packets are being dropped between the user and the controller , if not it is probably not a network issue and you need to look at the user pc for problems like some background script running or something like that specially if no one else on that switch is having an issue. The port info look fine so I doubt it is a speed/duplex issue ,verify nic setting just to be sure , if the nic is set as auto the switchport must be auto also ,if hardcoded then the switch must be hardcoded.