Re: accessing shared drive over vpn

I assume that you get an IP through the netscreen DHCP - right? If you do an
ipconfig /all on your box what do you see under the VPN DNS entry? If it is
not the LAN address of your SBS box it will not work. You can configure your
netscreen box to hand out the server DNS and you shouldn't have any
problems - assuming that the VPN is terminated in your SBS LAN.

--
Claus
"Squeeky Pete" <cfischer225@xxxxxxxxx> wrote in message
news:1177347976.150283.29730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
i have a vpn set up using netscreen remote as my client. (I'll only
include what i think is nessasary to solveing the problem)
so i can connect to the vpn (netscreen box)
i have a wins server set up and my client machine points to that
i have my servers name entries in the hosts file on client machine

when connected to vpn, i can access any network share by ip address,
so if a network drive is mapped via ip address i can get to it no
problem
or if i type \\192.168.10.xxx\sharename i can get to it

i can ping my servers by name but can not get to them via \\servername

when i try and click on a mapped drive, mapped by name i get an error
saying: an error occured while reconnecting Z: to \\servername
\sharename
microsoft Windows network: the local device is already in use. this
connection has not been restored

when i type \\servername i get an authentication window (now keep in
mind i logged onto client machine using cached domain logon
credentials) when i use the same credentail si used to log onto
machine it says unsuccessful, if i use a diff logon name i get: "the
domain controller can not be found to verify that user name"

if anyone can hel por would like mor einfo on the problem please let
me know


thank you sooo much in advance



.

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