Jeg har ikke prøvet via trådløst, det virker ihvertfald heller ikke.
Det supportere mit trådløse netværkskort ikke.
Ja, både udefra og indefra.
Jeg har dog ikke nået at afprøve om det virker fra standby. er på arbejde nu.
\en di-524 virker fint med wol, ingen problemer der.
nu prøver du vel ikke at bruge wol på det trådløse, for det virker jo kun med kabel\
Jeg sad og læste igår at den ikke kunne, fordi den sender ikke kontinuerligt til pc´erne. Derfor virker det kun så længe den lige har været tændt (pc), ellers vil dlink 524, automatisk "glemme" dem. Fra en google.group.
>What I don't get is: Even if I have a static IP address, so far it does
>not work because the PC is off and so the router "forgets" about it,
>right? So the static IP address will only see to the PC getting the
>same IP address everytime it's on -- but there is no static route when
>it's off, because there is no route at all. Or is there??
Do you have control over the office DI-524 router?
You have a good point. There's no ARP table entry in the router if
the PC is turned off. RARP (reverse ARP) will work if the router
supports it. I don't think it does. Let's try this a bit
differently.
1. Leave your PC set to DHCP assigned IP address, not static. Assign
a "static DHCP" IP address to your client computer in the DI-524:
http://support.dlink.com/emulators/di524/h_dhcp.html At the bottom of the page. Note that the IP is defined by the PC's
MAC address. This will insure that the router ARP table is
permanently populated with your PC's MAC and IP address when it's
turned off.
2. Port forward some high numbered port to your PC's IP.
http://support.dlink.com/emulators/di524/adv_virtual.html This port forwarding is permanent and does not change whether the PC
is on or off.
>I have tried the Depicus-program. That's the one that worked before
>with my Netgear router, so the program is great.
That's the one I use. I also use the web based versions when I don't
have the program handy.
>My Netgear router was a FWG114P, I had v1 and v2, always upgraded the
>Firmware first, both worked fine regarding the WOL (because you can
>port forward to broadcast).
Amazing. I'll have to try that.
>On the other hand, the DynDNS-service did
>not work properly, it lost interest in updating the IP address after
>about five days...
>Now DynDNS works fine, but WOL doesn't (so far).
I've had the same problem with a few routers with built in DDOS
clients. They just seem to go comatose after a few days. On the
"does not work" list are, DI-604 rev c1, WGR-614v5 and v6, and DI-514.
I ended up using the DynDNS Windoze client on the PC, which works well
enough. DynDNS is trying to get vendors to certify clients, but the
small number of certified routers is not impressive:
http://www.dyndns.com/support/clients/hardware/ ----
http://groups.google.com/group/alt.internet.wireless/browse_thread/thread/856388ee586d8884/9a5f15c4d17d95da?lnk=gst&q=dlink+524#9a5f15c4d17d95da----
