VPN on DI-824VUP

I bought a D-Link DI-824VUP with the intention of VPNing into my home network, but I'm having trouble configuring it.  I have a cable modem, but I have a host name for the dynamic ip.  The first problem I'm having is that since D-Link doesn't provide  very good service, I don't know what VPN client to use.  I'll be connecting from various locations, so if I understand correctly, I'll want to use the Dynamic VPN.  Any help would be greatly appreciated, and more information is certainly available.
Who is Participating?
Rob WilliamsConnect With a Mentor Commented:
Glad to help in further detail, though I haven't set up the D-link unit, however, have a look at the following article, for your router and the D-link client, if you haven't already seen it.

A couple of things to keep in mind.
-The D-link site, and the site from which you are connecting, have to use different subnets. Therefore if the D-link site uses 192.168.0.x then you will not be able to connect from any site using the same subnet. Thus, it is recommended, if possible you change the D-link site to use something less common to avoid conflicts later. Avoid 192.168.0.x, 192.168.1.x, 192.168.2.x, 192.168.100.x, 192.168.111.x
-When you eventually establish a connection you will probably not be able to browse the D-Link network, and you may not be able to connect to resources by name. This is typical with VPN's and can be dealt with, but at least for now use the IP address such as connecting to a share using  \\\ShareName
- Since you have a dynamic IP, for now, while testing, use the current public IP rather than a domain name service. It just eliminates 1 potential other problem. You can locate the current public IP, the one to which you want your VPN client to connect, by connecting to  http://www.whatismyip.com  form a computer behind the D-link
bantabAuthor Commented:
Well the advice about having different subnets worked great.  I guess that should have been more apparent. I got it to work for the DNS name, so now I'm trying to figure out how to get shares over vpn.  Thanks for the help, and I might be calling again if I have too much trouble.
Rob WilliamsCommented:
Thanks bantab. Can you connect to a share using  the IP such as \\\ShareName  If so it's just a name resolution issue which is common. NetBIOS names are not routable and there fore not broadcast over the VPN. There are a few ways to try to work around this. If you don't have a domain/server environment you pretty well restricted to the first 2:

1) Use the IP address (of the computer you are connecting to) when connecting to devices such as;   \\\ShareName   or map a drive at a  command prompt using  
 Net  Use  U:  \\\ShareName
2) An option is to use the LMHosts file which creates a table of IP's and computer names. LMHosts is located in the Windows directory under c:\Windows (or WINNT)\System32\Drivers\Etc\LMHosts.sam , instructions are included within the file. Any line starting with # is just a comment and is ignored. Open the file with Notepad and add entries for your computers as below;      CompName       #PRE
Hit enter when each line is complete (important), then save the file without a file extension. To be sure there is no extension ,when saving enclose in quotations like "LMHosts". Now when you try to connect to a computer name it should find it as it will search the LMHosts file for the record before connecting.
More details regarding LMHosts file:
The drawback of the LMHosts file is you have to maintain a static list of computernames and IP addresses. Also if the remote end uses DHCP assigned IP's it is not a feasible option. Thus in order to be able to use computer names dynamically try to enable with some of the following options:
3) if you have a WINS server add that to the network cards configuration
4) also under the WINS configuration on the network adapter make sure NetBIOS over TCP/IP is selected
5) try adding the remote DNS server to your local DNS servers in your network card's TCP/IP configuration
6) verify your router does not have a "block NetBIOS broadcast" option enabled
7) test if you can connect with the full computer and domain name as  \\ComputerName.domain.local  If so, add the suffix DomainName.local to the DNS configuration of the virtual private adapter/connection [ right click virtual adapter | properties | TCP/IP properties | Advanced | DNS | "Append these DNS suffixes (in order)" | Add ]
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.