G
Gordon
Set up is this: One desktop wired to hub, one laptop wireless to WAP
connected to hub. Both machines running XP Pro SP2 and both are at the
current level of updates. ZoneAlarm is installed, and the firewall component
is configured to allow the full range of the LAN IP addresses on both
machines.
I set up a mapped Network Drive on the laptop, pointing to a shared folder
on the desktop. All is well. I want to transfer some large data folders from
the laptop to the desktop. As the wireless transfer rate was quite slow due
to other users, I decided to take the laptop to a wired network node and
connect that instead of using wireless. Well, what do you know? Suddenly,
and with NO CHANGES WHATSOEVER, the laptop doesn't see the mapped drive.
WHY? Why should the only change of connecting to the network via a cable
rather than wireless mean the new mapped drive isn't visible? All the others
that were set up previously are there and can be accessed - just this one
......
HELP!
connected to hub. Both machines running XP Pro SP2 and both are at the
current level of updates. ZoneAlarm is installed, and the firewall component
is configured to allow the full range of the LAN IP addresses on both
machines.
I set up a mapped Network Drive on the laptop, pointing to a shared folder
on the desktop. All is well. I want to transfer some large data folders from
the laptop to the desktop. As the wireless transfer rate was quite slow due
to other users, I decided to take the laptop to a wired network node and
connect that instead of using wireless. Well, what do you know? Suddenly,
and with NO CHANGES WHATSOEVER, the laptop doesn't see the mapped drive.
WHY? Why should the only change of connecting to the network via a cable
rather than wireless mean the new mapped drive isn't visible? All the others
that were set up previously are there and can be accessed - just this one
......
HELP!