VPN Not Resolving IP Addresses

We use a Juniper Networks SA700 VPN appliance.  It was fully functional for home users to connect, and for an unknown reason, now is not functioning.  Here are the steps at the moment:

The public login page is available
Users can successfully authenticate and start the Network Connect application
The Network Connect application claims to have connected and does provide an assigned IP address within the configured VPN's DHCP range (i.e. "192.168.x.x"). However, when the user runs an "ipconfig /all" from the remote location, they get the following related to the VPN connection:
Ethernet adapter Local Area Connection* 9:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Juniper Network Connect Virtual Adapter
   Physical Address. . . . . . . . . : 00-FF-20-DD-xx-xx
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3dca:4b00:6a89:xxxx%14(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.xx.xxx(Preferred)
   Subnet Mask . . . . . . . . . . . :
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 385941264
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-65-24-0B-00-50-8D-B7-xx-xx

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

I understand from the ipconfig info that the remote computer is not successfully negotiating the network ip address (which is why the user can't even ping our servers as they could when successfully connected).  But I am not versed enough to know how to troubleshoot this issue (I inherited this setup and am not strong with networking devices).

Any help would be greatly appreciated - thanks in advance!
Dan CarpIT DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sounds like the Juniper box needs a reboot to start with.  Have you tried power cycling it?
Dan CarpIT DirectorAuthor Commented:
Thanks bsidfw - I did reboot the box (can't truly power cycle it because I'm not on site today) with no effect.
Dan CarpIT DirectorAuthor Commented:
bsidfw - figured out my problem...

Since the last time I've tested the VPN at home, I had replaced my home networking setup.  The old router and the new router used different subnets and I didn't think anything of it at the time.  Turns out that my new router and the office LAN operate using the same subnet.  By switching my home network to a different subnet, everything now works perfectly.  I'll have to ask the other users who've had problems if this is also their issue, but I'm guessing that it is.

Thanks again for your help!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Big issue when office LANs use 192.168.1.x or 192.168.0.x.   It's a bit of laziness, I've been guilty also.

It's far easier to change the office LAN once than to constantly provide tech support to every home user who is using their router default settings.
Dan CarpIT DirectorAuthor Commented:
Resolved issue on my own.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.