- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Trouble with Cisco switch
Posted on 9/14/16 at 2:39 pm
Posted on 9/14/16 at 2:39 pm
I have a SG102-24-NA. In the last couple of months I've had network trouble where 1 of my workstations would lose network connection. After all the restarts to the switch, server, and workstation didn't work, I finally just went to the switch and found which actual ethernet wire went with the troubled workstation, unplugged the ethernet cable and plugged it back into a different port and everything started working again.
Is this common at all? Is there any fix? The router doesn't seem to have any upgradable firmware.
Is this common at all? Is there any fix? The router doesn't seem to have any upgradable firmware.
4
Posted on 9/14/16 at 2:55 pm to Kingpenm3
What yo logs say baw?
Posted on 9/14/16 at 2:58 pm to Kingpenm3
I have an extremely large number of switches I manage. Lots of HP (inherited) with some cisco sprinkled in. Ports can go bad it's not unheard of. I've had a few go bad in the past 12 months. The wire may have had a bad connection and simply plugging it back in did the trick and may work on the old port too. It could also be a cable that has a fault somewhere. I've seen Cat5e cable quit working and when tested has a fault, for no apparent reason.
I would mark the port as down, and if you don't have any other problems, carry on.
I would mark the port as down, and if you don't have any other problems, carry on.
Posted on 9/14/16 at 3:51 pm to Kingpenm3
Ports go bad all of the time.
Plus the Cisco Small Business line is pretty hot garbage.
eta
Just saw WavinWilly's post.. he's spot on
Plus the Cisco Small Business line is pretty hot garbage.
eta
Just saw WavinWilly's post.. he's spot on
This post was edited on 9/14/16 at 3:52 pm
Posted on 9/14/16 at 10:02 pm to Hulkklogan
quote:
Plus the Cisco Small Business line is pretty hot garbage.
You have a switch that you would suggest to replace it with?
Posted on 9/15/16 at 7:52 am to Kingpenm3
You can always try the quick and easy console in and shutdown that port then run a no shut on it. Was the port lit green or amber...to tell you the truth if all other workstations are working that pretty much tells you that you do not need a restart and that the switch overall is good and you can focus on the actually workstation/cables. And always label you cables cuts troubleshooting time in half, in that you do not have to go chasing cables throughout a whole rack or server room
Posted on 9/15/16 at 8:07 am to Kingpenm3
I work at an ISP and primarily work on carrier-grade equipment, so I don't really know much about the cheaper options. We used to use Cisco Small Business switches for our hosted voice solution, but have since moved to Juniper. For that application, the Cisco SMB line worked just fine. Perhaps in a small-scale environment the SMB line isn't bad.
However, I tried setting up 2 48-port gig PoE Cisco SMB switches at a school and had LOTS of issues; I used up almost all 48 ports and they couldn't handle the load. Intermittent packet loss, connectivity drops, etc.. Once I replaced the small business switches with Juniper EX2200s, the problems disappeared. So YMMV.. For a small office those switches are probably fine.
However, I tried setting up 2 48-port gig PoE Cisco SMB switches at a school and had LOTS of issues; I used up almost all 48 ports and they couldn't handle the load. Intermittent packet loss, connectivity drops, etc.. Once I replaced the small business switches with Juniper EX2200s, the problems disappeared. So YMMV.. For a small office those switches are probably fine.
Posted on 9/15/16 at 7:20 pm to Hulkklogan
Sorry to hijack your thread, but While yall are discussing switches /networking I have a problem that I could use some help diagnosing. My office network consists of a a new lenovo server running Server 2012 hosting AD-DC / DNS responsibilities (Single DC / single DNS, no secondary for failover...Yes i know) There are approximately 50 client computers with 95 percent being Windows 10 Pro machines/ Windows 7. The network is configured so that it goes
Modem = Router = D-link 24 port Managed switch -DC server - second 2012 server dedicated to running Sql) - 18 client connections - and 2 lines that go to two un-managed 24 port switches on either side of the office complex with approximately 32 Clients split 26/6.
The problem i'm having is every few weeks the 32 computers on the other side the two un-managed switches stop communicating with the DC/ DNS Server causing them to lose authentication/ network shares/ and internet access. Meanwhile the remaining 18 clients and servers connected to the managed switch continue to communicate / authenticate without issue. Eventually after multiple restarts / hard resets the 32 clients slowly begin to reconnect. Server Event viewer shows no DC/DNS warnings or errors, and the client side says cannot locate DNS server. The first time this happened it took 8 hours and the second time 5 hours for the network to stabilize. Ive tried everything i can think of in my limited knowledge of networking and suspect the authentication packets are getting corrupted as they pass through the second network switch (All connections are Gigabit connection and the two un-managed switches are less then two months old. Any input is appreciated.
Modem = Router = D-link 24 port Managed switch -DC server - second 2012 server dedicated to running Sql) - 18 client connections - and 2 lines that go to two un-managed 24 port switches on either side of the office complex with approximately 32 Clients split 26/6.
The problem i'm having is every few weeks the 32 computers on the other side the two un-managed switches stop communicating with the DC/ DNS Server causing them to lose authentication/ network shares/ and internet access. Meanwhile the remaining 18 clients and servers connected to the managed switch continue to communicate / authenticate without issue. Eventually after multiple restarts / hard resets the 32 clients slowly begin to reconnect. Server Event viewer shows no DC/DNS warnings or errors, and the client side says cannot locate DNS server. The first time this happened it took 8 hours and the second time 5 hours for the network to stabilize. Ive tried everything i can think of in my limited knowledge of networking and suspect the authentication packets are getting corrupted as they pass through the second network switch (All connections are Gigabit connection and the two un-managed switches are less then two months old. Any input is appreciated.
Posted on 9/15/16 at 8:27 pm to triggs85
What's the brand of the unmanaged switches? I had a similar issue switch a Cisco SG200 being used in a small training room.. Ended up resetting the switch, updating the firmware, and throwing it on a small UPS. Not sure which one of those fixed it, but the problem hasn't come back. I read a lot of forums about a similar issue, but it was mainly people with IP phones that couldn't get them to register. Had to do with the smartport setting I believe.
Get a cheap desktop. Install Server 12 and run active directory and DNS in read only mode. Unless you want a massive headache down the line
quote:
(Single DC / single DNS, no secondary for failover...Yes i know)
Get a cheap desktop. Install Server 12 and run active directory and DNS in read only mode. Unless you want a massive headache down the line
Posted on 9/15/16 at 11:34 pm to philabuck
the Un-managed switches are TP-Link TL-SG1024D their both on UPS's already ....
Well aware of the risk we're taking, Problem is we're in a budget spending freeze to Jan 1 So i have to limp along til the new budget kicks in before I can ask for more equipment.
Well aware of the risk we're taking, Problem is we're in a budget spending freeze to Jan 1 So i have to limp along til the new budget kicks in before I can ask for more equipment.
Posted on 9/16/16 at 2:48 pm to triggs85
Is this shitty diagram what you have, in a nutshell?
If so, when this is broken, do you have any logs showing any issues?
Are the users and server on separate VLANs, or is it one large broadcast domain?
When it's broken, can the users still reach the internet? (ping 8.8.8.8) DNS can be hosed but internet access is still there. If they can't ping out to the internet without DNS, then the links between the two unmanaged switches and the managed switch are likely having issues. This is especially true if the two unmanaged switches are daisy chained together rather than separately plugged into the managed switch
If so, when this is broken, do you have any logs showing any issues?
Are the users and server on separate VLANs, or is it one large broadcast domain?
When it's broken, can the users still reach the internet? (ping 8.8.8.8) DNS can be hosed but internet access is still there. If they can't ping out to the internet without DNS, then the links between the two unmanaged switches and the managed switch are likely having issues. This is especially true if the two unmanaged switches are daisy chained together rather than separately plugged into the managed switch
This post was edited on 9/16/16 at 2:58 pm
Posted on 9/22/16 at 8:45 am to Hulkklogan
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 on 9/22/16 at 9:25 am to triggs85
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 on 9/22/16 at 9:32 am to triggs85
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
Posted on 9/22/16 at 9:42 am to Hulkklogan
What happens when you set a static ip address and dns info on a client connected to the unmanaged switch? Can they communicate to the server?
Posted on 9/22/16 at 10:07 am to Hulkklogan
quote:
What is doing DHCP for you? The router or the server?
That's my thought process. i think they're losing contact with the DHCP server. Whatever is doing that needs to push out 8.8.8.8 or 4.2.2.2 as a secondary DNS.
Posted on 9/22/16 at 3:01 pm to 3nOut
DHCP is disabled all Clients are configured manually with static IP addresses and primary DNS.. since posting that I've gone through line by line and discovered that the problem switch was actually plugged into the primary router instead of the managed switch while the second unmanaged switch that remained online was plugged into the managed switch. After moving it to the managed switch the network came back online
This post was edited on 9/22/16 at 3:08 pm
Posted on 9/22/16 at 3:04 pm to triggs85
yuck
Good job figuring it out.
Good job figuring it out.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News