VPN to share on network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a 2K Server (SBS) with a client who needs to remotely log into server
VIA DSL connection. Routing & Remote Access shows VPN connection is made.
Outlook 2002 is able to pull mail. But we are unable to connect to a share on
the network. We are unable to browse to any share and when we type in the
locaton of the share we are told the path is "unavailable." Any suggestions?
 
Check and make sure the corporate network and the home network have
different ip subnets (different internal ip addressing scheme)
Todd said:
I have a 2K Server (SBS) with a client who needs to remotely log into server
VIA DSL connection. Routing & Remote Access shows VPN connection is made.
Outlook 2002 is able to pull mail. But we are unable to connect to a share on
the network. We are unable to browse to any share and when we type in the
locaton of the share we are told the path is "unavailable." Any
Click to expand...
suggestions?
 
Thanks Eugene

Excelent point, but Im sure this is not the problem. For some unknown
reason, the internal network was set up on the 10.0.0.x. I have no rason to
believe (but will check) that the user has a "home network" setup, but given
she is behind a DSL modem, it is very likely that she is on a tratidional
192.168.x.x network.

Anyone else got a suggestion. The problem is still open. (I have the user is
installing all Microsoft updates this evening.)
 
Well, you raise an interesting point. I need to note however that I have no
problem connecting from my XP Pro WS (in a different location.) That leads
me to believe the problem is a setup problem with the XP Home workstation.
(Note, I can not browse the VPN site either, but at least I can map to a
location, knowing the correct address. My client can't.) This is a SBS2000
domain so it has only one DC. \\server\share does not connect. I will suggest
that she try using the IP Address (thought I can't imagine why my WS could
translate Server Name into IP address and hers can't)
 
Thank you for the pointer. I have not yet had a responce to the suggestion of
using the IP rather then the share, but depending on the responce to that, I
will point out this article to the client. The WS at home is personal
equipment that the employer "allows" her key staff members to use when it is
necessary to work from home. I doubt she will consider upgrading the systems.
And of course you know the responce will be "but it use to work." Why does'nt
it work now?

Guess I will have to give that one some thought before I try to give an
answer.

Thanks for your pointer.
 
Name Resolution Guys. Name Resolution.
How is the client resolving network names?
WINS, DNS, HOSTS etc., ????
The clients need to use a Name Server/Service inside the VPN inorder to ID
what is on the network.
 
Why thanks for your contribution however if it cannot connect using the
\\ipaddress\share then it is NOT a resolution problem.
 
Back
Top