RV180W firmware 1.0.5.4 DHCP lease problem

Yesterday I upgraded my RV180W to firmware 1.0.5.4. Today the only machine that we have with XP can't get a DHCP lease (we have some 20 machines that can that all have W7 o W8.1). Also none of the iPhones nor Androids that connect via wifi get leases either and thus have fallen back to 3G.

Hello,
First of all I want to say that I'm sorry you are experiencing an issue with the device after the firmware upgrade.
Now, we have tested this device with the new firmware on our lab and we are not experiencing the same issue, which leads me to believe this may be an issue with your particular configuration or network topology.
We would love to have the opportunity to troubleshoot this issue on the Small Business Support Center. If you are still under support with the device, give us a call and we will be happy to assist you.
If you are not able to or are out of support, then please provide as much information as possible in regards to your current configuration as well as network topology, maybe a detailed network diagram could be helpful to so that we can have a better idea of that the issue could be.
I hope this was helpful.

Similar Messages

Cisco 867VAE drops connection on DHCP lease timeout

Hey!
We have a very annoying problem on our hands. I'm no IOS expert, but I make do.
We've got a Telia DSL connection that has a 20 minute DHCP lease timer. Every 20 minutes when it shakes hand again, the connection drops for about 5 seconds. This because the Cisco thinks that administratively shutting down the interface is a good idea....
How do I stop this behavior? I've tried manually setting <ip dhcp client lease 1 0 0> (for 1 day lease) but it completely disregards that.
Best would obviously be to stop it shutting down the interface every time, but worst case scenario I'll take a solution with a longer DHCP lease since the address rarely changes.
<snip from log>
*Aug 1 01:44:43.514 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.xxx.xx, mask 255.255.255.0, hostname elsa
*Aug 1 02:04:48.498 PCTime: %DHCP-5-RESTART: Interface ATM0.1 is being restarted by DHCP
*Aug 1 02:04:56.106 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.xxx.xx, mask 255.255.255.0, hostname elsa
*Aug 1 02:25:01.050 PCTime: %DHCP-5-RESTART: Interface ATM0.1 is being restarted by DHCP
</snip>
It's running firmware c860vae-ipbasek9-mz.153-2
I'm attaching the current running-config as well.
Thank you in advance!
Best Regards
Daniel

I'm sorry for not reporting in. The case is closed at Cisco and they simply couldn't do anything. The router does, according to the debug logs, send dhcp renew requests, but the ISP doesn't reply to them. If they get lost on the way, or if there's an incompatability with the ISP, I dunno. I heavily doubt it, since Telia (Swedish ISP) used Cisco gear for pretty much everything.
Also, Telia will not reply to anything like this, since they don't support equipment they don't supply.
So I'm completely at a loss, and will remain there until I stumble across something.
I've received an 887M router though, which I'm gonna test. But I'm currently stuck with the fact that it's not supported anymore, and therefor I can't seem to download new IOS software (it uses a very old one).
This is the last reply I got before they closed my case:
*Aug 27 14:56:15.751 PCTime: DHCP Ack Message
*Aug 27 14:56:15.751 PCTime: DHCP: Lease Seconds: 1200
*Aug 27 14:56:15.751 PCTime: DHCP: Server ID Option: 213.66.241.86
*Aug 27 14:56:18.751 PCTime: DHCPD: IP address change on interface ATM0.1
*Aug 27 14:56:18.751 PCTime: DHCPD: IP address change on interface ATM0.1
*Aug 27 14:56:18.751 PCTime: DHCP: Releasing ipl options:
*Aug 27 14:56:18.751 PCTime: DHCP: Applying DHCP options:
*Aug 27 14:56:18.751 PCTime:   Setting default_gateway to 81.230.121.65
*Aug 27 14:56:18.751 PCTime:   Adding default route 81.230.121.65
*Aug 27 14:56:19.751 PCTime:   Adding route to DHCP server 213.66.241.86 via ATM0.1 81.230.121.65
*Aug 27 14:56:19.751 PCTime:   Adding DNS server address 195.67.199.39
*Aug 27 14:56:19.751 PCTime:   Adding DNS server address 195.67.199.40
*Aug 27 14:56:19.751 PCTime: DHCP: Sending notification of ASSIGNMENT:
*Aug 27 14:56:19.751 PCTime:   Address 81.230.121.83 mask 255.255.255.192
*Aug 27 14:56:19.751 PCTime: DHCP Client Pooling: ***Allocated IP address: 81.230.121.83
*Aug 27 14:56:19.803 PCTime: Allocated IP address = 81.230.121.83 255.255.255.192
*Aug 27 14:56:19.803 PCTime: %DHCP-6-ADDRESS_ASSIGN: Interface ATM0.1 assigned DHCP address 81.230.121.83, mask 255.255.255.192, hostname elsa
*Aug 27 14:56:25.751 PCTime: DHCP: Client socket is closed
*Aug 27 15:06:18.759 PCTime: DHCP: Client socket is opened
*Aug 27 15:06:19.759 PCTime: DHCP: QScan: Bound..T1 fired..Renewing
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest attempt # 1 for entry:
*Aug 27 15:06:19.759 PCTime: Temp IP addr: 81.230.121.83 for peer on Interface: ATM0.1
*Aug 27 15:06:19.759 PCTime: Temp sub net mask: 255.255.255.192
*Aug 27 15:06:19.759 PCTime:    DHCP Lease server: 213.66.241.86, state: 7 Renewing
*Aug 27 15:06:19.759 PCTime:    DHCP transaction id: 914
*Aug 27 15:06:19.759 PCTime:    Lease: 1200 secs, Renewal: 600 secs, Rebind: 1050 secs
*Aug 27 15:06:19.759 PCTime: Temp default-gateway addr: 81.230.121.65
*Aug 27 15:06:19.759 PCTime:    Next timer fires after: 00:03:46
*Aug 27 15:06:19.759 PCTime:    Retry count: 1   Client-ID: cisco-d48c.b524.7b17-AT0.1
*Aug 27 15:06:19.759 PCTime:    Client-ID hex dump: 636973636F2D643438632E623532342E
*Aug 27 15:06:19.759 PCTime:                        376231372D4154302E31
*Aug 27 15:06:19.759 PCTime:    Hostname: elsa
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest - ciaddr: 81.230.121.83
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:06:19.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:06:30.759 PCTime: DHCP: Client socket is closed
*Aug 27 15:10:04.759 PCTime: DHCP: Client socket is opened
*Aug 27 15:10:05.759 PCTime: DHCP: QScan: Renewal..Retrying
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest attempt # 2 for entry:
*Aug 27 15:10:05.759 PCTime: Temp IP addr: 81.230.121.83 for peer on Interface: ATM0.1
*Aug 27 15:10:05.759 PCTime: Temp sub net mask: 255.255.255.192
*Aug 27 15:10:05.759 PCTime:    DHCP Lease server: 213.66.241.86, state: 7 Renewing
*Aug 27 15:10:05.759 PCTime:    DHCP transaction id: 914
*Aug 27 15:10:05.759 PCTime:    Lease: 1200 secs, Renewal: 600 secs, Rebind: 1050 secs
*Aug 27 15:10:05.759 PCTime: Temp default-gateway addr: 81.230.121.65
*Aug 27 15:10:05.759 PCTime:    Next timer fires after: 00:01:53
*Aug 27 15:10:05.759 PCTime:    Retry count: 2   Client-ID: cisco-d48c.b524.7b17-AT0.1
*Aug 27 15:10:05.759 PCTime:    Client-ID hex dump: 636973636F2D643438632E623532342E
*Aug 27 15:10:05.759 PCTime:                        376231372D4154302E31
*Aug 27 15:10:05.759 PCTime:    Hostname: elsa
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest - ciaddr: 81.230.121.83
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:10:05.759 PCTime: DHCP: SRequest: 293 bytes
*Aug 27 15:10:16.759 PCTime: DHCP: Client socket is closed
*Aug 27 15:11:57.759 PCTime: DHCP: Client socket is opened
*Aug 27 15:11:58.759 PCTime: DHCP: QScan: Renewal..Retrying
*Aug 27 15:11:58.759 PCTime: DHCP: SRequest attempt # 3 for entry:
As pointed to you in my previous mails renews/packets are being sent and as router is not getting back any reply, lease is timing out and that’s the reason why the interface is getting flapped. You need to find with ISP why the renews and rebind packets are not responded to by Providers DHCP server.
Hope this clarifies your query.
Thanks and regards,
Lijesh

[Q]: Static DHCP Lease with the WRT54GL...

Hello,
I have replaced my old D-LINK router with a WRT54GL wireless router.
On the old router I could configure static DHCP entries, providing the same IP address to specific MAC addresses (from my different devices at home), and still continue to receive all other settings via DHCP (Like DNS servers that my ISP changes from time to time).
Using static IP addresses is not an option due that the ISP I'm connected changes the DNS settings frequently and my computers can't connect to the internet. Setting the WRT54GL router as DNS server on my computers is also not practical.
On the WRT54GL I could not find how to create static (or permanent) DHCP leases. Is this possible?.. is this in the wish list for future releases of the firmware?
Thanks in advance.

Thanks for the quick response.
I was surprised that this (and maybe other) Linksys routers does not provide this simple feature.
All DHCP servers I know provide this feature and most of the unmanaged routers that provide DHCP services have this feature.
--- Ricky.

Cisco Phone 7937 DHCP lease issue

Hi ,
We have configured DHCP lease id 8 day. But Cisco Conferance Phone 7937 is taking DHCP lease for only 1 day. Can any one know the reason

Firmware 1.4(5) is available for the 7937. The release notes don't mention your problem, but there are other DHCP fixes in the firmware.
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7937g/firmware/english/1_4_5/release_notes/7937_rn_145.pdf
I haven't seen anything like this with our 7937s. Have you Wiresharked the phone, to be 100% sure what the phone is getting via DHCP is what you think it should be getting?
GTG
Please rate all helpful posts.

WRV210 DHCP Lease Renewal

I have been having intermitent connectivity issues with all devices on my network, and I have noticed that the DHCP leases are not renewing on the router. The only solution I have right now is to reboot the router every day. Has anyone had this issue, or have any ideas about fixes other than assigning static IP addresses for everything?
Thanks,
Mike

When you noticed that the DHCP lease has not renewed, if you go to a client machine and do a release/renew will it get an IP address then? Check and see if you are on the latest firmware version for your router. If you are having to reboot the router just to have DHCP broadcast acknowledged then you may want to go ahead and give your SBSC a call and open up a case with them.
You can find your SBSC here.

WRT54G Router DHCP leases

I would like to see the router DHCP leases on a screen in the firmware so you can see how many are being used and which ones. Who do I need to contact to pass along this suggestion?

I have the WRT54G V6.0 Router with firmware 1.01. I get the idiot of the week award for reading the manual and finding it on a page when logged in to the router. I just didn't look far enough in the software to find it before I posted. Sorry! All idiot bashing posts welcome..starting with the big DUH...........

WRT320N static DHCP leases

hi,
i have a wrt320n. it runs fine, but i'm in need of static DHCP leases.
the reason is simple: if one uses static port forwards for applications that doesn't support upnp, and the client gets a different ip than what's specified for the port forwards, it all gets messed up.
i couldn't find any reference for this feature neither in the manual nor in the router web interface, so i guess it's not possible ATM.
could you please add support for this (quite basic) feature?
thanks in advance.
Solved!
Go to Solution.

Well i think the feature which you are trying to look under the linksys router its not possible. I think you need to wait until linksys release the new firmware along with the DHCP Leases.

WRT150N DHCP Lease Renewal Lockup

I have a WRT150N that uses both wireless and wired clients. It is connected to a Roadrunner cable modem that renews DHCP ever 24 hours (approximately at 0545). If one of the clients is in use at that time the WRT150N locks up and will not respond to any of the clients. I have to unplug the WRT150N to restart it. I had a WRT54G previously and this never happened. I've uploaded the newest firmware to no avail and I can't afford having to do a hard restart 3 or 4 times a week. Is there a solution or would it be better to deep 6 this router and go back to what works.

When you noticed that the DHCP lease has not renewed, if you go to a client machine and do a release/renew will it get an IP address then? Check and see if you are on the latest firmware version for your router. If you are having to reboot the router just to have DHCP broadcast acknowledged then you may want to go ahead and give your SBSC a call and open up a case with them.
You can find your SBSC here.

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

TS1388 After one or two websites the search "freezes". To rectify this I need to go into "Network" and press "Renew DHCP Lease" on my imac 10.6.8

After one or two websites the search "freezes". To rectify this I need to go into "Network" and press "Renew DHCP Lease" on my imac 10.6.8TS1317 - Mac OS X: Troubleshooting a cable modem, DSL, or LAN Internet connectionAny help?

Check your computers time and date are correct, and updating to your location via Apple's servers.
WiFi, Internet problems, possible solutions

[SOLVED] Hostname not showing in DHCP lease list

This is a brand new installation using the new systemd base.
Installed openbox as window manager and Network Manager.
What did I miss that the hostname of this computer (opus) is not showing up in the DHCP Leases list?
When I connect to the network using Network Manger(DHCP), hostname is not sent to the DHCP server (DNSmasq). It shows up as a "*":
DHCP leases
Hostname    IP-address    MAC-address    Lease expires
*    192.168.10.100    XX:XX:XX:XX:XX:XX Nov 28th, 19:34
*    192.168.10.59    XX:XX:XX:XX:XX:XX Nov 28th, 19:23
alarmpi    192.168.10.69    XX:XX:XX:XX:XX:XX Nov 28th, 16:56
RM696    192.168.10.97    XX:XX:XX:XX:XX:XX Nov 28th, 18:23
(I blanked out the MAC-addresses.)
The first entry is connecting through wireless. The second is wired.
At the command line:
hostname
opus
hostname -f
localhost.localdomain
/etc/hosts:
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost opus
::1 localhost.localdomain localhost opus
# End of file
What file do I need to change and how?
Updated:
1) I created a /etc/dhclient.conf file and added:
send host-name "opus";
request subnet-mask, broadcast-address, time-offset, routers,
domain-search, domain-name, domain-name-servers, host-name;
and rebooted.
This had no effect.
2) Just for kicks, I uninstalled Network Manager and installed Wicd.
This DID send the hostname and it displayed on the DHCP Leases List. But it also had the effect of turning off the WiFi radio.
I did try to turn it back on: Went to the BIOS, made sure it was on (it was). Read some posts about power savings and what to do (tried them, didn't work).
So I uninstalled Wicd, re-installed Network Manager and I am back to where I was.
Last edited by dastagg (2012-11-29 11:15:11)

Sorry, forgot to add this:
https://bbs.archlinux.org/viewtopic.php?id=152376
Follow the instructions on the bottom.

My internet keeps going down and when I try to renew the DHCP lease it stops working altogether

Every couple of weeks my internet would go down, I would be surfing the web and suddenly my connection would fail. I would try renewing my DHCP lease and every time I did I would get an IPv4 address of 192.168.0.100. Originally, restarting the router would fix the problem but the past couple of times they needed a technician from the provider to fix it. Even using the Ethernet cable doesn't work either.
is there a reason why this keeps happening and how do I stop it from happening again? Is there anything I can try to fix it on my end?
my computer is a five year old MacBook, running OS X 10.9.4

Having the same problem. Watched 25 minutes of a rental and it stopped with the message"unable to load video"
Using current version IPad mini.
Ios7 is HUGH PIECE OF CRAP!!!!

RV180W Firmware Update

I saw a post with a response stating that a new RV180W firmware would be released by end of 2013.
It was part of the RV220W posts. I can't find that post but we (community) really need a update that fixes these issues like 100% CPU, selective logging ect....
It would also be nice if features from older routers could be added.
For example, I'm missing some of the logging features from my old WVRS4400N 1.1.13. Like having a firewall rule that you can check to have it logged.!
For example:
Oct 6 05:56:29 - [Access Log Log i7] Allow TCP Packet - 10.0.1.220:52450 --> 208.68.240.20:80
OR
Oct 5 06:50:27 - [Access Log 128higher] Deny TCP Packet - 192.168.2.130:62696 --> 17.149.36.208:5223
Steve

Steven,
I also remeber seeing this post.
I think the post was in relation to the Device Emulators which have been running 1.0.3.14 since before Christmas.
The Cisco response was the the new release was expected "by the end of the month" (December 2013). Now, another month on, there is still no sign of it (although there have been updates for other routers in the RV range).
As I've discussed on here before the RV180 is a great piece of hardware- however the support updates and bug fixes have been terribly slow. It certainly prevents this being the world class product you might expect from Cisco.
Cisco,
Any updates on the next release and what it might address in terms of bug fixes and new features?
Kind Regards,
Andy.

How do I revoke a DHCP lease in the 10.8.4 server app?

Hello Everyone,
I have some devices (security cameras) that have successfully requested a DHCP lease. Since then I went ahead and manually created a static reservation for them with a MAC hardware address in the DHCP. For whatever reason they are not switching over to the reserved address. The leases were originally for 1 day. It has been 5 days now. After the first day I switched my lease time to 1 hour. I have done everything short of leaving the devices off for 24 hours.
In Lion server, I could revoke the lease via the gui. No such luck now. My call to Applecare resulted in a "there is no way in 10.8.4 to do this". They said it would switch to the new reserved address after the initial lease period timed out, so I'm hoping the representative was wrong twice. They mentioned a complete lease wipe, but couldn't say if this would cause me to lose my list of reserved static addresses, which isn't an option.
It seems crazy that such a basic feature wouldn't make it into this release of the DHCP service. Any help would be greatly appreciated!

Are there any DHCP queries from the cameras? Check the DHCP server log via Console.app or Server.app (or Terminal.app) for details. (I don't know the 10.8 path to the DHCP logs offhand.)
According to a FAQ over at the Vivotek site, the following is the setup sequence for various recent cameras; the boxes start up in the "I don't have an IP address" self-allocated address block oddly enough, and apparently don't ask for a DHCP address? (You may well be aware of all of this, but this is the block that DHCP clients use when they first communicate with DHCP servers.)
If you are using our new product such as IP7138 / IP7139 / FD7131 / VS7100… etc, no matter your network environment is what, you can always find the camera by Installation Wizard II with the IP address 169.254.x.y.
And then, please double click the camera found by Installation Wizard II or directly type the IP address to your Internet Explorer URL box to access your camera (you do not need to change your PC's IP address). After access your camera, please go to "Network" page to configure proper network settings.
See if the devices are available via mDNS, as well; download the Bonjour Browser and have a look around your LAN. (If you're very lucky, the cameras might be visible and chatting on mDNS.)
Might also try resetting one of the cameras back to factory defaults, and seeing if you can get them to re-ask the DHCP server.
(I've had issues with some HP printers and DHCP clients and IP address assignment, but that's fodder for another discussion. And I also wouldn't rule out a rogue DHCP server, either. I've seen all sorts of unexpected stuff connected to networks over the years...)

WLC2504 clients not receiving DHCP leases

I'm stock with a 2504 using version 7.0.220.0 that won't lease out DHCP adresses
Wifi clients are unable to get a DHCP lease from an external DHCP server.
The WLC are handling 3 WLAN, 2 using internal DHCP server, 1 (that wont work) using external DHCP. The external DHCP server, is a router/firewall (out of my reach) that suffered from a power out, a short while ago, ever since the DHCP is not working on that VLAN, if client are getting static ip adresses, everything works fine. If i'm using the same network link, and plug it into a computer, I get a DHCP address.
I've enable DHCP proxy
Debbuging DHCP, using: Debug DHCP packets enable
Gives me this:
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP received op BOOTREQUEST (1) (len 308,vlan 20, port 1, encap 0xec00)
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option len (including the magic cookie) 72
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: message type = DHCP INFORM
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 12 (len 1) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP option: 55 (len 13) - skipping
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP options end, len 72, actual 64
*DHCP Socket Task: Nov 08 14:21:11.397: c8:0a:a9:cc:6d:f6 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 68, op: 'BOOTREQUEST')
Thanks

Hi Steen,
When a client is in DHCP REQ state on the controller, the controller drops DHCP inform packets. The client will not go into a RUN state on the controller (this is required for the client to pass traffic) until it receives a DHCP discover packet from the client. DHCP inform packets are forwarded by the controller when DHCP proxy is disabled.
Please check this, if still u r facing issue then provide more info.
Can you please paste a client debug of the client having DHCP issues.
Go to cli of the wlc and run the client debug . Diconnect the client then reconnect and gather the output and post.
Regards

RV180W firmware 1.0.5.4 DHCP lease problem

Similar Messages

Maybe you are looking for