DLINK DI-624 MY STORY

Here is my story, from start to finish, after trying to find the ideal
extended range-wireless-solution, this happened on June 19 of 2004:



1. Out of the box, lets play! NOT!

I bought DLink DI-624 Rev C wireless router and DWL-G800AP range extender.
Off the box they wouldn't work together, even though the yellow sticker on
the box said it the repeater would ONLY work with this specific wireless
router. So the problem was fixed with a simple upgrade on the wireless
router from version 2.xx to 2.42, and the range extender to 1.02; but that
only fixed the spontaneous restarting of the router produced just by feeling
the "presence" of the range extender. My PC thru wired-lan and my wireless
laptop had access to the internet now.



2. Internet working? NOT!

Some pages wouldn't load. Mtu Size had to be fixed on the router wan
settings. using ping -l 1460 -f yahoo.com worked. added 28 to that and
placed that result on the settings, no biggy.



3. Wired-LAN to WIRELESS packets going thru? NOT!

So then, there I was, testing the connection from my wireless laptop to my
pc connected to the di-624. No matter what I did, I couldn't make my laptop
see my pc or vice versa; pings wouldn't go thru either. I had to disable
wireless encryption for them to see each other; isn't that weird?? Seems
like the encrypted packets were "decrypted" just when received by the wan
port, but left encrypted when sent to the LAN port, so the pc was like
"HUH???" (that's just my theory).



4. FIXED? NOT!

There! So now the computers could see each other AWESOME! I didn't care
about the encryption as I thought MAC filtering was security enough. So
there I was pinging my PC, when all of a sudden NO REPONSE! hrmm... ah..
wait a minute.. Yes.. it started working again, but then it stopped... and
came back again, so I peek at my pc screen, and XP popped up the "LAN cable
unplugged" message, OH! but the router was restarting again! why would it be
doing that?! hrmm.. OK, so after reading a bunch of forums and posts, I did
the famous "crash recovery" flashing. And I believe that fixed the
resetting problem.



5. DHCP, why won't you talk to me?

If I recall correctly this only happened on the LAN connection. So this
happened a few times, I had to restart the router every time.



6. LAN has no access to WAN, but wireless does! HUH?!

Ok so there I was, playing Ut2K4 thru di-624 when all of a sudden connection
was lost. Was I able to surf? Nop. ADSL Down? Nop. Wireless LAPTOP Lost
internet too? Nop. So router refused to give any lan port access to wan.
Hell, I just restarted the router and started playing again. But crap, it
did it again after 10 minutes. I fed up with it, so I connected my old
reliable Linksys hub to the ADSL modem, and to the wan port of the di-624
and everything worked perfectly; even the laptop had internet. No more lost
connection at the pc because it simply wasn't using the DLink router. I
played ut2k4 for 3 hrs :P



7. Version 2.44, available. NOT!

Some forums posted 2.44 was available for di-624 but it wasn't on DLink
website! HRmm.. it seems they pulled it off (isn't that a serious sign of
unprofessionalism?) Since they only showed 2.42 as the latest one, I
started my search for 2.44. I found it thru Google on an inaccessible page
of DLink site. To the point, 2.44 was even more erratic than 2.42, no
wonder they pulled it off the website.



8. After all, tested for 7 days.

So the problems persisted for the entire testing period. DHCP wouldn't
response at times (wouldn't assign an IP to the LAN port). Having the pc
connected to the router, logs on my firewall showed lost of connection about
72 times during the last 7 days. The range extender had to be restarted
only twice.



9. Returning back to the store.

Condensed version of my conversation:

Me: "15% restock fee?!! NO WAY! This product doesn't work, neither any of
those on the shelves, I want a complete refund".

Manager: "Sir, DLINK has the lowest RMA rate than any other wireless product
manufacturer"

Me: "Ok, u want to go test these products and then any other one on your
shelf? DLink has too many problems"

Manager: "If it has so many problems why did u buy it?"

Me: "Because it's the only range extender you sell here. Why are you
selling something that DOESNT work?"

Manager: "Erick! Come here! Sir, this is our network specialist"

Erick: "What's wrong?"

Me: "These products don't have a firmware upgrade to fix known problems on
it, problems also posted by some people on the net, so I'm not the only one
having problems. The LAN ports stops working, DHCP stops working, it resets
by itself"

Erick: "Okay, what do u want?"

Me: "A refund"

Erick: "No problem, go to customer service and tell them I authorized it"



Back on customer service, waiting there, I saw there were 3 other di-624
boxes that were returned.



10. Running to the other store where they sell Buffalo Air Station with
range extender.

IT WORKS!!! VERY stable. VERY reliable.

And I wonder why is it so difficult to test products before putting them on
the shelves!



================================================== ========================



I wrote all that in June 27, it's now August 24 (2004). Two months later,
and DLink is only showing a BETA firmware for di-624 v2.45 succeeding 2.42.
As a funny side note... seeing their "fixes" they fixed "DHCP disconnect
bug" twice, once on version 2.41, and again on 2.42. If I were in charge in
DLINK, I would fire those programmers today.



Two months later, and I only had to reset the Buffalo once, and I think it
went nuts because of an electric storm. Also, notice Buffalo have not needed
to upgrade their firmware for over 6 months already



"DLink best wireless product manufacturer"?? BS!!!

I'm really surprised to hear about these experiences!

I've been running with a DI-624 Rev C (one antenna) and a DWL-2100 AP
(in repeater mode) for the last 6 months and haven't experienced a
single problem. I thought I would toy with the idea of running a
server behind it (not really expecting it to work with such a cheap
product) and that has been quite fine too!! I'm very happy with
D-Link support as well, they helped me setup WPA the other day when I
decided to get rid of WEP.

Maybe you just had a bad unit!!!

Martin


"Ivan" <(E-Mail Removed)> wrote in message news:<grBWc.14373$(E-Mail Removed)>...
> Here is my story, from start to finish, after trying to find the ideal
> extended range-wireless-solution, this happened on June 19 of 2004:
>
>
>
> 1. Out of the box, lets play! NOT!
>
> I bought DLink DI-624 Rev C wireless router and DWL-G800AP range extender.
> Off the box they wouldn't work together, even though the yellow sticker on
> the box said it the repeater would ONLY work with this specific wireless
> router. So the problem was fixed with a simple upgrade on the wireless
> router from version 2.xx to 2.42, and the range extender to 1.02; but that
> only fixed the spontaneous restarting of the router produced just by feeling
> the "presence" of the range extender. My PC thru wired-lan and my wireless
> laptop had access to the internet now.
>
>
>
> 2. Internet working? NOT!
>
> Some pages wouldn't load. Mtu Size had to be fixed on the router wan
> settings. using ping -l 1460 -f yahoo.com worked. added 28 to that and
> placed that result on the settings, no biggy.
>
>
>
> 3. Wired-LAN to WIRELESS packets going thru? NOT!
>
> So then, there I was, testing the connection from my wireless laptop to my
> pc connected to the di-624. No matter what I did, I couldn't make my laptop
> see my pc or vice versa; pings wouldn't go thru either. I had to disable
> wireless encryption for them to see each other; isn't that weird?? Seems
> like the encrypted packets were "decrypted" just when received by the wan
> port, but left encrypted when sent to the LAN port, so the pc was like
> "HUH???" (that's just my theory).
>
>
>
> 4. FIXED? NOT!
>
> There! So now the computers could see each other AWESOME! I didn't care
> about the encryption as I thought MAC filtering was security enough. So
> there I was pinging my PC, when all of a sudden NO REPONSE! hrmm... ah..
> wait a minute.. Yes.. it started working again, but then it stopped... and
> came back again, so I peek at my pc screen, and XP popped up the "LAN cable
> unplugged" message, OH! but the router was restarting again! why would it be
> doing that?! hrmm.. OK, so after reading a bunch of forums and posts, I did
> the famous "crash recovery" flashing. And I believe that fixed the
> resetting problem.
>
>
>
> 5. DHCP, why won't you talk to me?
>
> If I recall correctly this only happened on the LAN connection. So this
> happened a few times, I had to restart the router every time.
>
>
>
> 6. LAN has no access to WAN, but wireless does! HUH?!
>
> Ok so there I was, playing Ut2K4 thru di-624 when all of a sudden connection
> was lost. Was I able to surf? Nop. ADSL Down? Nop. Wireless LAPTOP Lost
> internet too? Nop. So router refused to give any lan port access to wan.
> Hell, I just restarted the router and started playing again. But crap, it
> did it again after 10 minutes. I fed up with it, so I connected my old
> reliable Linksys hub to the ADSL modem, and to the wan port of the di-624
> and everything worked perfectly; even the laptop had internet. No more lost
> connection at the pc because it simply wasn't using the DLink router. I
> played ut2k4 for 3 hrs :P
>
>
>
> 7. Version 2.44, available. NOT!
>
> Some forums posted 2.44 was available for di-624 but it wasn't on DLink
> website! HRmm.. it seems they pulled it off (isn't that a serious sign of
> unprofessionalism?) Since they only showed 2.42 as the latest one, I
> started my search for 2.44. I found it thru Google on an inaccessible page
> of DLink site. To the point, 2.44 was even more erratic than 2.42, no
> wonder they pulled it off the website.
>
>
>
> 8. After all, tested for 7 days.
>
> So the problems persisted for the entire testing period. DHCP wouldn't
> response at times (wouldn't assign an IP to the LAN port). Having the pc
> connected to the router, logs on my firewall showed lost of connection about
> 72 times during the last 7 days. The range extender had to be restarted
> only twice.
>
>
>
> 9. Returning back to the store.
>
> Condensed version of my conversation:
>
> Me: "15% restock fee?!! NO WAY! This product doesn't work, neither any of
> those on the shelves, I want a complete refund".
>
> Manager: "Sir, DLINK has the lowest RMA rate than any other wireless product
> manufacturer"
>
> Me: "Ok, u want to go test these products and then any other one on your
> shelf? DLink has too many problems"
>
> Manager: "If it has so many problems why did u buy it?"
>
> Me: "Because it's the only range extender you sell here. Why are you
> selling something that DOESNT work?"
>
> Manager: "Erick! Come here! Sir, this is our network specialist"
>
> Erick: "What's wrong?"
>
> Me: "These products don't have a firmware upgrade to fix known problems on
> it, problems also posted by some people on the net, so I'm not the only one
> having problems. The LAN ports stops working, DHCP stops working, it resets
> by itself"
>
> Erick: "Okay, what do u want?"
>
> Me: "A refund"
>
> Erick: "No problem, go to customer service and tell them I authorized it"
>
>
>
> Back on customer service, waiting there, I saw there were 3 other di-624
> boxes that were returned.
>
>
>
> 10. Running to the other store where they sell Buffalo Air Station with
> range extender.
>
> IT WORKS!!! VERY stable. VERY reliable.
>
> And I wonder why is it so difficult to test products before putting them on
> the shelves!
>
>
>
> ================================================== ========================
>
>
>
> I wrote all that in June 27, it's now August 24 (2004). Two months later,
> and DLink is only showing a BETA firmware for di-624 v2.45 succeeding 2.42.
> As a funny side note... seeing their "fixes" they fixed "DHCP disconnect
> bug" twice, once on version 2.41, and again on 2.42. If I were in charge in
> DLINK, I would fire those programmers today.
>
>
>
> Two months later, and I only had to reset the Buffalo once, and I think it
> went nuts because of an electric storm. Also, notice Buffalo have not needed
> to upgrade their firmware for over 6 months already
>
>
>
> "DLink best wireless product manufacturer"?? BS!!!

I've been having a similar problem with my DI-624 Rev. C and firmware
2.50. It continuously drops my LAN connection to only my computer,
which is running Shareaza. My other two computers 1 WLAN and the other
LAN never get dropped until I have to reboot the router so I can get my
computer back on the internet.

I've tried different things to stop it from dropping my connection like
removing the default settings that I would never use on the router.
I've turned off the logging completely thinking that maybe the log was
overflowing. But it only ever drops my computer the other two stay
connected and can talk to the internet and each other.

It would be nice to have the settings I export work on the next
firmware upgrade so I wouldn't have to manually go back and change
all of the settings each time an upgrade comes out!!
Good luck to all. I will post if I ever get this thing stable!

test
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> I've been having a similar problem with my DI-624 Rev. C and firmware
> 2.50. It continuously drops my LAN connection to only my computer,
> which is running Shareaza. My other two computers 1 WLAN and the other
> LAN never get dropped until I have to reboot the router so I can get my
> computer back on the internet.
>
> I've tried different things to stop it from dropping my connection like
> removing the default settings that I would never use on the router.
> I've turned off the logging completely thinking that maybe the log was
> overflowing. But it only ever drops my computer the other two stay
> connected and can talk to the internet and each other.
>
> It would be nice to have the settings I export work on the next
> firmware upgrade so I wouldn't have to manually go back and change
> all of the settings each time an upgrade comes out!!
> Good luck to all. I will post if I ever get this thing stable!
>

test
"AirHead" <(E-Mail Removed)> wrote in message
news:41780103$0$797$(E-Mail Removed). ..
> test
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
> > I've been having a similar problem with my DI-624 Rev. C and firmware
> > 2.50. It continuously drops my LAN connection to only my computer,
> > which is running Shareaza. My other two computers 1 WLAN and the other
> > LAN never get dropped until I have to reboot the router so I can get my
> > computer back on the internet.
> >
> > I've tried different things to stop it from dropping my connection like
> > removing the default settings that I would never use on the router.
> > I've turned off the logging completely thinking that maybe the log was
> > overflowing. But it only ever drops my computer the other two stay
> > connected and can talk to the internet and each other.
> >
> > It would be nice to have the settings I export work on the next
> > firmware upgrade so I wouldn't have to manually go back and change
> > all of the settings each time an upgrade comes out!!
> > Good luck to all. I will post if I ever get this thing stable!
> >
>
>

test
"AirHead" <(E-Mail Removed)> wrote in message
news:41780103$0$797$(E-Mail Removed). ..
> test
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
> > I've been having a similar problem with my DI-624 Rev. C and firmware
> > 2.50. It continuously drops my LAN connection to only my computer,
> > which is running Shareaza. My other two computers 1 WLAN and the other
> > LAN never get dropped until I have to reboot the router so I can get my
> > computer back on the internet.
> >
> > I've tried different things to stop it from dropping my connection like
> > removing the default settings that I would never use on the router.
> > I've turned off the logging completely thinking that maybe the log was
> > overflowing. But it only ever drops my computer the other two stay
> > connected and can talk to the internet and each other.
> >
> > It would be nice to have the settings I export work on the next
> > firmware upgrade so I wouldn't have to manually go back and change
> > all of the settings each time an upgrade comes out!!
> > Good luck to all. I will post if I ever get this thing stable!
> >
>
>

I basically went through the same process with a DLink 614+ router an
DLink DWL-800AP+ repeater. I could get onto the net but the tw
computers could not see one another in a workgroup. I tried ever
configuration, Microsoft network wizard, no encryption, n
firewalls--but nothing worked. I thought I was going crazy or stupid

I finally bought a Linksys WRT 55AG router and everything worke
perfectly right out of the box (using only 802.11b mode like the th
DLink). I almost couldn't believe it. I hate to think of all the hour
I wasted trying to figure out what "I" was doing wrong with the DLin
router.

I'll never touch a DLink product again


Ivan Wrote:
> Here is my story, from start to finish, after trying to find the idea
> extended range-wireless-solution, this happened on June 19 of 2004
>
>
>
> 1. Out of the box, lets play! NOT
>
> I bought DLink DI-624 Rev C wireless router and DWL-G800AP rang
> extender
> Off the box they wouldn't work together, even though the yellow sticke
> o
> the box said it the repeater would ONLY work with this specifi
> wireles
> router. So the problem was fixed with a simple upgrade on the wireles
> router from version 2.xx to 2.42, and the range extender to 1.02; bu
> tha
> only fixed the spontaneous restarting of the router produced just b
> feelin
> the "presence" of the range extender. My PC thru wired-lan and m
> wireles
> laptop had access to the internet now
>
>
>
> 2. Internet working? NOT
>
> Some pages wouldn't load. Mtu Size had to be fixed on the router wa
> settings. using ping -l 1460 -f yahoo.com worked. added 28 to that an
> placed that result on the settings, no biggy
>
>
>
> 3. Wired-LAN to WIRELESS packets going thru? NOT
>
> So then, there I was, testing the connection from my wireless laptop t
> m
> pc connected to the di-624. No matter what I did, I couldn't make m
> lapto
> see my pc or vice versa; pings wouldn't go thru either. I had t
> disabl
> wireless encryption for them to see each other; isn't that weird?
> Seem
> like the encrypted packets were "decrypted" just when received by th
> wa
> port, but left encrypted when sent to the LAN port, so the pc was lik
> "HUH???" (that's just my theory)
>
>
>
> 4. FIXED? NOT
>
> There! So now the computers could see each other AWESOME! I didn't car
> about the encryption as I thought MAC filtering was security enough. S
> there I was pinging my PC, when all of a sudden NO REPONSE! hrmm..
> ah.
> wait a minute.. Yes.. it started working again, but then it stopped..
> an
> came back again, so I peek at my pc screen, and XP popped up the "LA
> cabl
> unplugged" message, OH! but the router was restarting again! why woul
> it b
> doing that?! hrmm.. OK, so after reading a bunch of forums and posts,
> di
> the famous "crash recovery" flashing. And I believe that fixed th
> resetting problem
>
>
>
> 5. DHCP, why won't you talk to me
>
> If I recall correctly this only happened on the LAN connection. So thi
> happened a few times, I had to restart the router every time
>
>
>
> 6. LAN has no access to WAN, but wireless does! HUH?
>
> Ok so there I was, playing Ut2K4 thru di-624 when all of a sudde
> connectio
> was lost. Was I able to surf? Nop. ADSL Down? Nop. Wireless LAPTOP Los
> internet too? Nop. So router refused to give any lan port access t
> wan
> Hell, I just restarted the router and started playing again. But crap
> i
> did it again after 10 minutes. I fed up with it, so I connected my ol
> reliable Linksys hub to the ADSL modem, and to the wan port of th
> di-62
> and everything worked perfectly; even the laptop had internet. No mor
> los
> connection at the pc because it simply wasn't using the DLink router.
> played ut2k4 for 3 hrs :
>
>
>
> 7. Version 2.44, available. NOT
>
> Some forums posted 2.44 was available for di-624 but it wasn't on DLin
> website! HRmm.. it seems they pulled it off (isn't that a serious sig
> o
> unprofessionalism?) Since they only showed 2.42 as the latest one,
> started my search for 2.44. I found it thru Google on an inaccessibl
> page
> of DLink site. To the point, 2.44 was even more erratic than 2.42, no
> wonder they pulled it off the website.
>
>
>
> 8. After all, tested for 7 days.
>
> So the problems persisted for the entire testing period. DHCP wouldn't
> response at times (wouldn't assign an IP to the LAN port). Having the
> pc
> connected to the router, logs on my firewall showed lost of connection
> about
> 72 times during the last 7 days. The range extender had to be restarted
> only twice.
>
>
>
> 9. Returning back to the store.
>
> Condensed version of my conversation:
>
> Me: "15% restock fee?!! NO WAY! This product doesn't work, neither any
> of
> those on the shelves, I want a complete refund".
>
> Manager: "Sir, DLINK has the lowest RMA rate than any other wireless
> product
> manufacturer"
>
> Me: "Ok, u want to go test these products and then any other one on
> your
> shelf? DLink has too many problems"
>
> Manager: "If it has so many problems why did u buy it?"
>
> Me: "Because it's the only range extender you sell here. Why are you
> selling something that DOESNT work?"
>
> Manager: "Erick! Come here! Sir, this is our network specialist"
>
> Erick: "What's wrong?"
>
> Me: "These products don't have a firmware upgrade to fix known problems
> on
> it, problems also posted by some people on the net, so I'm not the only
> one
> having problems. The LAN ports stops working, DHCP stops working, it
> resets
> by itself"
>
> Erick: "Okay, what do u want?"
>
> Me: "A refund"
>
> Erick: "No problem, go to customer service and tell them I authorized
> it"
>
>
>
> Back on customer service, waiting there, I saw there were 3 other
> di-624
> boxes that were returned.
>
>
>
> 10. Running to the other store where they sell Buffalo Air Station with
> range extender.
>
> IT WORKS!!! VERY stable. VERY reliable.
>
> And I wonder why is it so difficult to test products before putting
> them on
> the shelves!
>
>
>
> ================================================== ========================
>
>
>
> I wrote all that in June 27, it's now August 24 (2004). Two months
> later,
> and DLink is only showing a BETA firmware for di-624 v2.45 succeeding
> 2.42.
> As a funny side note... seeing their "fixes" they fixed "DHCP
> disconnect
> bug" twice, once on version 2.41, and again on 2.42. If I were in
> charge in
> DLINK, I would fire those programmers today.
>
>
>
> Two months later, and I only had to reset the Buffalo once, and I think
> it
> went nuts because of an electric storm. Also, notice Buffalo have not
> needed
> to upgrade their firmware for over 6 months already
>
>
>
> "DLink best wireless product manufacturer"?? BS!!!


--
Matt Slaight
brought to you by http://www.wifi-forum.com/