 |
 |
Networking question
|
|
|
|
|
Grizzled Veteran
Join Date: Nov 2001
Location: Seattle
Status:
Offline
|
|
I'm using a Dell 3024 switch in a home network that seems to work just fine. The only issue I seem to have is when I wake my machine from sleep it doesn't seem to recognize the network for 15 to 30 seconds. Does anybody know why this is? This wasn't a problem before when everything was just connected to my router.
|
|
|
| |
|
|
|
|
|
|
|
Admin Emeritus  Join Date: Oct 1999
Location: Zurich, Switzerland
Status:
Offline
|
|
Some switches don't auto-negotiate correctly. Try using the advanced ethernet preferences in the Network pane of System Preferences to manually set the ethernet settings (most likely 100mbps full-duplex) and see if that helps.
tooki
|
|
|
| |
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Nov 2001
Location: Seattle
Status:
Offline
|
|
Originally Posted by tooki
Some switches don't auto-negotiate correctly. Try using the advanced ethernet preferences in the Network pane of System Preferences to manually set the ethernet settings (most likely 100mbps full-duplex) and see if that helps.
tooki
I tried it and it made it worse. Thanks for the idea. I've tried to setting the switch to 100 but that doesn't seem to help either. The next thing I'm going to try is update the switch firmware.
|
|
|
| |
|
|
|
|
|
|
|
Administrator  Join Date: Apr 2001
Location: San Antonio TX USA
Status:
Offline
|
|
It could be something as simple as a flakey cable. Make sure you use a good cable when you try it next time.
|
Glenn -----OTR/L, MOT, Tx
|
| |
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Nov 2001
Location: Seattle
Status:
Offline
|
|
Originally Posted by ghporter
It could be something as simple as a flakey cable. Make sure you use a good cable when you try it next time.
Yeah, thats also one of the things on my list.
|
|
|
| |
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Nov 2001
Location: Seattle
Status:
Offline
|
|
For those who are interested, I figured out what the problem was.
A switch that supports spanning tree generally operates the spanning tree algorithm on all the ports by default. The algorithm can take up to 50 seconds to converge and determine if another switch has been connected to the port. So it can determine if a loop has been created and shut down the port.
In the case of a client workstation this obviously does not apply. Cisco overcame this issue by providing a feature called 'portfast'. This is used when you know a workstation will be connected to the switch. This feature disables the spanning tree algorithm on the port and allows it to move into the forwarding state immediately.
Since I have a Dell switch, I simply shutdown the spanning tree. This took care of my problem.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top