Started By
Message

re: Trouble with Cisco switch

Posted on 9/22/16 at 8:45 am to
Posted by triggs85
Member since Nov 2007
480 posts
Posted on 9/22/16 at 8:45 am to
When it fails there is No internet access nor network access...however If we use a secondary public dns (8.8.8.8) then we regain internet access... no seperate vlans... the unmanaged switches are on seperate homeruns.... it happened again today , however this time only one of the unmanaged switches went down... also I've noticed that one computer on the side that went down is connected but the connection is so slow to connect that it's unusable.
Posted by 3nOut
Central Texas, TX
Member since Jan 2013
29001 posts
Posted on 9/22/16 at 9:25 am to
quote:

When it fails there is No internet access nor network access...however If we use a secondary public dns (8.8.8.8) then we regain internet access... no seperate vlans... the unmanaged switches are on seperate homeruns.... it happened again today , however this time only one of the unmanaged switches went down... also I've noticed that one computer on the side that went down is connected but the connection is so slow to connect that it's unusable.




what are you using for DHCP in your scenario and when you say no network access, what IP does one of the affected machines get during the outage? 169.XX ?
Posted by Hulkklogan
Baton Rouge, LA
Member since Oct 2010
43305 posts
Posted on 9/22/16 at 9:32 am to
quote:


Trouble with Cisco switch
When it fails there is No internet access nor network access...however If we use a secondary public dns (8.8.8.8) then we regain internet access... no seperate vlans... the unmanaged switches are on seperate homeruns.... it happened again today , however this time only one of the unmanaged switches went down... also I've noticed that one computer on the side that went down is connected but the connection is so slow to connect that it's unusable.


Okay so it sounds like when you lose connectivity, it's not to the internet. If you can change your DNS to 8.8.8.8 and surf the internet, then your DNS requests are failing, not your internet connection. That points to more of a server issue, imo.

Have you dug through switch logs or server logs to find errors?

What is doing DHCP for you? The router or the server?
This post was edited on 9/22/16 at 9:35 am
first pageprev pagePage 1 of 1Next pagelast page
refresh

Back to top
logoFollow TigerDroppings for LSU Football News
Follow us on Twitter, Facebook and Instagram to get the latest updates on LSU Football and Recruiting.

FacebookTwitterInstagram