Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[austinak]

Greetings Everyone,

I'm new to the Forum, read the stickies, read some posts I thought might relate to my issue, but haven't found the answer.  I hope someone here can help me out, point me in the right direction, etc...

My office has a DFL-210 with a static IP address and everything has been working great.  The office has recently allowed users to start working from home, so now a VPN is in order.  I have followed the FAQ titled "How do I add a L2TP over IPSec Server using PSK and Local User Authentication" to the letter to configure the DFL-210.  I have also followed the FAQ titled "How do I configure my Windows Vista & Windows 7 computer to connect to a L2TP over IPSec tunnel on my DFL series firewall" to setup the connection to the VPN on my Windows 7 Ultimate PC.

I can connect to the VPN from my Windows 7 PC, and the IPv4 config info that is handed out via the DFL-210 is listed below.

IP Address: 192.168.5.201
Subnet Mask: 255.255.255.255
Default Gateway: 192.168.5.201
DNS Servers: 192.168.5.15 & 24.93.41.126

I can ping the DNS Server (a 2003 Server DC), but only by IP address - not by name (tried "server" and "server.domain.local").  I can map to a network drive on the server using "\\192.168.5.15\share" but not by "\\server\share".  This presents a problem - users that take laptops home are not able to reconnect to their mapped drives that were created at the office using "\\server\share".

Is this normal?  On VPNs I've created with other routers, I'm usually able to get name resolution and ping the server by name.  Also, the subnet mask for the LAN side of the router is 255.255.255.0, not 255.255.255.255 like the VPN client is issued.  I don't know too much about subnet masking, but couldn't my computer's VPN network subnet mask differing from the subnet mask of the local network at the office be causing these name resolution issues?  The server's IP configuration is listed below.

IP Address: 192.168.5.15
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.5.1 (DFL-210)
DNS Server: 192.168.5.15

Please let me know what I am doing wrong, if there is a way to resolve this problem, or if there is a better way to accomplish what I'm trying to achieve.  Any and all help is greatly appreciated.

Thanks,

Austin

[Fatman]

If you need to resolve NBNS names please ensure you have a NBNS server (your server 2003 machine should be capable), and that it is being assigned to your L2TP clients.