D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: tipstir on January 30, 2009, 12:51:17 PM
-
I had seen this a while ago by turning on the logs...
(http://pic19.picturetrail.com/VOL1099/4465559/21344768/353113960.jpg)
I also got 300mbps link message under SP3 then the wireless when down. Now this is the only wireless device active is the DIR-655. I think it's has to do with WPA2, so now I've gong back to WPA to see how it goes for now. Office 2007 (Outlook) was trying to access Exchange File, but it couldn't. Still weird if you ask me.
-
Check the forum, there's a lot of references/solutions for this issue.
-
Check the forum, there's a lot of references/solutions for this issue.
Where in this forum of thousands of post is this solution? I've disable the logs again.. Shutdown the wireless it's not broadcasting. Wireless mon reports nothing from that. But still on Turbo G for now using until that problem with DIR-655 could be solve. Again this is with firmware 1.11 not the beta versions.
-
There's a button called 'Search'. Use it, it really makes life a lot easier :P
If you really desperate, you can use 'Advanced Search'!
Sorry voor the sarcasm, but you've made it quite easy...
-
There's a button called 'Search'. Use it, it really makes life a lot easier :P
If you really desperate, you can use 'Advanced Search'!
Sorry voor the sarcasm, but you've made it quite easy...
Funny guy aren't you.. If you had seen the post thread link it would be nice to post it here. That's all I was asking.. But there always got to be a funny guy in the bunch!
Yes I did search manually, but I know you know where.. Anyway everyone going to be different.. I can't think they're going to be as helpful as me.. Thanks anyway..
-
Yeah, you're making it irresistible. ;)
A forum usually has two functions in my personal opinion:
1. as a resource for sharing info on how to solve an issue
2. as a place to address any questions or issues that are not present or new
I guess that's why they keep a record of all the 'closed' issues.
If you consider the forum to be some kind of helpdesk where you can address 'staff' to help you out that's your prerogative. But don't be insulted when reality does not seem to comply with those ideas.
But that are just my personal thoughts. If there is anybody who wants to copy previous posts here, fine with me. But I think you're very capably to find those resources yourself.
-
I had seen this a while ago by turning on the logs...
(http://pic19.picturetrail.com/VOL1099/4465559/21344768/353113960.jpg)
I also got 300mbps link message under SP3 then the wireless when down. Now this is the only wireless device active is the DIR-655. I think it's has to do with WPA2, so now I've gong back to WPA to see how it goes for now. Office 2007 (Outlook) was trying to access Exchange File, but it couldn't. Still weird if you ask me.
Hi tipstir,
Do you have a Metal Filing Cabinet around near the DIR-655 Router? If so move it and also move any base of a Wireless Phone System.
-
Hi tipstir,
Do you have a Metal Filing Cabinet around near the DIR-655 Router? If so move it and also move any base of a Wireless Phone System.
Thanks for helping... :)
No, it's in a network closet small enough to house everything for the network. Nothing has been changed.
My wireless phone system is on 5.8GHz DSS. Nowhere near the DIR-655.
This was taken back in Dec 08, when I was testing Gig switch from Netgear GS605. One of the worst Gig switch you can buy reaches 131F in my temp probe testing. Anyway That's been removed. But just to give you an idea of what I working with below..
(http://pic19.picturetrail.com/VOL1099/4465559/21344768/350675530.jpg)
I've shutdown the ANT since when I first reported the problems. I going to have to bring them back online as the Wireless N Access Point I using with its paired up PCMICA cards can't give me Strong enough N signal in one area. I using Odyssey Access Client Manager. Forget Windows Wireless for N device crap. When it comes to G it's okay to use Odyssey tunneling I get strong -51 to -54dB for wireless N using auto 20/40Hz.
-
Yeah, you're making it irresistible. ;)
A forum usually has two functions in my personal opinion:
1. as a resource for sharing info on how to solve an issue
2. as a place to address any questions or issues that are not present or new
I guess that's why they keep a record of all the 'closed' issues.
If you consider the forum to be some kind of helpdesk where you can address 'staff' to help you out that's your prerogative. But don't be insulted when reality does not seem to comply with those ideas.
But that are just my personal thoughts. If there is anybody who wants to copy previous posts here, fine with me. But I think you're very capably to find those resources yourself.
I am sure you're been at this for some years now as I have been from old dial-up to what we have today. If your so smart and have the answer just come out with it. I don't see the point of playing head games. This forum to help owners of dlink products but it's not a help desk those are completely different. Don't even bring that into this situation. I am no beginner.
My ideas what do you mean? This is not the only Wireless N Router I own nor is it the only one I have as a router. If you have solve the mystery riddle to the puzzle I don't see what's the beef in not sharing the answer.
Enough with the joke comments, not require here I don't find it funny..
-
Did you try changing the radio channel? I know that wireless phones, both on the 2.4Ghz and 5.xGhx bands, can affect the wireless network routers. The only phones that are supposed to be "wi-fi" friendly are the new DECT 6.0 models.
-
My ideas what do you mean? This is not the only Wireless N Router I own nor is it the only one I have as a router. If you have solve the mystery riddle to the puzzle I don't see what's the beef in not sharing the answer.
To sum up all the possible solutions it would take a whole page (especially since the info provided about your setup etc. is nothing but a bare minimum). Since you're not beginner you should know that.
-
Did you try changing the radio channel? I know that wireless phones, both on the 2.4Ghz and 5.xGhx bands, can affect the wireless network routers. The only phones that are supposed to be "wi-fi" friendly are the new DECT 6.0 models.
DECT 6.0 has 1.9GHz band.. I had it set to auto which is channel 6 for month 1/2 it works then bang that wireless up and down started to happen.. So what I did was changed the channels manually to 1, 9 where I wasn't using those two. It seem to work then no wireless it just stopped. I had to shutdown the power then turn it back on and it worked.. Then later on I could hear the wife saying "I AM GETTING TIME OUTS AGAIN"
So oh boy..
-
To sum up all the possible solutions it would take a whole page (especially since the info provided about your setup etc. is nothing but a bare minimum). Since you're not beginner you should know that.
Done before.. I just posted the logs here to see if anyone else had the same issue or had a way to fix the problem. What you see in the image is kind of rough I as I was adding more devices to the network and trying to see if the GS series could be use as 100mbs switch but nah it just gets overheated. No heatsink inside I would have to add one to them. Real pain.
If no one has solve this problem I'll just have to work with what I got for now. Router is quick with 1.11, I can't use the current crop of beta firmware, until I see some sort of speed gain and not speed reduction. Again what might be working for some might not work for me as everyone setup is going to be different.
Only think I could do is reset to factory defaults prior to a full backup then test with the factory defaults and see if there is a problem with the wireless side. Or downgrade to 1.10, then go back to 1.11. Might not make a difference though.
-
The cause of the wireless restarts can be client side.
If the problem persists on all firmwares this might be the case. Also a broken radio can be an option, but only when all other options are eliminated.
Unless you've tried the other solutions/options already published nobody can be sure you need a different approach. Unless you give more info, redirecting you to those posts is really the only option.
-
The cause of the wireless restarts can be client side.
If the problem persists on all firmwares this might be the case. Also a broken radio can be an option, but only when all other options are eliminated.
Unless you've tried the other solutions/options already published nobody can be sure you need a different approach. Unless you give more info, redirecting you to those posts is really the only option.
Well I just brought down the network, and removing the DIR-655 I'll test that in a lab conditions to see what's the the issue could be the wireless hardware inside or something else. I have another router configured to match DIR-655 network configuration and its running brand new version of DD-WRT v24 sp2 running now in place of the DIR-655. If it's hardware I'll see if DLINK will replace it as it's under warranty. If not I guess another purchase of Wireless N router. Oh I hope not?
Again thanks to all who posted suggestions..
-
Finally got to test out what's the cause.. But I started to get the same results as wireless access point.
Wireless Up -- Wireless Down then gw_interupt on one wireless N.
Firmware 1.11 problem
Firmware 1.21b11_beta02 working..
Using 40Hz 802.11n only
WP2/AES
Seems to be working...
-
Also I did find the posting here about gw_interrupt using google lead me back here but what I found didn't solve the problem. Well anyway it works.. I am just going to use DIR-655 in Wireless N Access Point until next firmware release hopefully that would be sooner or later..