VPN to Windows 2003 server

anonymous_at_discussions.microsoft.com
Date: 05/07/04 

Date: Fri, 7 May 2004 01:02:52 -0700

I am attemting to attach to my office network from a
remote site via a VPN. The office is networked via a SOHO
Watchguard router. I have successfullly established the
VPN tunnel from the remote site to the SOHO box using
Watchguard MUVPN remote user VPN software and am able to
ping the server sucessfully. I am not able to see the
shared resources of the server via Windows explorer from
the remote site. Any input as to where I look for my
errors.

After working with the settings I now see the server when
I bring up network neighborhood and when I click on the
server icon in explorer it shows the folders I have set to
share on the server. These folders also have a plus sign
infront of the icons indicating that there are subfolders,
but when I click on the plus sign it simply disappears and
when I then click on one of the main folders after a few
seconds a box comes up that says \\servername\folder is
not accessible. the device does not exist on the network.

Any additional help or direction would be greatly
appreciated.
thank you

Relevant Pages

  • Re: [Full-disclosure] Remote Desktop Command Fixation Attacks
    ... This set of steps is redundant in many places, and it's also enormously expensive, since you're using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator), in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license. ... Your computers necessarily don't have full access to your network infrastructure when they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to be applied. ... Turning on, enabling, and implementing every possible security setting and device you think of is not defence in depth, and will probably only have two effects - your users won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful* security measures. ...
    (Full-Disclosure)
  • Re: VPN with SBS 2003 (not R2) and DSL.
    ... Reading property value for VPN returned OK ... Reading VPN Server Name returned OK ... identical network cards. ... it seems doubtful that SBS will work properly with two NICs ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... on the SBS 2003 server just not sure where to go for help on it. ... Next time I'm at my home PC, I'll VPN in and see what IP info I'm getting ... client PC on your LAN, you should be able to do so from a remote VPN client, ... get the network path was not found. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Error 800
    ... The VPN client IP is 10.0.1.40, this is a private IP address. ... server IP address is 81.137.105.244, this is a Internet IP address. ... not test VPN connection from your perimeter network. ... SBS on your switch to make it work. ...
    (microsoft.public.windows.server.sbs)
Loading