RV042 second DHCP issue

Hy all,
I have a CISCO RV042 in a network with 2 subnets 192.168.1.x and 192.168.2.x and I want multiple DHCP on both subnets. How can I do that?
If I use a second router for the second subnet (192.168.2.x) to use its DHCP. The bandwith management will work? Do I need port VLANs?
The network is like this:
The RV042 is the main router thru it we acces the internet, it also suplies DHCP 192.168.1.x, I enabled multiple subnet for 192.168.2.x.
The reason I want 2 subnets is beacause I have 2 acces points for wireless clients and I want to use rate control on WAN with bandwith management from RV042 too give wired clients more bandwith than wireless clients.
I know that RV042 doesn't supply multiple dhcp like RV180,but I needed dual WAN.
Thank You

Hi,
Thank you for the answer, but my issue remains, below I tried to write a little bit more
If I make the configuration like this:
On CISCO RV042:
Port based VLANs:
VLAN 1 on LAN 1
VLAN 2 on LAN 2
On AT-FS750/24 switch:
Port-based VLANs:
VLAN 1 for 2,3,4 ports where 2,3 are the AP's (TL-WA901ND) and 4 uplink to RV042
VLAN 2 for the rest, let's say 5,6,7,8,9, etc ports that are for wired clients.
Tagged-based (802.1q):
VLAN ID 11 for 2,3,4 ports where 2,3 ports are tagged are the AP's (TL-WA901ND) and 4 untagged uplink to RV042.
VLAN ID 22 for 2,3,4 ports where 2,3 ports are tagged are the AP's (TL-WA901ND) and 4 untagged uplink to RV042.
On AP's (TL-WA901ND):
Multi-SSID with tagged based VLAN:
SSID 1 on VLAN ID 11
SSID 2 on VLAN ID 22
If I use the second router (not supporting VLANs) only for DHCP for the wired clients with the configuration:
-In the WAN I'll plug RV042 LAN 2 (VLAN 2) and from its LAN 1 I'll connect LAN 5 (VLAN 2) in the switch.
second router WAN:
IP:    192.168.2.2
SM:   255.255.255.0
DG:   192.168.2.1
DNS: 192.168.2.1
For DHCP
LAN1:
IP:   192.168.3.3
SM: 255.255.255.0
It will work to split wireless from wired ?
How can I split the 2 wireless networks in guests and business more efficient?
Let's say the wireless clients from "SSID 1" have to have a guaranteed bandwidth.!
How can I set it up so the wireless clients gets different IP class on the 2 wireless networks?
Can I use the rate control from RV042 on the IP (192.168.2.2) of the second router?
My problem is that I need all the subnet available from RV042 DHCP for the wireless clients (192.168.1.x), because RV042 can route only in class C (254).
I configured the static IP's in 192.168.2.x subnet for Ethernet equipments, I used multiple subnets from RV042.
Momentarily I use COS from the switch for the tagged VLAN to prioritize the traffic, but this is no longer an option for me.
Can a CISCO RV180 make a difference in this configuration?
Thank you,
Dragos

Similar Messages

Need a how to: RV042 second DHCP

Hy all,
I have a CISCO RV042 in a network with 2 subnets 192.168.1.x and 192.168.2.x and I want multiple DHCP on both subnets. How can I do that?
If I use a second router for the second subnet (192.168.2.x) to use its DHCP. The bandwith management will work? Do I need port VLANs?
The network is like this:
The RV042 is the main router thru it we acces the internet, it also suplies DHCP 192.168.1.x, I enabled multiple subnet for 192.168.2.x.
The reason I want 2 subnets is beacause I have 2 acces points for wireless clients and I want to use rate control on WAN with bandwith management from RV042 too give wired clients more bandwith than wireless clients.
I know that RV042 doesn't supply multiple dhcp like RV180,but I needed dual WAN.
Thank You

Wrong forum, post in "Small Business routers". You can move your posting with the Actions panel on the right.

Wierd DHCP Issue

Hello All,
I facing a very wierd DHCP issue and would like to know your thoughts on it.
I have my wired clients on vlan 1 and wireless cleints(eap-peap) on VLAN 2.
We are facing an issue where multiple wired clients who were on access port vlan 1 are receiving IP address from wireless subnet(vlan2) -their DHCP server was the WLC virtual gateway IP address(1.1.1.1). This is causing an outage to few wired clients.
The WLC trunk does not have vlan 1 allowed on its ports and all APs are in local mode and all on access vlan.
I'm not entirely sure whats causing this, but only way I think this is possible is that 'A Client' laptop has his network connections bridged - his wired nic on VLAN 1 and wireless NIC on vlan 2, acting like a WGB, which is causing new wired clients(vlan1) DHCP broadcast request forwared through the bidge mode laptop to AP--> WLC. Do you think this is possible??
Havent been able to identify which client is causing this issue yet.
Has anyone faced a similar issue and anyway to block this through WLC/ACS policy?
Thanks
Jino

Hi,
Might we consider to make use of network monitor to take a look at the traffics for the 1.1.1.1 address?
How to use Network Monitor to capture network traffic
Download link here:
Microsoft Network Monitor 3.4
Best regards
Michael Shao
TechNet Community Support

Very weird dhcp issue

We've started 're-vlanning' our main location here, breaking up depts
into their own vlans.
All seems ok so far, aside from a real doozy.
For the IT vlan, we have one address that will not talk to our web
content mgmt appliance. It's the 2nd address in our assignable pool,
and it doesn't matter if it's dhcp or statically assigned, that address
will not talk to that device.
That is the *only* device that cannot be reached from this particular
address in our dept vlan, every other one works fine.
Any ideas on this?
Stevo

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> and it doesn't matter if it's dhcp or statically assigned, that
> address
So.... the title of this thread should actually be 'Very weird non-DHCP
issue', since your own testing confirms this has nothing to do with DHCP?
If you do a LAN trace on this machine as well as your web content
management appliance do you see packets on either side? Both sides? If
not on both sides but you do on the source (workstation) side see
packets going out, then get LAN traces after each network device
(switch, router, firewall, etc.) to see when the packets disappear.
Feel free to post the LAN traces somewhere with descriptions of IPs,
ports, and what you should be seeing, if you want to post them somewhere
for review.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP4jFPAAoJEF+XTK08PnB55aMP/3Rg9u6LX6jFCXGYuex/oXdS
NZ/liqfCgjyIcykWWeKGgdtm2I7JZOcFiG8YW2le55mcltvCL1VJW +1VGng4kZER
0f4hjfyQ3CcQ6HIU3RM6VL5U2Pblb80MsEQe0qo0xgtPXipmjs i7Q0xIv9p0wT7A
7JMkfgM9tfuI5Yro+BDLfSIkFWicKuKs1sKpNugKalPuyyRrzW IiznoalIKFshon
a40ETLJVZmngBYfqfeZL9nPNsFlveFNXrDkdbl2WbaprsHtNnA NwZfVUIlc5kOCT
MknY0GXof4/tk149OVCCLgjEzoRtTIZH0BJTHQwW7ANkWUUNYwi49+Mk46V0o awl
oe1aA+NK9gl2bWXWLCtTro4ERSVMvkcI0OffytrfcBsqdCKg/g3QPMjV3kiVEULI
xnSTsqFgOl2qO8qGaL6FJtk39ZBnCwqDPtmoNt93OK4hAhWBuA Xihc+kiQHrwkpO
O04quZu8qQG6A6qwFDr+r+QqarFR3kielfvi7H6o5iLfZn/sDhvijGOAknJVctH8
j8fezki9PMznkcT+of2Oe4T99K9fChN2WFSgUKdlpkYSjbkmjP fdbWloou+WBjCm
7hHwnAbKPPgoN8aPPfw9rG9E+K/0YW2kt4wRu79BEDvF6eMv0UdDPE1qPuw1ttmm
jg2zzMZDkgIG39A0P3u7
=+fCy
-----END PGP SIGNATURE-----

6500 DHCP ISSUE

Hello All,
I am having an issue do DHCP from the 6500, and was hoping someone cant help. So, I tried to setup DHCP from the FWSM to the clients and this worked fine with giving out the IP, however the gateway for devices on the inside is supposed to be the 6500, not the FWSM, which is why the clinets wouldn't get out to the internet. Do I need to set up DHCP relay on the FWSM or does anyone know the way I can setup DHCP on the 6500 to give out IP's to the clients. Again just to reiterate, when I setup DHCP on the FWSM the clinets get the IP's but do not get out to the internet and when I setup DHCP on the 6500 the clients do not get an IP. Also I know tghis is a dhcp issue becasue when I assign a static address on the network the clients get out fine. Thanks in advance for the help!
6500 Config
ip dhcp pool TEST
   network 1.1.1.0 255.255.255.0
   default-router 1.1.1.1
   dns-server x.x.x.x y.y.y.y
FWSM Config
FWSM/TEST# show run
interface Vlan3
nameif outside9
bridge-group 1
security-level 0
interface Vlan203
nameif inside9
bridge-group 1
security-level 100
interface BVI1
ip address 1.1.1.4 255.255.255.0
passwd 2KFQnbNIdI.2KYOU encrypted
access-list INSIDE1_IN extended permit ip any any
global (outside1) 1 x.x.x.x
nat (inside1) 1 1.1.1.0 255.255.255.0
access-group INSIDE1_IN in interface inside1
route outside1 0.0.0.0 0.0.0.0 1.1.1.1 1
FWSM/TEST#

Hello Alain,
Thanks for your quick response. I attached a Diagram of the layout. Just to let you know this is an FWSM with many virtual contexts and most including this one that are Transparent. I understand that I need an access-list on both ends to specifiy so the FWSM opens it, I am just having issue because the FWSM sees this as unsual traffic and the access-list needs to be on-point to work. Thank you for the response and I'll look forward to hearing back from you.

VRF and DHCP issue

VRF and DHCP issue
We have a 6500 ( 12.2 (33) SXH5 ) that has a VRF running for our guest network. On this 6500 resides the DHCP pool with a range defined for our guest network. We have a stack of 3750's (12.2 (46) SE) connected to the 6500 with a L3 connection. The 3750's have a local guest VLAN with its gateway defined in a VLAN interface. This VLAN on the 3750 has an IP helper address pointing to an IP within the VRF on the 6500. When debugging DHCP on the 6500, a request is received and sent back out. The client never receives this request.
If a static IP is applied, the client is able to communicate anywhere within the VRF successfully (including pinging the IP within the helper-address. As many posts have pointed out - there is no VRF <name> under the ip dhcp pool <name> within the 6500. I am just wondering if anyone else has run into this and what their solution was.
Thanks.

Hi,
I have tested the dhcp server and vrf on Cisco 3640 and it is working without VRF under the ip dhcp pool. Please ensure that you have configured routing for the dhcp-relay agent(VLAN facing dhcp client on 3750 in your case).

RV220W second vlan DHCP issue

Hi all,
I have a Cisco RV220W router (firmware version 1.0.4.17).
I would like to have two separate networks with the following specifications:
Netwrork1: address range for the network is 192.168.0.1-254. All devices should be able to reach eachother within this network and connect to the internet either on LAN or through Wifi. From this network I should also be able to reach the device management page of the router. Also the devices should get the ip addresses throgh DHCP.
Network2: address range for the network is 192.168.5.1-254. All devices within this network should not be able to reach the devices in network1. All devices on this network should reach the internet through Wifi only. Device management page should not be available on this network.
I have configured the router as shown in the attached screenshots but the problem is that in Network2, devices get IPs from the 192.168.0.1-254 range and not from the 192.168.5.1-254 range. Also there is no internet on these either.
Any help would be greatly appreciated.

Good morning
Thanks for using our forum
Hi mate, my name is Johnnatan and I am part of the Small business Support community. To add to Tom´s post you could “Isolate”, your networks enabling this feature, and disabling the Broadcast SSID of your Network1.
I hope you find this answer useful, *Please mark the question as Answered or rate the answer so other will know when an answer has been found.
Greetings,
Johnnatan Rodriguez Miranda.
Cisco network support engineer.

RV042, Load Balance issue

Hello,
I'm a newbie to routers and on this discussion.
I've purchased a Linksys RV042 hoping I could connect my two ISP.
Both of them are 1/1 Mb, first is DSL second PPPoE connection.
The problem is that on system summary page it doesn't show me that second WAN is connected. Even when I trying to manually connect to Internet it doesn't help.
When this connection is in Load balance Mode, internet is very slow, sometimes it's even disconnected.
My question is:
How to configure Load Balance properly?
I've tried this page:
http://www.cisco.com/en/US/products/ps9923/products_qanda_item09186a0080a36632.shtml
but it didn't helped.
Or maybe it's just a demo of this option and doesn't work at all?
Thanks for the reply.....

Eliviszopa,
Hi. My name is Tiya and I am one of the Cisco SMB Support Engineers. I have been eyeing your post and I would like to add a few recommendations.
From what I've gathered, you are having an initial problem with your Dual-WAN configuration, in that you are unable to have both WAN interfaces Live at the same time. I will list a few things that will help you in determining if there is an issue with your RV042's Dual-WAN configuration and connectivity.
I understand your Network Topology to be: [ISP Modem 1 & ISP Modem 2]---->RV042---->LAN Clients (PC).
First thing, we need to ensure your router it at the most current firmware version for optimal performance. The RV042 series routers are currently in their 3rd HW revision, so we also need to ensure we download the firmware that is compatible with the HW version of your RV042
To locate HW version:
Look on the bottom of your RV042.
You will find the Serial Number and MAC      address sticker.
The HW Version will be visible by the      Model Number on that sticker.
Image below has a Red Square around the      Model Number and HW version of an older RV042 as a reference. HW is indicated      with 'v' and rational number, i.e. v1.1, v2.0. Your sticker may look      slightly different, but the content will be the same:
Now that we are certain of the HW version, check the release notes below to check the best firmware version for your RV042. I have provided a link below to the RV042 Release Notes:
Firmware v 4.0.0.7 Release Notes:      http://www.cisco.com/en/US/docs/routers/csbr/rv0xx/release/rv0xx_rn_v4-0-0-7.pdf
Firmware v 1.3312.19-tm Release Notes:      http://www.cisco.com/en/US/docs/routers/csbr/rv042/release/notes/RV042_RN_v1-3-12-19-tm.pdf
If your RV042 is using neither of the 2 firmwares, follow this link to download the correct version for your router:
http://www.cisco.com/cisco/software/type.html?mdfid=282414010&flowid=784
I would recommend you download and      'flash' your RV042 with the current compatible version of firmware to      address the possibility of software corruption.
Now, we need to reset your RV042 to factory defaults to remove any parameters previously configured and also, in essence, clear the router's memory so that we can start afresh. When this happens, your RV042 will return all settings to their default state; in other words, it will be as if you are pulling it out of the box for a new install. To do this:
Disconnect the RV042 from your network,      so that the only item the RV042 is only connected to the power outlet.
Locate the reset button on your RV042.      This will be on the front of your router and it will be recessed a bit.
Use a small tipped item; paperclips      usually work best, to hold down the reset button for 30 secs. Anytime less      will not guarantee a full reset to factory defaults.
Connect your RV042 to your PC. After      about 30 secs, ensure that you have an IP address of 192.168.1.100 on your      PC.
Now, let's test each WAN port with each of your ISP connections.
The next few steps will take us through a process that will ensure both WAN ports are working, and ultimately will help is in determining your Dual-WAN connectivity performance.
Connect one of your DSL modems to WAN1 and configure the WAN1 interface accordingly:
· DSL connections typically are UN-bridged by default; where you will see the modem is performing NAT. You will use DHCP as the WAN tupe for UN-bridged DSL connection types. This UN-bridged state can be recognized quickly in a couple of ways.
o    There is a PRIVATE IP address displayed as the WAN1 IP address, e.g. 192.168.x.x. where X is a number 0-254, 10.x.x.x where X is a number 0-254, or less commonly, 172.16.x.x where X is a number 0-254.
o    When connecting to the modem directly to your PC, you are able to reach the Internet.
o    If your DSL connection is UN-bridged, you must make sure the LAN IP Subnet of your Modem and Router are NOT the same.
o    Again, you will use DHCP as the WAN type for UN-bridged DSL connection types.
· DSL connection that is Bridged will require a PPPoE Username AND Password. This PPPoE username and password will be entered on the RV042 under the WAN type PPPoE. PPPoE connections can be quickly recognized in the same manner:
o    There is a PUBLIC IP address displayed as the WAN1 IP address AFTER correctly configuring WAN interface to use PPPoE and using correct UN/PW.
o    You are NOT able to reach the Internet when connecting your PC directly to your RV042.
· Contact your ISP to assist you in determining the bridged state of your modem to be absolutely certain.
2.     After you have properly configured WAN1 and confirmed Internet connection, configure WAN2 in the same fashion.
3.     Change Primary WAN to WAN2 by going to the following location in the RV042:
· System Management>Dual-WAN> Smart-Link Backup Primary : WAN2 (change this option)
4.     Disconnect DSL Modem from WAN1 and connect to WAN2.
5.     Power cycle the DSL Modem, RV042, and also disconnect your PC from the router as well while it is powered down.
6.     After about 5-10 sec, and in this order, power on your Modem, power on you RV042, and reconnect your PC to one of the LAN ports of your RV042
7.     After about 30-60 secs, test for Internet connectivity.
Now we will do the same for your other ISP connection.
1.     Disconnect all devices from the RV042, save your PC.
2.     Change Primary WAN to WAN1 by going to the following location in the RV042:
· System Management>Dual-WAN> Smart-Link Backup Primary : WAN1 (change this option)
3.     Connect 2nd ISP connection to WAN1 and configure according to Modem configuration, either DHCP or PPPoE.
4.     Power cycle the DSL Modem, RV042, and also disconnect your PC from the router as well while it is powered down.
5.     After about 5-10 sec, and in this order, power on your Modem, power on you RV042, and reconnect your PC to one of the LAN ports of your RV042
6.     After about 30-60 secs, test for Internet connectivity.
7.     Do the same for WAN2 using your 2nd ISP connection
At this point, we should now know for certain if both WAN Interfaces will allow Internet connectivity.
If you have problems with these steps, repost with the steps you took and the results.
If things are OK, then we will continue with configuring the router for Load Balance Mode:
1.     Navigate to System Management>Dual-WAN and change your selection from Smart-Link Backup to Load balance
2.     Configure both WAN1 and WAN2 with the configuration that correlates to the Modem connection it will receive.
3.     Connect both Modems to the correct WAN port on the RV042.
4.     Power cycle all devices; Both Modems, RV042, and PC
5.     Navigate to RV042 management page and check to see if there are IP addresses for WAN1 & WAN2 Interfaces.
If you have problems with these steps, repost with the steps you took and the results. Let us know your results.

DHCP issues on wireless

When I connect to my wireless router (D-Link WBR-2310 I believe) using my mac, it gets the default self-assigned address instead of DHCP-assigned address. My PC connects fine wirelessly and wired over ethernet. If the router is reset, it works fine. If I assign manual address to iBook wireless, it works fine (by "works fine" I mean that I can connect to the internet).
Had similar problem with my old Linksys router (Linksys WRT54G) where the following devices had issues connecting to the internet iPod Touch, iBook, PowerBook, and MacBook. This was under unsecured, WEP and WPA settings.It seems that the issue is resurfacing with my current router.
Currently, I am using WPA security (I don't like WEP and neither does my PC). I would rather not switch security settings to unsecured due to the close proximity of my neighbours (yes it's canadian spelling!).
Any suggestions?

I have encountered this same router and issue visiting my future in-laws for the holidays. DHCP with manual address appears to work, but I also still encounter occasional drops. The router is setup for WPA2 security, and support a mix of Mac and Win clients. I haven't put a lot of time into trying to fix it, but here is what I know so far:
1) Sometimes it does just work with DHCP
2) DHCP with manual address works, but will still drop occasionally for brief periods
3) Sometimes, just turning the airport off then on again will resolve the issue and pull an address
4) Just waiting about 30-60 seconds also seems to work -- usually
5) Plugging into the wire works great!
I haven't sat by the router and worked on this, but it seems that occasionally the router just drops the signal, and with it the DHCP assignments. Something about the DHCP implementation is very slow, and it just take a while to get around to assigning an address to my machine. I haven't looked into firmware updates since it's not my box and I don't want to mess it up further and then leave, but that's certainly something to check into.
We also have an 12" PB that cannot even connect to the wireless with the "Error joining wireless network" message. Haven't been able to figure that one out at all.
They may just be getting an Airport or Linksys as a late x-mas gift here... (as my connection drops again while I type this! Airport off, airport on, wait 30 sec, and we're back)
Cheers, and good luck!

Suddenly unable to get new users IP's (Probably DHCP issue)

Hi,
I just took over the support for a small business and while fixing a "roaming profiles" issue I realized that new computers (clients) were not able to get new IP Address or they don't have internet.
I have verified the physical connections and the obvious: (Server has internet, rebooted machine, restarted DHCP Service) but I didn't get proper documentation about the server.
I think it's a Gateway and from the DNS I see it has all Secondary zones set up.
The connected clients don't have any issue anymore.
How can I verify if DHCP is running fine?
Why would the server suddenly stop allowing new IPs?
I have to figure this out by tomorrow so anything you need I'll be following very closely all posts.

I am seing these in the logs:
Nov 14 00:01:43 bumblebee bootpd[190]: DHCP DISCOVER [en0]: 1,0:1c:10:b7:91:2e <207.115.108.186>
Nov 14 00:01:43 bumblebee bootpd[190]: service time 0.001088 seconds
Nov 14 00:01:45 bumblebee bootpd[190]: DHCP DISCOVER [en0]: 1,0:1c:10:b7:91:2e <207.115.108.186>
Nov 14 00:01:45 bumblebee bootpd[190]: service time 0.000325 seconds
Nov 14 00:01:49 bumblebee bootpd[190]: DHCP DISCOVER [en0]: 1,0:1c:10:b7:91:2e <207.115.108.186>
Nov 14 00:01:49 bumblebee bootpd[190]: service time 0.000391 seconds
Nov 14 00:01:57 bumblebee bootpd[190]: DHCP DISCOVER [en0]: 1,0:1c:10:b7:91:2e <207.115.108.186>
Nov 14 00:01:57 bumblebee bootpd[190]: service time 0.000347 seconds
Is this something normal?

Guest Wireless Tunnelling - DHCP Issue

Hi,
I'm attempting to implement Guest Anchor tunnelling between two WLC's but I've run into an odd issue I cannot find a clear answer to.
We have two 5508 WLC's, both Running 7.4.100.0.
The Guest Anchor Controller obviously resides in a DMZ, it's functionality has been proven by connecting an AP directly to it, and connecting the the guest WLAN.
The two controllers have been configured as Mobility Peers, the Mobility Tunnel between them is up (mping and eping both successful, status is up).
The Guest WLAN has been replicated on both controllers, I have set the Mobility Anchor on the WLAN. The Guest Anchor has itself as the mobility anchor and the Internal Controller has the Guest Anchor set.
DHCP is provided by the Guest Anchor's internal DHCP Server. DHCP Proxy is enabled on both Controllers, with the Option 82 format set to AP-MAC. Both Controllers WLAN settings are set to DHCP Server Override, pointed to the Management IP of the Guest Anchor and DHCP Addr. Assignment required.
The problem I'm experiencing is with connecting clients through the Internal WLC. The Client Associates to the Internal WLC and obtains a lease from the Guest Anchor and connects to the network. A few seconds later the client is dessociated from the internal controller. On every subsequent connection attempt, the client does not recieve a response to it's DHCP Requests, and hence ends up with an apipa address.
The Message logs on two controllers return the following errors:
INTERNAL CONTROLLER:
*apfReceiveTask: Jun 27 14:03:25.839: #APF-4-HANDOFF_END_RCVD: apf_mm.c:1626 Handoff end received in wrong role (peer Ip: 0.0.0.0, sender:GUEST_ANCHOR_IP, Role:0) for mobile Client_MAC
GUEST ANCHOR CONTROLLER:
*DHCP Server: Jun 27 14:03:14.466: #DHCP-4-REQIP_NOT_PRESENT: dhcpd.c:559 Received a packet without a requested ip!.
Has anyone else seen similar behaviour? Does anyone have an ideas what might be causing this?
Many Thanks,
Paul

Hi George,
Thanks for the reply.
The Guest WLAN on the Internal Controller is Anchored to the WLC in the DMZ. The Guest Anchor is anchored to itself.
There are only two controllers in the configuration, so breaking off one of the Anchors isn't really an option.
I have tested the Guest Anchor as a Standalone WLC by connecting an AP directly to it, in that configuration DHCP works as expected.

WVC200 DHCP issue (LAN vs Wireless

Hi All,
I have a WRT600N router from Linksys and bought a second WVC200 camera.
While setting up the first camera I had some trouble during set up (now I have the same issue with the second one).
During installation of the first camera while on the ethernet hookup as instructed the DHCP assigned a specifc IP (192.168.1.107). After succesfully finishing the initial set up I detached power and the ethernet and hooked up power alone again to switch to a wireless connection.
For whatever reason the router assigned a different IP (192.168.1.115) or so I thought....
After tinkering for a while I upgraded the Firmware to the last version and the wireless conection suddenly worked (the IP did not change).
Now to the second camera.
Did the same thing but somehow after the upgrade the IP still doesn't remain the same (despite DHCP reservation). Still falls back to the 192.168.1.115.
What I realised after checking the router is that the router doesn't recognize the wlan connection for whatever reason. I do WPA TKIP and it works just fine with the other wireless equipment. I also switched off and on the wireless MAC Filter and added the MAC address of the second camera with the right IP (192.168.1.108) in the DHCP reservation list as a device (same in the wireless filter list). I also checked the MAC address at least 10 times....
What else can I do to trick the router in finding the camera and assigning the right IP address or is the wireless connection just broken?
Thx for any help.
Malte
Message Edited by Malte on 08-18-2008 03:14 PM

I have the exact same problem! I have a WVC200 since a couple of years. It have served well but for a while ago it stopped to work properly. I didn't do anything about it right away but today I thought I should set it right.
I did a firmware upgrade, reseted the camera and started all over with the settings. At first I had a TP-cable in it. My router is a Zonet ZSR0140CP that also acts DHCPserver. I have told the DHCP that the MAC-adress of the camera should have a specific IP-adress. In the camera I have set that it should get a IP-adress from DHCP. I have a D-Link DWL-900AP+ that acts wireless AP. It is WEP Encryption with 64 bit HEX. And it doesn't act as a DHCPserver, it's just an AP
Everything went fine until I broke the electricity to the camera unplugged the TP-cable and plugged the elecricity in again.
For a long while it just serched an IP-adress and when it got one it was 192.168.1.115! Thats not much right in that ip adress... Wherever did it got that from??
Please don't tell me to reset everything. I have already done that. And I still have the same problem. I dont think it is the router/switch/AP who is the problem here.
//Camilla

Linksys WAP200 DHCP issues (acces point)

Hello,
during installation of Linksys WAP200 we noticed the following two issues:
a) The main problem consist of that AP (wifi access point) do not process DHCP request. Any DHCP request is not received when we had to used only one SSID and AP is in VLAN1 (the same problem is registered if are allowed VLANs to AP). Additionaly were created additional SSID - all is working properly.
b) The second and more important problem if is required to make restart of AP or due to outage of electricity, again is not allowed to receive IP address from AP. When is second SSID deleted and again reconfigured is whole communication and functionality restored.
Technical specification of AP:
Model: Linksys WAP 200
Firmware: 1.0.22-ETSI
SN: MO200J500700, MO200J300921, MO200J300922, MO200J300923,MO200J300924, MO200J300925, MO200J300926, MO200J300927, MO200J300928
These enclosed network devices are used in LAN topology:
RV082-EU, Linksys 10/100 8-Port VPN Router SRW224G4P-EU,
Linksys SRW224G4P 24-port 10/100+4Port Gigabit Switch, PoE
SRW248G4P-EU, Linksys SRW248G4P 48-Port 10/100+4-Port Gigabit Switch, Po
Do you have any idea where should by problem or we have to wait on new firmware ? :(
Thanks for help and suggest.
Pavol

Hi Pavol,
As with the SRW series switches, the default VLAN (vlan1) is untagged.
VLAN2, VLAN3 and VLAN4 will obviouslybe tagged, so the WAP200 supports trunked VLANs.
I have been using WAP200's for both bridging in some applications and just in AP mode for other applications for a number of years, in conjunction with my SRW2008P switch.
But I have seen issues, where after a software upgrade. I had to reset the AP back to factory defaults and create the configuration again.
Firstly reset the WAP200 back to factory defaults and it still fails, I would suggest you call the wonderful folks at the Small Business Support Center (SBSC) in your country via the following URL;
http://www.cisco.com/en/US/partner/support/tsd_cisco_small_business_support_center_contacts.html
I must admit I am using the US software 1.0.22 and not the European software :D but it may just be a configuration issue you may have.
I did see software version firmware_wap200v1.0.22.2-ETSI for European countries, i am not sure if that is the software you are using.
regards David

CAS 4.0.0 Sever DHCP Issue

I am having an issue with DHCP on our CAS 4.0.0 server. I need to expire a DHCP lease or remove it because the device is going to use a reserved IP address. The challenge I am having is that this device is an Apple IPad and apparently these devices do not play well with DHCP servers. The customer is insisting that the only option they have is to renew a DHCP lease not release and then renew. All other devices we are setting up with reserved IP are working as expected its just the Apple IPad giving us trouble. The question is "Is there a way to manually remove or expire a DHCP lease on the CAS server?"

I second @Ann154 observation. My phone has been rock solid since 4.0.4. On 4.0.2 I was so disappointed with the freezing and restarts as well as the 4G disconnect issue, that I was really thinking if I had made the right decision by going for the Galaxy Nexus.
Now Verizon really needs to work out it's update validation process to reduce the time between when Google releases an update to when Verizon approves and "releases" it. 4 months is simply unacceptable.

DNS / DHCP Issues in Server 2008R2 Domain

Hi folks,
We’ve been having an ongoing issue for a while now in that some PCs and laptops (Win 7) in our company can’t be contacted by hostname i.e. if we try and RDP from one Windows 7 PC to another the RDP session fails as if the PC isn’t turned on, but it
is indeed turned on and connected to the network.
Even if we ping the host name of a particular computer that is on it fails to reply but if I go into DHCP I can find the hostname bit it has a different IP address assigned to it other than what is listed in DNS for that host name.
So for some reason when some computers get switched on and be allocated a new dynamic IP address through DHCP the corresponding record in DNS doesn’t seem to get updated meaning we need to go into DNS and manually amend the Host A record with the new
IP address that it has been given so we can RDP onto that computer using the hostname.
At present aging and scavenging isn’t enabled in our environment as we are afraid to in case it removes live DNS entries that just haven’t been turned on in a wee while. Does aging and scavenging just ignore static DNS entires and does aging and
scavenging work in DHCP as well?
One other thing I noticed is that if I delete an incorrect DNS Host A record and create it manually and assign the hostname and the correct IP address it says static rather than having a timestamp on it. When I create the new record I always click on our
domain in the Forward Lookup Zone and on creation I always select Create the associated pointer (PTR) record so not sure why the manual record doesn’t get a time stand.
So any help/advice or suggestions would be greatly appreciated.
Thanks,
Bonemister

Hi David,
Thanks for your reply and for clarifying those things for me. Unfortunately in my workplace when I add a manual DNS Host A record it does become a static entry and doesn't have the '0'
you mention, do you have any idea why that would be as I'm worried about it affecting things if I were to enable aging and scavenging.
Is it possible to just enable aging and have it remove entries before a time of my choosing or does scavenging need to be enabled also?
I still can't understand why the relationship between DHCP and DNS isn't working correctly. Sure if DNS has an A record for a computer and the IP address changes via DHCP there is bound to be
a way to setup DNS to be able to update the records it holds - do you know if my reading of this is correct.
By the way, I can confirm that my adapters TCP/IP DNS settings are the same on of the PCs that had the DNS fault as in your screenshot the only different is we have the tick in Append parent suffixes... - would that make a difference.
Thanks also for that other link, it seems very interesting and I'll have a good read through it carefully before doing anything!!
Thanks again for you reply and I look forward to seeing any responses.
Regards,
Bonemister

RV042 second DHCP issue

Similar Messages

Maybe you are looking for