SOLVED D-Link DI-624 "A Network Cable is Unplugged" error

[Paperlantern]

Ok, jsut bought the new wireless router, model in the title. Getting a little peeved. It runs great as a wired router, all things do as should, performance is pretty good. However, whenever i invoke the wireless feature, such as log onto my laptop wirelessly, sometimes it will come up and say "wireless network unavailable", however not all the time, what REALLY gets me pissed is, when i'm on the laptop, my two desktops, will flip out and the little bubble that says "A Network Cable is Unplugged" pops up and goes away like every 20 - 30 seconds. if i shut off the laptop, it seems to go back to normal after a little while. but if i turn on the laptop again, whammo, wired PC's go ape. Is there something interfereing? should i disable something? i'm getting a little mad here, any help or suggestions will be appreciated, thanks

 

[stonecold3169]

I'm having the same issue with the same unit. It's like the processing chip in it overloads itself or something, because if I'm using my notebook and PC simultaniously it errors like that every hour or so... if I'm using just the PC, I error maybe once ever 12-16 hours. Sooo weird. I tried turning off the wireless part of it for now, going 20 hours and strong on the PC without the network cable is unplugged error... of course, this is far from acceptable, but at least now we know where the error comes from

 

[Jobu]

I have this same model router, and have read that it likes to reboot randomly from time to time. Maybe that's what is happening? Have you upgraded the firmware since purchasing it? I upgraded the firmware the day I bought it and haven't seen any sort of problem with mine, wired or wireless.

 

[dmcowen674]

Originally posted by: Jobu
I have this same model router, and have read that it likes to reboot randomly from time to time. Maybe that's what is happening? Have you upgraded the firmware since purchasing it? I upgraded the firmware the day I bought it and haven't seen any sort of problem with mine, wired or wireless.

I have the same unit as well, one of the first newer revisions with one antenna, upgraded the firmware for the 108 meg and have had no problems with the unit since I plugged it in. I'm puzzled by the posts I'm reading from people.

Paperlantern, did you select an IP address for the Router's Gateway address or let it pick a number?

That's one of the only thing's I can think of I did different from everyone else.

 

[Paperlantern]

SOLVED! Now i have no clue why i didnt think of this sooner, but its PAINFULLY obvious. THe wireless router runs on the same freqency as our wireless phone. Since the model keeps tabs on the handsets from time to time to update missed calls and so forth, its always messing with it, but the really noticable problem is when you are actuall on a call on thw phone, thats when everything goes ape, i had to return it, i couldnt use it with the phone ive got... 2.4GHz... youd think someone would have thought of that

 

[kranky]

Don't beat yourself up, as it's not as obvious as you might think. My sister (who does networking for a living) had the same problem in her house last month and couldn't figure it out. I asked if she had a new cordless phone by any chance, and she said, "Yeah, I just got...CRAP! It's 2.4! 2.4!"

Your microwave might also interfere with a 2.4Ghz network.

There are some 2.4Ghz cordless phones now that are claimed to be "network friendly" and not step on a wireless network. VTECH is one that comes to mind.

 

[dmcowen674]

Originally posted by: Paperlantern
SOLVED! Now i have no clue why i didnt think of this sooner, but its PAINFULLY obvious. THe wireless router runs on the same freqency as our wireless phone. Since the model keeps tabs on the handsets from time to time to update missed calls and so forth, its always messing with it, but the really noticable problem is when you are actuall on a call on thw phone, thats when everything goes ape, i had to return it, i couldnt use it with the phone ive got... 2.4GHz... youd think someone would have thought of that

That is a really weird error for the Router to give for frequency interference. Glad you got it worked out but clearly there is still more work to be done with Wireless units giving proper diagnostic feedback as to what's happening.

I'll forward this info on to D-link.