Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

This has been bugging me a lot today:

I have several computers behind a router. One of them serves Windows shares and is connected to the router by ethernet cable. The main client is connected to the router by Wi-Fi, and could connect to the shares just fine. But today I added a switch to the mix, so that the server is now connected to the switch, which in turn is connected to the router.
Poof, the wireless client can no longer connect to the server's shares. It can still ping it, attach a remote desktop session, etc., but network shares are not working.

Server is Windows 7, client Mac OS 10.5.

What could be going on here?

So far I've rebooted router, server, client and even switch. No help.

Edit: Turns out other clients, and even the same MacBook Pro, can access the shares just fine if/when running Windows as opposed to Mac OS X. My Linux based smartphone connects just fine too.

share|improve this question
2  
So it only has this problem when running OSX on the Mac? If you pop the switch back out of the equation does OSX start working as expected? What kind (make/model) of switch is it? –  techie007 Nov 10 '11 at 20:36
    
Indeed so. The switch is a D-Link DGS-1008D. –  oKtosiTe Nov 10 '11 at 21:21
    
This Mac, whether running Windows or OSX, both use the same network card, correct? Want to try and eliminate ARP cache from the equation –  matt Nov 10 '11 at 21:50
    
Hmm, arp should remain the same if this is a switch. My guess would be that the link speed autonegotiate is failing, and some packet loss is occurring. Does OSX and Windows connect at the same speed (you should be able to tell from the LED) –  Paul Nov 11 '11 at 0:34
    
I'll check. Another hypothesis is that another computer (the reason I installed the switch in the first place) is causing the problem. Will post back later today. @Paul –  oKtosiTe Nov 11 '11 at 10:27
add comment

1 Answer

up vote 0 down vote accepted

It seems to have been a fluke, as a cold reboot (of the Mac) appears to have resolved the problem.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.