Cisco Routers :: RV042 - DHCP Giving Out Wrong Default Gateway And DNS Server
Oct 3, 2012
I have a RV042 router. The problem that I am having with it is that the DHCP is giving out the wrong Default Gateway and DNS Server. There is no option to change the DHCP server IP on any of the settings pages on the router. I am begining to think that there might not be a way to do it. I see that there is an option for the DNS under the DHCP page but the Public IP that is being handed out is not the one on that page. I also have 2 WAN connections hooked up as well a DSL link and a Cable link (the cable link is the primary one).
The following information is provided in an effort to resolve this issue:
IP of Router 10.0.0.2
IP of DHCP Server (the one that is being handed out):10.0.0.1
IP of DNS (the one that is being handed out): 10.0.0.11
What I want to it be.
IP of Router: 10.0.0.2
IP of DHCP 10.0.0.2
IP of DNS 10.0.0.2
So network was running fine for about a year or so. Network consists of 1 Motorola SB6120 cable modem attached to a D-Link DIR-601 wireless router. All settings were default except for SSID and WPA password. One day I just couldn't access internet anymore. I've narrowed it down to the default gateway that is being given out through DHCP. The default gateway that is being given out is the IP of the modem (192.168.100.1) and not of the Router (192.168.0.1). I can't find any option on Wireless router to be able to force the gateway address when handing out the gateway IP. Theoretically I thought I should be able to put router on same subnet as modem as 192.168.100.2 but that still doesn't work. If I set the IP adresses statically on the PCs and give it the Gateway of the Router everything works fine. I should mention this is for my boss' house and basically I dont want him calling me everytime he has a friend come over and I have to talk em through setting up a Static IP.
And just for an example this is what I get if I use DHCP:
IP Address: 192.168.0.155 Mask: 255.255.255.0 DNS: 192.168.0.1 Default Gateway: 192.168.100.1
And If I want it to work I have to change the default gateway to 192.168.0.1 I've tried updating routers firmware and reset to factory default numerous times. Is it possible for a router DHCP stop working?
RV042 router is giving out the outer certificate instead of server certificate. Outlook anywhere is failing and we are receiving certificate errors for any secure site behind this firewall. I'm not talking about remote management. I'm talking about people trying to access our web site, which is secured, and getting an error because the RV042 is giving its own SSL certificate instead of the Server's certificate. Firmware Version: 1.3.13.02-tm. I don't see any updates for that hardware. I do have it working on an RV042 with the same firmware at a different location. How do we turn that off or keep it from happening? Output from a test site Attempting to resolve the host name xxxx in DNS.The host name resolved successfully. Additional DetailsTesting TCP port 443 on host xxxx to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server xxxx on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject:
SN=California, L=Irvine, C=US, O="Cisco-Linksys, LLC", OU=RV042, CN=68:ef:bd:b8:0f:78, Issuer: SN=California, L=Irvine, C=US, O="Cisco-Linksys, LLC", OU=RV042, CN=68:ef:bd:b8:0f:78.Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name xxxx doesn't match any name found on the server certificate SN=California, L=Irvine, C=US, O="Cisco-Linksys, LLC", OU=RV042, CN=68:ef:bd:b8:0f:78.
I have RV042 on my remote network, i have problems with VPN connection , user can connect to RV042 but only inside IPs that can ping from vpn user.Is it any way to make the traffic from Rv042 will back to RV042 . maybe with nat.. in example below 192.168.5.100 is my lan IP from my DSL dhcp, and 172.27.0.20 ip on remote, traffic not back to my pc/vpn client, what i want is to translate 192.168.5.100 to RV042 LAN ip address
Just installed RV042 router. And it's giving out router certificate instead of server certificate so people who are trying to access our secured server are getting errors. I'm not talking about remote management. I'm talking about people trying to access our web site, which is secured, and getting an error because the RV042 is giving its own SSL certificate instead of the Server's certificate. How do we turn that off or keep it from happenning?
The RV042 firm version is v4.0.0.07-tm (Aug 19 2010 19:19:50)
I've configured a VPN IPSEC on my ASA5510. It Assigned IP/NETMASK/Gateway via a DHCP Server on the LAN.The problem is that when a client is connected to the VPN , it takes the right IP and NETMASK. ( 192.168.1.109 / 255.255.255.0) but the Default Gateway is wrong ( 192.168.1.1). It should be the default Gateway of my LAN router ( 192.168.1.229).
This is terminating on an ASA c5510 sec+ running 8.3(2) Client devices running XP with the same VPN client get an address from the ASA pool e.g. 10.10.50.1 with no default gateway. Users are able to connect without a problem. Windows 7 (32bit) clients with this same VPN client get this address but get a default gateway 10.10.50.2 and are unable to connect for obvious reasons.
After we change the firewal from PIX515E to Fortigate311B, one notebook which installed Cisco PN client 188.8.131.520 in WIN7 64bits can not access VPN because the default gateway is not correct. For example the IP get from Ip pool is 172.28.22.10 but the default gateway IP is 172.28.22.1. ?
I have more than 10 PC om my Workgroup, using DHCP on network, but I have one PC alwaws got wrong IP (auto from dhcp), and can't connect even using static IP (status connect, but can't ping to gateway and other IP)Here "ipconfig /all" on one of PC that work. [code]
I'd like to add a WRT54g2 to my LAN. I'd like it to communicate with my existing LAN router, and not to talk directly to the LAN. Therefore, in Basic Setup, I don't have the top part (Internet Setup) configured. Is that a mistake?But, it seems that when I enable DHCP, it hands out its own IP as gateway, and then doesn't seem to send the traffic on upstream. When I configure clients manually with the real router IP, they work fine.
So, I'd like, I guess, Linksys to forward traffic on a static route to real router. How do I do this? Adding a route to real router yields the error, "maybe default route already exists."
ipconfig /all reports one of my three DNS servers as 192.168.1.1. My Default Gateway and DHCP Server are also reported as 192.168.1.1. This is from a recently installed Valet M10 updating an old Linksys router. The Linksys reported the three DNS servers octets independent of the router's ip and other default settings.JK
Internet <-> Residential Gateway (RG) from ISP (OEM: Pace) [192.168.1.254/255.255.255.0] <-> RV180 [192.168.1.253/255.255.255.0] <-> SG500 switch [192.168.1.250/255.255.255.0] <-> rest of network.
I know this is a cascading LAN-to-LAN arrangement. The cable from the RG to the RV180 is from a LAN port on the RG to a LAN (not WAN) port on the RV180.
I eventually want to segment my network into a few VLANs from the RV180 down. I am aware most people would recommend DHCP on the "primary" router, but the RG is non-VLAN aware, so I figure I need to handle the DHCP off the RV180. At the same time, I have also opted not to do a LAN-to-WAN cascade because I want to retain the ability to configure the RG from the rest of the network and not have to cart a computer over to the RG to do it.
On the RG, I've disabled DHCP, and placed 192.168.1.253 in the DMZ.
On the RV180, I've enabled DHCP and put it in Router mode.
The issue is that I do not have any Internet connectivity. If I allow the computers in the network to receive IP addresses over DHCP, the default gateway that is communicated is 192.168.1.253, which is the RV180. If I configure static IPv4 information on my computers to point to 192.168.1.254, I am able to connect outside, as you would expect.
How can I get the RV180 to pass out DHCP IP addresses, but point to 192.168.1.254 as the default gateway? I thought the solution might be to create a default route (or something). I went to the static routes tab but it wouldn't let me enter 0.0.0.0 as a destination IP to route through 192.168.1.254.
Further down the line, is it possible for both the RG and the RV180 to connect directly to the SG500, along with the other nodes in my network? That way the RV180 only serves to maintain the VLANs and pass out IP addresses via DHCP, instead of having it be the choke through which everything goes through on the way out?
I have two Cisco RV042 Routers, they are being used to connect two offices, i have created a standard gateway to gateway connection, fixed public ip addresses on both sides and everything works fine, except when the tunnel gets disconnected, it does not connect back automatically, i have to log into either router console and click the connect button to get the tunnel working again, this is really annoying since it happens once or twice a day at least.
I have a 3911 router with a 1242 AP. The problem that I have is that when the user is trying to connect, the user get the OS Ip address 169.254.168.154 and I see that when I do the "show dot11 association" command, but when I do sh ip dhcp binding on the router I see
172.19.9.141 0100.18de.74db.14 Jan 31 2011 11:14 AM Automatic
The router is seeing as if the router gave the ip address to the user, but the reality the user was assigne the OS ip address 169. I did "debug ip dhcp server events" and I got the following:
Jan 31 11:09:06.752 EST: DHCPD: Seeing if there is an internally specified pool class:Jan 31 11:09:06.756 EST: DHCPD: htype 1 chaddr 0100.18de.74db.14 Jan 31 11:09:06.756 EST: DHCPD: remote id 020a00000a58218400000000Jan 31
I have 2 units Cisco WLC 5508 running software version 7.0.220 with 70 over units Cisco AP 1262N and 1242AG. Some of wireless clients having problem to get the correct IP address from the DHCP server. There are 2 units of Microsoft DHCP. Both DHCP server ip have been configured on the Interface at the WLC. The core switch also being configured with ip helper. I've attached the debug output of one of the wireless client during the problem.
I rdp into our server 2008 via IP. This is a router on ip 0.1, this is forwarded to my server on IP 0.3. This server was setup with DHCP default gateway of 0.1. We added a new outside connection on IP 0.2. I was talked through the changes so that internal DHCP requests went to gateway IP 0.2 but RDP still used 0.1. I plan on getting rid of 0.1.Where is the setting to change the RDP to use default gateway of 0.2?
I have been having some trouble with my internet for awhile now. It fine one second and than it will get really slow and eventually stop working. When I troubleshoot to see what the problem is it either gives me DNS server is not responding or default gateway is not available, sometimes it will give me both. It says it fixes the default gateway problem but it will show up again 5 minutes later.
Here is my ipconfig /all Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
i have a cisco router that has dhcp configured, the router ip address is 10.10.10.***. all computer that attached to the router are using static ip and works fine but when i am connecting my laptop using wireless in gets an 192.168.1.*** address.
I Connected two connection on my computer. One is LAN connection that is my Office network connection, and another one is USB Wireless device. I was using those two connection on the same computer. Now i office Network admin came and changed the Setting from the LAN Propertied. he removed the default gateway of my server IP address from DNS Server and he gave that ip address to the Default gateway in the LAN Propertied tab. After which i cannot access the wireless. If i change to ip address to the DNS Server my wireless is working..what is DNS Server and Default gateway..... Also i want to know the diffrence between that..
I used the Cisco Configuration Professional to add an Easy VPN Server to my 3825. I'm able to connect when remote but I can't ping the default gateway of 192.168.1.1 which is in the same network as the VPN DHCP pool. I can access every single other device on the VLAN segments but not the default gateway which means when i connect I can't look at my router. And there's more, I cannot ping anything offnet (ie 184.108.40.206).
Attached are some images which show some details from the client during the VPN connect and a few from the router (i had to use the lan switch as a jump host). If you can figure this out before I go back to the coffee shop to test this tomorrow I will send you a cake.
I've got half a dozen RV042 routers in various locations. They are running v4.0.0.07. Seemingly randomly, I got the 502 Bad GatewayThe CGI was not CGI/1.1 compliant. error when attempting to log into the web interface with google chrome (same with IE too). This happens from the LAN side. I actually didn't notice it until my Opsview monitoring software threw up a critical when it didn't get an http response. The router is otherwise actually working just fine.Since the first occurrence, more of my routers have developed the same error.
I've tried different browsers, clearing caches, though I'm not surprised those efforts were fruitless, as there is clearly a problem even when no browser is involved (nagios). The nagios http check also returns a 502 Bad Gateway.
I set up an RV042 as a VPN gateway for a client a year ago. It is running firmware 220.127.116.11-tm (Feb 13 2009 13:03:21). I created a new certificate. When I download the client certificate, It comes as a .zip file. One the can not be opened by a zip utlity (windows, Winzip or 7 zip). It looks like I can just rename the file to a .pem file, but I want to make sure that is right. They were getting QuickVPN timeouts, but that looks like it was fixed in 1.3.13.
I can connect to the internet via wireless just fine, and everything will be hunky-dory for a while. After a while, however (this varies anywhere from a day to a week), there will be a small hiccup on the connection, and then something fails in the Acquiring Network Address stage. My computers will get an IP, but they will not get the default gateway or DNS server.I have tried a plethora of fixes, from simple computer reboots to fiddling with all sorts of settings, and nothing works to reestablish the connection. My father has also tried fixing it, to no avail. I have to go and reset my router, which also interrupts TV service, because it is through AT&T U-Verse. Needless to say, this does not make other people in the household very happy, and I really shouldn't have to be resetting my router every couple of days like that. My PC uses a Netgear WG111v3 adapter and is Windows XP. My laptop has on-board Wifi and is Windows XP Professional.
I am using a RV016 (192.168.1.2) as a router and DHCP. It automatically assigns its own IP which is 192.168.1.2. I can not set my RV016 to assign a Default Gateway IP of the server. The workstations will connect to internet via this server (192.168.1.1)
I have router Linksys RV042 v1.2 with latest firmware Version: 1.3.13.02-tm. And I'm using QuickVPN v 18.104.22.168. I've setup VPN connection with values, below: But every time I'm trying to connect to router by VPN it always popup a window "Remote Gateway not responding".It occurs when I'm trying to connect to VPN behind other router, when I'm connected directly to Internet the connection is established.But I'm connecting to other networks using VPN and it's working properly (behind the same router), so I think it's problem with RV042 configuration but I don't now weher.
I am trying to setup the following. We have an RV042 Router and are using it as our gateway at the office. In the office we are using a Windows Domain abc.lan with DHCP of 10.0.0 - 10.0.0.254. The Router/Gateway is setup with a Static IP of 10.0.0.100.A couple of our office employees would like to work from home via VPN using their laptops. With the many options available for this router, I am not clear as to which options and what settings I should set.
When I create a virtual switch on hyper v, i lose network connectivity and the default gateway is missing I have to manually put the default gateway in and disable and re enable the network adaptor each time the server restarts in order to get network connectivity. I am running windows server 2012 Hyper V Virtual Ethernet Adapter loses default gateway server 2012
Comcast installed a new fiber 10M EDI internet connection in our facility the other day and found out it is our responsibility to provide a layer 3 gateway to map the internet connection to the 14 public IP addresses they assigned to us. We are using RV042 for our existing networks with a T1 we had.
Will the RV042 provide the gateway function to route the single IP address comcast provided to the 15 public IP addresses? If so , can you provide the configuration example on this process?
Comcast EDI Connection ---> ???????? ----> 14 Static External Addresses
Interconnect Block 22.214.171.124 / 255.255.255.252.Comcast Gateway is 126.96.36.199Clear Layer 3 device WAN interface: 188.8.131.52
Usable IP Block 184.108.40.206/28Mask: 255.255.255.240Usable Addresses: 220.127.116.11 - 18.104.22.168
2) Allow all port 80 connections, and forward to 10.4.20.60
3) Allow all port 443 connections, and forward to 10.4.20.60
4) Allow port 22 connections from specific IP addresses, and forward to 10.4.20.60
5) After a remote client has connected using Client to Gateway VPN, allow that remote client to access anything on the LAN
I'm able to do #1-4 above, but I can't get #5 to work. Or I can get #5 to work, but can't implement the restrictions I need in #1-4. Attached are some relevant screenshots. I think the problem is that I have Forwarding rules set up that require me to have a firewall rule to Deny All Traffic from WAN1 (unless I'm specifically allowing it). In the Access Rules screenshot, rule #6 is the problem. If I enable it (thereby denying all WAN1 traffic), then VPN clinents can't access anything on the LAN. However if disable this rule, VPN clinents can access anything on the LAN, but the firewall also opens up all outside connections to SSH, since that's set up in the Forwarding rules. I would have thought that once a remote client is connected using client to gateway VPN, then that client is considered to be on the LAN, as far as the firewall is concerned. Thus a firewall rule (like #6) that is specified for WAN1 shouldn't effect remote VPN clients.