Unable to obtain IP from d link DIR-615

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Unable to obtain IP from d link DIR-615

scrotebags

4 posts

Wannabe Geek

#30806 21-Feb-2009 21:43

Hi all,

I new to the forums so please dont flame me.

I have hunted high and low for an answer to my problem and havent been able to get anywhere.

I am a TCL customer (cable) and am trying to connect 3 PC's and 1 xBox through a d link DIR-615 (version C2 running 3.01b firmware - updated after contacting d link support.)

The problem appears to be obtaining an IP for the wireless laptops connecting to the router. Sometimes they connect fine for a few hours/day and then I cant connect to the router and I keep getting a windows "limited or no connectivity" error.

I have enabled DHCP. Im running WPA/WPA2 with a TKIP cipher. The PSK is only 10 letters long (as I have heard of problems with longer PSK's).

It appears that when I change the PSK to something new the laptops are able to obtain a connection without a hassle and then the process begins again where I have to change the PSK on the router and laptop and then it is able to connect. I have absolutely no problem connecting a wired PC to the router.

Ideas?
Solution?

Much appreciated.

mdude409

2 posts

Wannabe Geek

#198158 26-Feb-2009 09:43

I just got a new DLINK DIR-615 and began seeing the same problem.

This was happening to me after I had a good connection for a relatively short period of time, maybe a few hours, maybe less than an hour. I would press the"Repair" option on the menu of my network connection utility and the "Limited or no connectivity error" always occurred after attemping to aquire a new IP address. If I reset/rebooted the router I was good after running repair on each of the clients again.

I looked into the DLink router configuration utility at 192.168.0.1 (with a pc connected to the router by cable) and found that under the Network Settings section, there was a subsection for adding DHCP reservations. Clients are typically dynamic but always use the same addresses. There is a list of the clients shown in this subsection in the list with the header "Number of Dynamic DHCP clients: #" Generally this list is all those devices you have in your house that you had used to connect. There is a column "Expires" that shows a date for when the address expires and in my case all the dates were bogus (May 12 2008) which might explain why it disconnects, not sure, but no matter.

What I am sure if is that I should never need to aquire new addresses in my own subnet. Next to each listed client is a link to "Reserve" the address for the specific device. Each attempt to aquire in the future will just give the same address back. Be sure to save your changes.

This fix worked quite well for me and all my clients on my home network. I hope it works for you.
Good luck.

scrotebags

4 posts

Wannabe Geek

#198214 26-Feb-2009 13:17

Yeh thanks for that. I had reserved the DHCP addresses for each of the clients previously and still got the same issue. I have recently had to "downgrade" to a WEP 128bit secure connection which seems to have solved the issue. The point was raised elsewhere that as 11n is stil in a draft format at this stage then the WPA security and ciphers are somewhat untested and therefore not overly reliable as of yet or there could be unidentified issues such as these on some networks.

It was also recomended to me to try and use a AES cipher rather than TKIP when enabling WPA security. I may try that later down the track as WEP is working 100% reliable at the moment.

Ragnor

8223 posts

Uber Geek

Trusted

#198220 26-Feb-2009 14:58

Definately use AES rather thanTKIP if your wireless router and all the wireless network cards in your machines support it.

perkhouse

1 post

Wannabe Geek

#201283 15-Mar-2009 14:45

I have a DIR-615 (hw vC1 fw v3.01) and I'm having similar problems. My wired devices are obtaining an IP and able to access the 'net, but the wireless devices never get a valid IP address.

I've tried WEP, WPA, and WPA2, but none of the (WEP and WPA compatible) devices will get an IP unless I disable security. I really hate the idea of paying for my neighbor to surf, but right now I'm running it unprotected, yet "invisible".

**edit: I also noticed that the check boxes are marked contrary to their function: "visible" is actually invisible and "invisible" is actually visible. (Not that it really helps if someone knows what they're doing.)

mdude409

2 posts

Wannabe Geek

#202147 19-Mar-2009 12:34

I do not know if it will help, but I did find that I also had to adjust to the proper security type in the Windows Network connection properties on the clients. Seems that it was not always able to correctly detect (WEP, WPA, encryption method etc.) but fortunately it's something I had to do only once.

On a seperate note; I did use AES cipher for WPA, still am, never tried WEP. But my problem was still not resolved until I started reserving addresses.

For what it is worth; My original IP address problem was only with my two XP machines, not with Vista machine and not with the Ipod Touch. They were good even without my reserving adresses for them. I assume it was no coincidence that it was the same two XP clients that had initial trouble identifying the proper security types. Older OS on clients with newer WIFI device and firmware and protocols; Scrotebags may have hit the nail on the head.

But since I made the changes all are still good. No problems in nearly a month now.