Print

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

[iron2000]

Just bought this router on the 14th.
Updated the firmware to v2.02.
(It came with 2.01)

I set the IP address range to 10 slots and crated reservations for the 10 IP address to 10 devices.

The problem is compared to my previous Netgear, I need to wait for about 1 minute for the router to give my PC the IP address.(Network Connections say "Identifying...") I'm on Windows 7 but the same thing happens on my sis' Mac Mini.

Both computers are connected to the router via cables.

Also strange is that the dhcp client list (the list above the reservations) only displays my PC but not my sis' mac which is also connected and has an IP.

I downgraded to 2.01 again but theres still this problem.

On Monday I did a factory reset.
Seems to be working as the other computers showed up dhcp client list.
Didn't input the full list of 10 reserved IP this time.

But the problem came back again.
This time right after I filled up the full 10 IP reservations.
(Set the dhcp IP range to 10 slots)

Got to do another factory reset and maybe go back to 2.02 again to take a look.

Other things I suspect that might have cause it:
- Turning both router and modem on and off at same time (share same socket)
- Turning router on and off with the cables of the client PCs connected
- Router borged down by Xmas Port Scan attacks
- The so called 'green' functions of the router


If the problem come back again I would have no idea about it.

By the way, anyone knows if the 2.02 fw is final or still beta and does anyone have the release notes for it?
(Get 2.02 from the SG site.)

Thanks


[EDIT]
Can't pinpoint this problem as now the router seems ok again.
Perhaps is its weakness to port scan attacks?


[EDIT]
Ok, so I updated back to 2.02.
Disabled and enabled the connection, ok no 1 minute "Identifying" wait.
Only my PC is connected.
Then I went to turn on my sis' Mac Mini.
Fine, no one minute wait on her side too.
Shut down her Mac.

But when I come back to my PC, disabled and enabled the connection.
The 1 min wait came back again!

Also saw that from the log my sis' Mac gave a ping flood to the router.
(Maybe it one of her start up apps? The Twitter app or Adium?)

Could ping floods and port scan be the weakness of this router?

[iron2000]

Ok better start on a new post.

Hmm..

Just did a factory reset again.
Disabled and enabled my connection, ok no 1 minute "Identifying" wait.

Logged on to router.
Strange, no captha this time round after this second factory reset.
Set up internet and wireless stuff.
Shrink DHCP from 100-199 to 100-125 this time (26 slots) just in case since it allows 24 reservations.
Reserved IP for my PC.
Log out.
Disabled and enabled my connection, ok no 1 minute "Identifying" wait.

Turn on sis' Mac.
Straight away it gets IP.
Disabled and enabled my connection, ok no 1 minute "Identifying" wait.

Logged on to router.
Both computers appear at DHCP Client List.
(Always when the other computers don't appear there, there will be the problem)
Reserved IP for sis' Mac.
Log out.
Disabled and enabled my connection, ok no 1 minute "Identifying" wait.

All ok for now after the second factory reset.


It was ok too after the first factory reset on Monday.

After I reserved the IP for the computers that day, I found that they are still holding their old IP.
And I turned off the router and modem (share same socket) to make the router forget.
Then when I turn on and logged in I found that the our computers are not listed at the DHCP Client List anymore.
But they did have IP and can access the net.
And there was no 1min wait then when I disable and enable my connection.

Wasn't until the next day when I did a full IP reserve of all 10 slots that the 1 min wait reappear.
Unchecked 2 slots and the wait disappears.
But later that night when I return home, the 1 min wait appears again.

Then it led to the second factory reset as described above.


Sorry for being long winded but I'm trying to give enough information.
Hope someone has an idea of whats going on.
Thanks.

[iron2000]

Flashed DD-WRT and it seems to be working rather well for now.

So it could be D-Link's firmware?

[smithlanger]

sounds good to me 

[altair_xms]

same problem (for wireless connection using my laptop): after updating to WinXP SP3 the problem doesn't occur ...