I have upgraded my SG200-08 switches from firmware version 1.0.5.1 to version 1.0.6.2. Since that new firmware is active, the network-printing from my Macbooks and iMacs is not working anymore. They all have TCP/IP connected network printers (not based on Bonjour connections) and they cannot print anymore; timeout communicating to printer. Windows workstations on the same network are still able to print to the network printers, only the Mac's do have this problem.
I am still able to view printer-information via the Mac's, so communicating is still possible. Also surfing to the admin-page of these printers is still working, only sending the actual print-job is failing.
I have reset the SG200-08 switches to factory defaults, but still no printing.
Finallly I did a downgrade, back to firmware version 1.0.5.1 and now printing from the Mac's is working again.
Any ideas, perhaps a firmware bug?
I have seen the new firmware version 1.2.9.44, but there are only language files available for the SG200-08, no firmware file...
So I don't know if this new version perhaps solves this problem.
I believe I am running into this same issue, but it does not appear to be related to using privileged ports for source and destination. I just upgraded to 1.0.6.2 recently and my Fedora Linux based NFS stopped working (which has previously worked for a long time with no problems). From my NFS client, I see the request being sent out to the server but no response:
# tcpdump -e -nnn -i eth0 host 10.0.4.13 and not port 22
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
I tried changing the MTU on the client (it isn't an issue with the server, the other SG200-08 switch the server is connected to in my case never receives the SYN packet from the downstream switch) to 1492, that didn't help (same response):
When I do a port mirror on the SG200-08 and use tcpdump on the switch port connected to the client I see the frame arrive. When I do a port mirror on the uplink trunk port, the frame is never transmitted, it is being dropped by the switch for some reason.
It is very disappointing to see how things are taken up here by Cisco.
This issue has been reported by me two months ago and there is still no action taken by Cisco as far as I can see.
In the meanwhile there are more people who confirmed the issue, with samples, so Cisco engineers should be able to reproduce this problem now, especially because the used configurations are not very complicated.
Hi Rene, one piece of information I do not see from anyone.
Have you completely factory default the switch (configure nothing) plug stuff in and see if it works?
Make a simple point to point connection. Assign static IP, only 2 things connecting to switch, the client and the server. No routers, no VLAN, no nothing (including no wireless from somewhere). Give this a try.
-Tom Please mark answered for helpful posts
-Tom
Please mark answered for helpful posts
http://blogs.cisco.com/smallbusiness/
Hi Guillaume, my personal concern is, since it is a layer 2 device, I'm very curious of the behavior without any other network influences.
Would it be possible to set up a point to point connection using static IP addresses?
Host A <=> Switch <=> Resource
If this fails at a factory default parameter this would need a good assessment. But the key is to make sure the switch is failing.
We need to rule out any external factors such as domain controllers, routing policies, or even firewall/security setting on the client/server environment.
-Tom Please mark answered for helpful posts
-Tom
Please mark answered for helpful posts
http://blogs.cisco.com/smallbusiness/
TL;DR I tried a very basic setup one client and one server both sides in static addressing but the NFS packets are still lost.
I did try this setup. Static IP addresses on both sides (IPv4 and IPv6) and it still fails.
The very basic setup, no router, nothing except the NFS server and the NFS client did not worked.
It still a strange behavior though since the switch is supposed to do L2 things only why a protocol such as NFS, which is L2, would fail after an upgrade while everything else still worked properly.
I checked everything on the network first before telling me "is it the switch?". And I can tell that I was suprise that after downgrading the switch firmware the NFS mounts came up.
I don't know how a switch firmware especially for the Small Business series but I don't see why it would filter/drop or do anything else but forward the packet on the right port. If someone could at least clarify some of these questions I would be grateful.
I had the exact same issue as the one above. This is a BUG. I too wasted 8 hours troubleshooting!
Details for Re-Pro: Esxi 5.1 using NFS to Qnap ts-469pro. SG200-08 came with 1.0.5.x from Amazon.com. Everything worked before using the Cisco device, and with the Cisco device at the above firmware revision.
Update switch to 1.0.6.x (latest): Esxi NFS connection FAIL - "Cannot connect to nfs host". Mac connection via NFS to Qnap worked- it uses a dynamic outbound port. Esxi uses a fixed outbound port (under 1024).
To the Cisco moderators: We're all advanced tech people here. PLEASE stop asking for the generic support info! Changing MTU size, removing external network variables, etc. should NOT be necessary.
Why? Before upgrade=ok. After upgrade: FAIL.
Can someone at Cisco please throw an SG200-08 into the test lab, update the firmware to the latest rev, plug an ESXi server and an NFS server into it, and see what happens? Your test lab should have this readily available.
The user community has done all the QA work for this bug - especially forum member "Degrummondt" who did the AWESOME Tcpdump caps!
Cisco - please finish our work, fix the bug, and push out an update to the firmware! A warning on the SG200-xx support page would also be appropriate.
Regards, Steve Hornby, MCSE Senior Systems Engineer
Could you please reach out to the SBSC and open a Service Request for this issue? We would like to investigate this issue further. We have not seen this issue in our environment. We would like to capture your configuration and some additional information like captured packets when it happen so we can investigate further.
I would love to submit a service request, trouble ticket, etc. whatever you want to call it. But see no way to do so. Not interested in phone call or online chat.
I just wanted to say I am also having this issue on devices connected through this switch. I wish I would have found this thread a long time ago! I have this switch which feeds my entertainment center and a SG300-10 that my NAS etc is connected to. I just switched to NFS from samba/cifs because there is less overhead with nfs. My media player would not even see my NFS shares. I thought it was the media player so I bought another one and same issue. I didn't think it would be the switch because everything else that goes through it works fine except NFS. Today, just for the heck of it, I bypassed the switch and my media player all of a sudden detects my NFS shares. This has been the most irritating experience I've had. Since I never attempted using NFS until recently I never thought it was the firmware upgrade I did a couple of months ago! I will roll back my firmware and report back shortly.
****UPDATE****
So I rolled back to 1.0.5.1 and my NFS is working through this switch. I have wasted countless hours on this and bought a new media player when I didn't need to. The fact that this thread is months old and there isn't a fix yet is shocking.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
