Wake-on-lan issues, XP Pro, Dell Dimension 2350..

Hey all, bare with my long post. I just registered because I cannot for the life of me figure out this issue. I have tried every method, every tip from forums, nothing works. Normally I have no problem troubleshooting an IT problem but this one has gotten the better of me and I had to turn to a forum.

So I have a bit of an older machine, a Dell Dimension 2350 with Windows XP Pro w/ Svc. Pack 3. The PC is upgraded as much as possible within Dell's criteria..1 GB of RAM, all peripherals, video card, etc.. enough for me at this point. It has the retail motherboard (HERE) and retail integrated 10/100 Ethernet adapter.
[B]I have been trying to get the Wake-On-Lan feature to work from either within my own network or from over the internet from any network (ideal).[/B]

Network-wise, I have Comcast Cable internet which is used through a Linksys wireless router (a Wireless-G, WR-series) (my laptop uses the wireless but the desktop PC in question is obviously wired LAN). After reading several tutorials on Wake-On-Lan, I feel I've done everything needed but still am not getting it to work. I do know a few areas that the problem might be contatined in though, maybe one of you will see it.

First of all, I've rebooted and gone into Bios settings, into the Power Management tab, enabled the "Allow to Wake from PCI devices" option (the only WOL-related option in there; not sure how a PCI option would help me though if the network card isn't PCI. But there are no other Bios options for WOL, any ideas?). Then I've gone into Device Mgr and into my Network card settings, made sure that the power management settings has the "Allow this device to bring the computer out of standby" option turned on. Also, in the advanced tab, there is a category called Wake Up Capabilities (the only one in there that pertains to WOL). In there it gives options of 'Wake Up Frame' (default), 'None,' or 'Magic Packet.' I changed it to Magic Packet even though I read that it could be on Wake Up Frame and still work.

So, that takes care of network and Bios settings. From seeing these, I assume I do not need to connect any 3-pin wires from the network card to the system board to make this work since it apparently is in fact an integrated card.
I then tried to wake the PC from my laptop (on the same network but wireless). I tried a few of the WOL apps to wake it from within the network but no go. I had to enter MAC address (found in ipconfig/all on the PC) and usually the IP as well (the one found on whatsmyip.net). Nothing worked.

I had also been trying to do WOL from a few WOL websites that allow you to wake from any network over internet. I had opened up a port in my router firewall to forward the packets to the PCs IP Address (I forwarded my computers IP- the one found on whatsmyip.net to port 9.) I also have been messing with static IP addresses, in which I made a static server name for my machines IP address using DynDNS.com.

No settings or IP/MAC combinations make my computer wake from within the network or from the internet on one of those sites. It either just doesn't work, says the network is private, or it says you cannot wake because you are on the computer you are trying to wake. I guess that means that the laptop I'm on wireless with has the same IP address as the PC? Not sure why.

There's a ton more info I could mention from my venture but this is already too long of a post. If you need any more info from me, please just ask and I will reply immediately (Blackberry). Please help me if possible, thanks!


[I]Sidenotes[/I]:
-I chatted with Dell and they "confirmed" that this PC/mobo has WOL capabilities.
-Possibly the static server name I made is messing this up? I'm convinced that something with the IP address/static name/port forwarding/router settings is causing this.
-I used my router's DDNS feature and plugged in the server/ip name to keep it static (new to this).
-I've read a few sites saying that when trying to use WOL with a Linksys router that you should try changing the broadcast to 225.225.225.128 (instead of the default 225.225.225.0) and forward the Broadcast IP (for me then would be 192.168.1.128 to port 9 (or whichever port). I'm wary of this stuff as I'm a little inexperienced with the IP stuff, but I did my best with the forwarding settings.