Worstations On Switches Vs Hubs

[sifiguy]

Hi there

We're getting batch files called by a login script failing to run when our workstations are attached to switches (2950's), but the batch files run fine when the workstations are attached to hubs. The weird thing is the hubs still work when the are uplinked to the switches that produce the errors when the workstations are directly attached to them.

Our workstations are Compaq Evo's, with Intel PRO/100 VM on-board NICs. We use Compaq servers (mostly DL380's) and are running Netware 6.0 for file and print. The Netware Client is 4.83.1 SP1.

Any help would be greatly appreciated.

 

[dx1]

You might want to enable portfast on the switch ports that your clients and servers are connected to.

 

[jpm121]

Yup, that's exactly what portfast is supposed to do. The batch file tries to run on startup, but the LAN interface isn't ready on the switch side to receive anything.

 

[vipergg]

Yeah you need portfast turned on , if you don't nothing is going to get tranferred after login on the switch for 40-50 seconds due to spanning tree running . this should fix your problem . this will also eliminate any dhcp problems if you happen to be running that .

 

[sifiguy]

I don't understand. Surely if I can log in and my drive mappings are all fine then I have a valid negotiated connection?

 

[BuckWeet]

Spanning tree is kicking

spanning tree kicks in upon link initation, then takes approx 30 secs to start passing traffic. So whats happening is your link is going up, and you're trying to get a DHCP lease, run the script, etc.. but the ethernet switch is not passing any data from that port..

So by turning spanning-tree portfast on, as soon as the link goes up it will start passing traffic, this should fix all problems that you have..

Also only do portfast on end user devices (phones, pcs,servers) always keep it on for network switch/hub uplinks

BuckWeet