windows 7 laptop can't access sbs 2003 shares when wireless, ok on wired
I have a win 7 pro laptop that is part of a domain with a single sbs 2003 standard server.
when in the docking station / wired LAN connection, the laptop can access the shares, and has a mapped drive s: maps to \\server\share
when out of the docking station, we can ping the server by name and ip (and the wired and wireless IPs for the laptop are on the same subnet as the server (192.168.1.x)
but in windows explorer we can't browse to \\server and when we click on the network drive, we get:
network error
windows cannot access \\192.168.1.5
check the spelling o fthe name. otherwisethere might be a problem with your network....
error code 0x80004005
unspecified error
and
restoring network connections
an error occurred while reconnecting s: to \\server\share
microsoft windows network: the network location cannot be reached
this connection has not been restored
we get these messages even if rebooting out of the dock , so it only gets the wireless IP.
any ideas?
when in the docking station / wired LAN connection, the laptop can access the shares, and has a mapped drive s: maps to \\server\share
when out of the docking station, we can ping the server by name and ip (and the wired and wireless IPs for the laptop are on the same subnet as the server (192.168.1.x)
but in windows explorer we can't browse to \\server and when we click on the network drive, we get:
network error
windows cannot access \\192.168.1.5
check the spelling o fthe name. otherwisethere might be a problem with your network....
error code 0x80004005
unspecified error
and
restoring network connections
an error occurred while reconnecting s: to \\server\share
microsoft windows network: the network location cannot be reached
this connection has not been restored
we get these messages even if rebooting out of the dock , so it only gets the wireless IP.
any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
actually, when the problem first started, a bunch of things were unchecked on the wireless NIC - ipv6, microsoft networking, i think it was, etc. I checked all, rebooted and probelm still existed.