RV082 - QuickVPN / PPTP - Name resolution

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Autourdupc, Sep 12, 2006.

  1. Autourdupc

    Autourdupc LI Guru Member

    Dear all,

    I have a RV082 (firmware 1.3.2).
    When connecting either with QuickVPN or PPTP, I can't resolve my machine name :
    i.e : ping IP address works but ping name does not work.

    What I suggest is to allow the possibility in the RV082 to put the DNS IP address of the computer acting as DNS in the network, either in the QuickVPN and PPTP configuration.

    Actually, the DNS given (in PPTP) is the IP of the RV082.
    What I need, is that the given DNS address is the IP of my DNS in my network.
    With this modification, I can have the same functionnality inside my network and outside.
    In my network, all computers are DHCP client, and DNS given is the IP address of my local DNS computer.

    Waiting for reply.
  2. Toxic

    Toxic Administrator Staff Member

    on your WAN Connection Type did you add the DNS entry for you DNS server?
  3. Autourdupc

    Autourdupc LI Guru Member

    Dear Simon,

    No, I didn't... The WAN connexion is Freebox and DNS are given by the provider.
    In the network, I have a 2003 server acting as CPD, DHCP, DNS, WINS.
    In DHCP parameters, I give IP, Gateway, DNS, NTP.

    What I need when I connect remotely, is to receive the local DNS IP address of my server.

    I'm I true ?
  4. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    IMO...one does not need to worry about name resolution for most types of remote access work. Such as Remote Desktop Connect.

    What I do for all my clients VPN setups, is I set their office workstations on a "DHCP Reservation". I'll create an RDC connection for them on their laptop or home PC..to that IP address. Or they just get in through SBS RWW. Static IPs make it so much more bulletproof, and are so easy.
  5. OpticalMan

    OpticalMan LI Guru Member

    Autourdupc, yes you are correct that this is a valid request for a feature. I want it also. Although, it may never get implemented because for some reason it seems difficult for people to understand. For example, Simon recommended to put the DNS in on your WAN IP config. That is incorrect and won't solve the problem. I think he and others don't understand the need. It's simple. The DNS related assignments for remote users (PPTP and QuickVPN) automatically get assigned the router LAN IP address. Linksys needs to make a setting to allow a custom DNS IP address for remote users. The local LAN users already can be assigned a custom DNS IP on the DHCP setup page. There is a work around for PPTP using windows VPN dialer. It allows you to override the DNS IP. QuickVPN has no alternative other than after connecting to manually change your TCP/IP settings. Or one could use the DNS databse feature of the RV082 and statically define all your servers.
  6. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Yes there's that option...you can go to the TCP properties of your VPN connection...enter the IP of your DC at the office..then in advanced settings...you need to type in your full active directory name in the DNS Suffix for this Connection field.

    That way, your resolution requests will bounce off that domain first, instead of the defaults on your local connection.
  7. Autourdupc

    Autourdupc LI Guru Member

    Dear YeOldeStonecat,

    Of course, we can enter manually some parameters, but in PPTP, the router act has a DHCP for PPTP clients.
    Why do I have to put manually some parameters ?
    It is the work of the DHCP server...

    Before using the RV082, I had a bewan router, and PPTP was working simply.
    I wanted just to replace the Bewan by the RV082 and now, I have to modify all my clients...

    I think that the RV082 should be updated to let the administrator to put the DNS manually for PPTP clients, and of course Quick VPN clients.
    Why giving the IP address of the router ? Why giving the public DNS ? And why not giving no DNS ?

    Remember that PPTP clients has to work has if they where connected inside the local network. If I have to "customize" the client PPTP connexion, it is boring ! And this kind of way is not common (Bewan don't do like that).

    I hope that you do understand my request.

  8. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    I agree..it would be a nice feature....I just don't think it should be a show stopper. Takes a few seconds to edit the DNS section of the clients PPTP adapter. And I find it much more of a relief anyways..to setup all my clients with static IPs on their workstations through a DHCP reservation...and have them RDC to that LAN IP. Takes away much room for error...makes it much more hassle free for me..and that's what counts.
  9. Autourdupc

    Autourdupc LI Guru Member


    Of course, you are also right...
    But in this case, why receiving a DNS address ?
    What is the better address : WAN IP, WAN IP DNS, nothing... I'm not sure that the choice made by the manufacturer is the good choice !

    May be we must have the choice to select witch IP we need...

    And in the same manner, we also need a checkbox to decide if we need the NetBIOS broadcast.
    We have this possibility in the advanced feature of the VPN "Client to gateway". Why limiting the possibilities in QuickVPN and PPTP ?

  10. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Yes...would be better to have the choice of a default WAN obtains DNS, or to insert your own internal DNS..have a separate way to edit this since if one has a DC on their LAN..they would logically want to run DHCP from their real Windows server also. Would be nice...make things a little easier on us. Somewhat of not an obstacle for me though, they way I design my setups.

    I'm not a fan of allowing netbios to pass through a VPN tunnel though...I have a lot of WANs setup, none of them would run this feature....I use internal DNS for all of that name resolution. And on the one I have left running a couple of 9X clients...WINS also. Netbios clogs the pipes too much.

    I think of few of us here would love to see some 3rd party firmware come out for these mighty beasts. All this horsepower...to have something like DD-RV0T! :D
  11. Autourdupc

    Autourdupc LI Guru Member

    Dear all,

    I hope the LinkSys staff will get my SOS to improve modifications on the firmware of RV082...
    Of course, NetBios over TCP/IP is not a good idea, but sometimes it is the good solution to get a working network easily.

    Please, LinkSys, take a look to my request !

    Regards to all,
  12. Mike28

    Mike28 Network Newbie Member

    I know this is an old thread, but if I was looking for it in 2014 then others probably are too.

    I ran into this problem with a Cisco RV082 and was able to figure it out so I wanted to share!

    In my case, DHCP was disabled on the RV082 and it needed to remain that way. I checked the box to enable DHCP on the device (without saving!), entered the DNS servers and WINS server address as if I was going to enable DHCP, then unchecked the enable DHCP box and clicked save. Even though DHCP is still disabled and was never actually saved, the addresses given to PPTP connections will get these DNS and WINS settings.

    Apparently the PPTP server looks to the settings on the DHCP page of the RV082, even when DHCP is not enabled. It just needs to have the check box "enabled" (even without clicking save!) long enough to put your settings in. Save the settings on the DHCP page once the settings are in place and the DHCP is not enabled.

    Hope this helps!
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice