Switch / DHCP issue

Hey guys - just would like to know what is happening here:
Brand new Linksys switch(SLM2048)- default settings. Connected to DHCP server via other Cisco switches.
Plug in 6 laptops directly into the switch - "unable to find DHCP server".
At the same time
Plug in 6x other laptops into a Netgear 8port gigabit ethernet switch and then into the Linksys switch - "DHCP server found".
Other points to note: There is another brand new Linksys switch(SLM2048) connected to the LAN. (And both are at default settings). After the I changed the default ip of one of the switches to DHCP it all worked fine when plugged directly into the first switch.
Yes I have A solution - But not THE solution??
Why is it by adding another switch to the link it works. Why does adding that switch negate the need to change the default IP on the second Linksys switch on the network.
Any ideas would be appreciated.. (hope I have explained this OK and not confused anyone)
Cheers
James

odd problem that you got there. i just setup the same switch a week ago but i did not encounter this. try to flash the firmware and reset the device and see if that helps.

Similar Messages

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-----

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

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).

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

2100 wireless LAN controller intermittant DHCP issue does not respond to clients

Hi everyone,
I have been struggling with a difficult problem for some time now:
The cisco 2100 wlan controller I have is configured with a dhcp scope in the same ip address range as its WLAN. The configuration works and on a good day I have up to 200 clients connecting with out issue. In the web interface they display as associated and authenticated
On a bad day I find I will begin seeing about 50-80% of all new devices that attempt to join the WLAN show up as associated but not authenticated. These clients end up self assigning themselves a 169.254.0.0/16 (APIPA) address
When my controller / WLAN enters into this state: if clients leave the WLAN they typically fail to get back on and successfully authenticate. By the end of a day around 80-90% of all devices are essentially without Internet access due to this issue.
Rebooting the controller and or APs typically makes no difference or makes things worse – although sometimes it appears to resolve the issue. The same holds for disabling the entire wlan for about 10 minutes and then re enabling it.
Im using 1130 cisco aironet APs with the controller. I have checked extensively for interference and congestion – I think I have congestion – some APs typically host 40 to 90 devices. However as mentioned on a good day the wlan will host 200 devices all day without any issue and some APs will host 50 to 70 devices without major issue.
I can provide more specifics if anyone should need – eg firmware, IP addresses, exact model numbers etc.
Please let me know if anyone has seen something like this before ?
I believe the 2100 is rated to handle up to 350 devices and its recommended not to load a 1130 AP with more than 25 devices ??
Regards
Matthew

Hi Amijad, Hi George:
Thank you both for your time in considering my situation.
I will think about implementing an independant DHCP server; im really wondering if the equipment is just overloaded
- What software versoin the WLC uses?
Product Version.................................. 6.0.199.4
RTOS Version..................................... 6.0.199.4
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... 6.0.199.4
PID: AIR-WLC2106-K9, VID: V05
- What ports of the WLC are connected to the neighbor swtich? one or more?
2 ports connect to the neighbor switch on separate vlans
- port 1 is vlan 0 and hosts the management and ap-management IPs for the wlan controller
- port 2 is vlan 1 and hosts the wlan
- the controller has one dhcp scope defined on port 2 for the WLAN
- What is the security of your WLAN?
WPA+WPA2
AES
PSK
- Do you have "DHCP required" enabled on the WLAN?
yes DHCP required is enabled in the WLAN
please let me know if you have any additional advice.
regards
Matthew

AP 1140 DHCP Issue

Hi All
I am installing a 3750 switch with integrated controller and 12 x Cisco 1140 AP's. I have configured the 3750 WLC with a management and AP Manager IP address along with 3 WLAN profiles and security settings. I am confident that these are correct, and in any case are, I believe, not related to the problem I have.
None of my AP's would connect to the controller and when I checked the DHCP (Windows Server) server they had not been issued with an IP address. I logged into an AP via the console and saw the following message "Not sending discovery request AP does not have an ip" If I plug a laptop into the port the AP connects to I pick up an IP address without a problem from the DHCP server. This is not a faulty AP issue as none of the AP's are getting an IP address.
The only other relevant fact is that the Windows DHCP server is on a different subnet (VLAN)though I have enabled DHCP forwarding which obviously works as my laptop gets an IP address.
I have raised this with Cisco TAC and their first response has been to get me to configure Option 43. I will try this but am not expecting it to work as the only thing this will do is to return the IP address of the controller. My AP's however are not getting any response.
Any suggestions as to how to resolve would be gratefully received.

Wouldn't option 43 only work when the AP's are actually getting an IP address?
Could you post an extended capture of the AP output during the boot and lack of join?
To make sure you connectivity is what it should be, you could always try manually assigning an IP address to the AP, and also manually tell the AP the controller IP address. If that works, then you likely have a problem with your DHCP server or scope definition. Do you have any MAC assignments/reservations in the DHCP scope? Have you tried reserving the AP IP addresses by MAC address within the relevant DHCP scope?

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!

Wireless Guest Users DHCP issue

Dear all
We have 2 wism as well as Anchor controller
Guest users are getting ip address from anchor controller.
We had created DHCP scope on anchor controller itself.
We had opened particular ports to communicate between guest controller and inside controller for EOIP tunneling to take place.
Issue is that some times user is getting IP address in the range of AP management vlan.
Do we require to open ports for bootpc and bootps as well or do we need to create dhcp scope in the switch.
If any one has faced the above issue pls reply me at the earliest.
Regards
-Danish

If the anchor goes down, or mobility fails, the user should never egress from the Foreign WLC (in my opinion). However, if you are saying that the user gets an IP from the MGMT Interface of the Foreign WLC (not the Anchor), then it is doing exactly what it shouldn't.
What version of code is this?
I've seen a lot of deployments implement a "dummy interface" on the Foreign WLC. So a fake vlan/subnet is created on the WLC and mapped as the default interface for the Foreign's Guest WLAN. In the event anchoring does fail and the client sticks to the foreign WLC this dummy interface would actually prevent the user from having network access.
Are you seeing this often?

Vwlc 7.3.101.0 DHCP issue ?

Hello all,
a wireless client can't get an IP address via DHCP.
The controler is configured as "DHCP bridging mode", the DHCP server is a 3750 on the same L2 segment.
The security part is done by ISE 1.1.3, the client get authenticated successfully and debug on the vwlc says :
(Cisco Controller) >*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP processing DHCP REQUEST (3)
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP   xid: 0x7f6910ce (2137592014), secs: 0, flags: 0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP   chaddr: 00:26:4a:fd:ed:a4
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP   ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP   requested ip: 192.168.10.4
*DHCP Socket Task: Apr 22 17:50:13.445: 00:26:4a:fd:ed:a4 DHCP successfully bridged packet to DS
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP received op BOOTREPLY (2) (len 308,vlan 0, port 1, encap 0xec00)
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP processing DHCP ACK (5)
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP   xid: 0x7f6910ce (2137592014), secs: 0, flags: 80
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP   chaddr: 00:26:4a:fd:ed:a4
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP   ciaddr: 0.0.0.0, yiaddr: 192.168.10.4
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP   siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP   server id: 192.168.10.1 rcvd server id: 192.168.10.1
*DHCP Socket Task: Apr 22 17:50:13.447: 00:26:4a:fd:ed:a4 DHCP successfully bridged packet to STA
however, the wireless client never get the IP address.
See attached .jpg, the IP address seems to be attached to the wireless client.....
Is anyone could help me please ?
Regards.
TM

Ok DHCP Snooping was the issue....
The DHCP message response seems to enter back the switch (from the vwlc to the AP ) on the same port it came from.
(the Sw acts as a DHCP server)
Now I have an IP address assign by DHCP but no connectivity though !!!

802.1X dyanmic VLAN assignment DHCP issue (Vista client)

I am labbing dynamic VLAN assignment and have run into a small problem. The switchport is succesfully changing to the new VLAN, but my test PC seems to get an IP address in the native data VLAN before being moved to the new dynamic assigned VLAN. So when the switch changes the VLAN the PC keeps its old IP address and nothing talks any more.
Is this a Vista issue? I thought all of these problems were just issues in XP? Do I need to tweak any interface dot1x timers?
(Cat3750 with 12.2.55 / ACS5.1. Everything else is running fine by the way.)

if i do a show run on the switchport the config hasnt changed, but i dont expect it to, as its not a permanent config change that you would want to be saved by a different admin user saving the config. You can see the debug report it is changing the VLAN:
Apr 19 09:22:56.263: %AUTHMGR-5-START: Starting 'dot1x' for client (0014.c209.896f) on Interface Gi1/0/19 AuditSessionID C0A8FE250000000900291476
Apr 19 09:22:58.604: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
Apr 19 09:22:59.560: %DOT1X-5-SUCCESS: Authentication successful for client (0014.c209.896f) on Interface Gi1/0/19 AuditSessionID
Apr 19 09:22:59.568: %AUTHMGR-5-VLANASSIGN: VLAN 12 assigned to Interface Gi1/0/19 AuditSessionID C0A8FE250000000900291476
Apr 19 09:22:59.585: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan12, changed state to up
Apr 19 09:23:00.307: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
Apr 19 09:23:00.315: %AUTHMGR-5-SUCCESS: Authorization succeeded for client (0014.c209.896f) on Interface Gi1/0/19 AuditSessionID C0A8FE250000000900291476
as well as checking with the show int switchport command and it is in v12 which is the dynamically assigned vlan
DHCP server is the cat3750 for all local VLANs

WAP551 DHCP issue

Hi,
I have trouble with new WAP551 accesspoints.
For supplying a new building on our campus we decided to use WAP551 accesspoints. Another building is working with WAP541 models an all is working fine.
The accesspoints are working in cluster mode with 16 nodes. They are supplying multiple SSIDs in multiple VLANs with different DHCP Servers in some VLANs.
When I start switching between the SSIDs I will not get a DHCP address. When I am going to look at the switchport, where the AP is connected, I cant see any DHCP Packet passing by. It seems that the AP stops passing DHCP. Sometimes it takes a few minutes, then suddendly a DHCP request passes by and my client gets an address.
To isolate the issue, I took one of the new WAP551 to the old building and installed it there as single AP, but it is the same there (so it has nothing to to with my infrastructure of the campus) and the WAP541 are still working fine - I can switch between the SSIDs a couple of times and always get an DHCP address.
I installed the latest firmware of 2015-01-19 - 1.1.2.3 - but no change - still the same.
I have no idea whats going on, has anybody here new ideas?

My name Eric Moyers. I am an Engineer in the Small Business Support Center.
I am sorry to hear that you are experiencing this issue.
This seems to be a very involved network. In order to more quickly troubleshoot and resolve your issue, please call our support center and open a case so that one of our engineers can work directly with you.
http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
Eric Moyers
.:|:.:|:. CISCO | Cisco Presales Technical Support | Wireless Subject Matter Expert
Please rate helpful Posts and Let others know when your Question has been answered.

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

Airport Extreme - possible DHCP issues on UTP ports?

I have a recent (late 2012) iMac which has been consistently connected to my Airport Extreme via UTP with no issues until recently. The Airport Extreme is connected to my single port Motorola 5101 Bigpond Cable Modem.
Connected to the Airport Extreme via UTP are the iMac and a Lacie 4TB NAS media server. There are generally multiple devices connected wirelessly (iPhone, iPad, PS3, XBox) again with no issue.
I have a PC connected to an Airport Express at the other end of the house (PC has no wireless card) and the Express and Extreme are bridged with a common SSID.
Saturday night the "house network" occasionally lost wireless (iPhone switching to 3G) but after resetting the Extreme and the iPhone this seemed to settle down and has been working fine since then (4 days prior to this post).
Later on the Saturday night my iMac lost internet connectivity and resetting the Airport Extreme and resetting the Motorola 5101 did not help. Eventually rebooted the iMac and the Extreme and the 5101 and eventually (after a few minutes) internet connectivity was restored. (Error was "no IP address" and Airport Utility could not see either the Extreme or Express). Connectivity was restored by first turning on WiFi on iMac which immediately got an iP (10.x.x.x) allocated and then after a few minutes the UTP link also came up and remained up when WiFi was turned off.
The iMac has since "lost internet connection" around 3 times in total and a similar process to the above has not always restored connectivity – i.e. doing all the above worked some of the times and did not work others.
When this problem is happening on the iMac UTP connection there are no issues with wireless devices getting an IP allocated.
I am now running the iMac on WiFi with the UTP cable removed. Today I will try a new UTP cable between the iMac and the Airport Extreme to see if there is perhaps some intermittent cable issue.
The Airport Extreme and Airport Express (both a few years old) are running 7.6.4 firmware. I had recently setup timed access for a few wireless devices and also trialled the "guest wireless account" but these were set up around 1 week prior to the recent issues occurring. I have now removed both of these so that the Apple network devices are back to the settings they had which worked fine for years (albeit with different firmware versions over this time).
My diagnosis is that it seems that there is a problem with IPs being allocated by DHCP to devices connected to UTP ports but not over wireless. The only thing that seems to contradict this is that the Lacie NAS drive which is UTP connected (to UTP port 3) seems to still work and be accessible without issue.
So am also wondering if there is some intermittent iMac issue with the UTP port or with the cable. Will change the cable today as mentioned above to confirm or otherwise.
Any advice on further diagnostic processes and/or thoughts on Airport Extreme issues (hardware or firmware) etc would be appreciated. A search of the forums did not show anything similar but my search was not super-extensive.
Thank you for any help anyone can provide.
Andrew

In the end after LOTS of troubleshooting and testing - and WAY too much frustration Apple - this issue has proved to simply be what I assume is a bug in the Automatic network location management under Mavericks and I had this issue to a lesser degree with 10.8.5.
I have now setup a "Home" new network location and my connection has been 150% stable ever since.
So nice to not need to reboot my Mac 7 times a day or more after several weeks of significant frustration.

Switch / DHCP issue

Similar Messages

Maybe you are looking for