Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Beachguy]

Hardware revision is B1, and the firmware is 2.07A.

I have the DHCP set for the range of 192.168.0.100 to 192.168.0.199. However, when any device connected, it receives a 192.168.17.xxx address, not 192.168.0.xxx and I can't figure out why. This device is new- I bought it less than 6 weeks ago. The QC also seems a bit lower than my previous D-Link devices- I have had 7 or 8 D-Link routers and have been very happy with them. This one, not so much.

When I first installed this, it worked just fine, but after a couple of weeks, the .17 addresses started to show up and I started having access problems until I manually addressed the PCs, Macs, iPads, or Android devices. Now, ANY new device that comes in to the network grabs a .17 address, NOT a .0 one.

Any thoughts? I've always been a loyal D-Link customer for the last decade, but this has my confidence shaken.

Many thanks!

Beach

[FurryNutz]

Have you done a factory reset of the router?
Make sure devices are set up for automatic obtain IP addressing? Could your devices have been set for static from the previous router?
I would reset any networking settings on the devices, flush dns and release and renew for new IP addresses.

Make sure the Admin PW is set and is secure so nobody can gain access and change the settings.

[Beachguy]

Have you done a factory reset of the router?
Make sure devices are set up for automatic obtain IP addressing? Could your devices have been set for static from the previous router?
I would reset any networking settings on the devices, flush dns and release and renew for new IP addresses.

Make sure the Admin PW is set and is secure so nobody can gain access and change the settings.

All of the above have been done already. This affects new and old devices.

[FurryNutz]

Interesting....can you access the routers web page?
Any log entries regarding any issues?

Is this router new? Did you update the FW or did it come with v2.07 already loaded?

[Beachguy]

Interesting....can you access the routers web page?
Any log entries regarding any issues?

Is this router new? Did you update the FW or did it come with v2.07 already loaded?

Router is 6 weeks old, bought brand new. Came with 2.05A and tech support had me update it to 2.07A. It was already doing this at this point, 2.07A made no difference.

Nothing unusual in log files- usual zillion entries about blocked incoming SynAck packets.

[Beachguy]

I am suspecting I should return this and get a different make/model. I have been quite unhappy with this one, which is new for me with D-LINK.

[FurryNutz]

Any chance for a return for a replacement router? This should not be happening. I would return or RMA it.

[Beachguy]

Any chance for a return for a replacement router? This should not be happening. I would return or RMA it.

I'll need to find the receipt for it. I have the box it came in. I've been researching on the net, and had I done so before buying it, I would have avoided it. I'm seeing a lot of negatives. Meanwhile, my old 655s still crank it out like champs.

[FurryNutz]

The DIR-825 is a solid router. I think you got a hold of a bum router and updating it didn't fix it and should have been returned when this was first encountered. I enjoy my 825 greatly. Just found a bad one. Don't discount them all. Besides, the 825 is a 655, just with 5Ghz radio. 

Give another 825 a try. Should be good. Good luck.