VPN client can connect but no network routing

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello,

I've had a Windows 2003/ISA VPN setup and working for some time, but
recently, my XP client PCs cannot access any of the network resources after
logging in. Pinging any of the servers/workstations on the network by IP or
host name is not successful, neither is pinging any successfully logged in
VPN clients from the network.

I've not made any changes to my setup since it's been working. The only
strange thing I have noticed is that the Default Gateway on the connected
VPN client's PPP adapter is blank (I have split tunnelling disabled), and
the subnet mask is 255.255.255.255. The IP address (DHCP allocated), DNS
server IP address, and Primary WINS server address are all correct.

Any help or pointers will be greatly appreciated, TIA!


.

Relevant Pages

  • Re: Setup site to site VPN?
    ... If you're not familiar with VPN setup, i would discourage using routers from 2 different manufacturers. ... Use the same router at both locations and the setup should be easy, and you can call a single vendor to get support if you run into problems. ... As with just about anything in networking, there are standards for VPN, but every vendor tweaks them a little. ... DHCP and windows domain controller) on a different network address. ...
    (microsoft.public.windows.server.general)
  • Re: VPN client can connect but no network routing
    ... > I've had a Windows 2003/ISA VPN setup and working for some time, ... my XP client PCs cannot access any of the network resources ... > successfully logged in VPN clients from the network. ... >, DNS server IP address, and Primary WINS server ...
    (microsoft.public.isa.vpn)
  • VPN and Internet Explorer
    ... We have a VPN setup for ... In Windows XP, I setup the VPN ... When they are on our network and open IE it ... a connection'. ...
    (microsoft.public.windowsxp.network_web)
  • VPN
    ... I need some help with VPN setup. ... business server with 25 users. ... into the server cannot see the network drives. ...
    (microsoft.public.windows.server.networking)
  • 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)