M
Mike Barone
Hi !!!
I have a number of clients who remotely connect to our
server via VPN. This setup worked perfectly until we
recently moved our files from a Workstation server to a
Domain Server. The remote users can map the drives to
their local PCs, but cannot access any files. Whenever
they click on a drive to access, the PC looks like it
hangs, and after a couple of
minutes, they get a message saying "Specified Network
Name is no longer available".
The Workstation Server was a Windows NT 4.0 Server with
SP6A installed. The new Domain Server is Windows 2000
Server with SP3 installed. (I am sure that installing
SP4 will not solve the problems the remote users are
encoutering, because we have some XP PCs here on site
that never joined the domain, yet can access the Domain
Server and access files just fine, so I would need other
options to solve this problem. I think this might be
some sort of authentication problem.)
The remote users are using Windows XP Pro with SP1
installed and is part of the Workgroup Workgroup.
The VPN Software the remote users use to connect on site
are Checkpoint SecuRemote - version FP3 53515.
They can map the drives just fine, ping the server, and
the shares they connect has it set to "Everybody" Users.
Unfortunately, nothing can be accessed remotely.
Not even mapping the drives by IP Address (instead of
server name) gives the same results.
Im sure that this problem has been encountered before and
that Im just missing something minor, but would need
detailed instructions on how to correct. Right now, I am
having the users connect to a couple of office PCs
running Windows XP in Workstation mode, which can map the
Domains drives here on site via REmote Desktop. From
there, they can transfer files to and from their PCs.
Just out of curiosity, does switching from a Workgroup to
a Domian add any type of protocol transmissions ? What
kind of protocol transmissions need to pass through the
firewall when trying to connect to a domain ? The
firewall is controlled by other people, who are currently
on vacation, so if this can be solved without having to
make any modifications to the firewall, it woudl be
greatly appreciated.
Thanks much.
(e-mail address removed)
I have a number of clients who remotely connect to our
server via VPN. This setup worked perfectly until we
recently moved our files from a Workstation server to a
Domain Server. The remote users can map the drives to
their local PCs, but cannot access any files. Whenever
they click on a drive to access, the PC looks like it
hangs, and after a couple of
minutes, they get a message saying "Specified Network
Name is no longer available".
The Workstation Server was a Windows NT 4.0 Server with
SP6A installed. The new Domain Server is Windows 2000
Server with SP3 installed. (I am sure that installing
SP4 will not solve the problems the remote users are
encoutering, because we have some XP PCs here on site
that never joined the domain, yet can access the Domain
Server and access files just fine, so I would need other
options to solve this problem. I think this might be
some sort of authentication problem.)
The remote users are using Windows XP Pro with SP1
installed and is part of the Workgroup Workgroup.
The VPN Software the remote users use to connect on site
are Checkpoint SecuRemote - version FP3 53515.
They can map the drives just fine, ping the server, and
the shares they connect has it set to "Everybody" Users.
Unfortunately, nothing can be accessed remotely.
Not even mapping the drives by IP Address (instead of
server name) gives the same results.
Im sure that this problem has been encountered before and
that Im just missing something minor, but would need
detailed instructions on how to correct. Right now, I am
having the users connect to a couple of office PCs
running Windows XP in Workstation mode, which can map the
Domains drives here on site via REmote Desktop. From
there, they can transfer files to and from their PCs.
Just out of curiosity, does switching from a Workgroup to
a Domian add any type of protocol transmissions ? What
kind of protocol transmissions need to pass through the
firewall when trying to connect to a domain ? The
firewall is controlled by other people, who are currently
on vacation, so if this can be solved without having to
make any modifications to the firewall, it woudl be
greatly appreciated.
Thanks much.
(e-mail address removed)