I have a dlink DI-524. I am running a webserver on port 81. I had the fucking virtual server working for weeks, and now all of a sudden it does not work.

I have no personal firewall, i have winxp sp2 firewall disabled. If I connect my pc directly to cable modem everything works fine (webserver serves pages). I connect my router (with my pc connected 192.168.0.1 - static (assigned by mac add so will never change)) and i get connection refused. Dlink sucks fat hairy nutsack and doesnt keep logs (or at least from what i can find) of what firewall is doing.

I have tried the port fwding using dlinks stupid virtual server and also by settin the computer with webserver in DMZ. No success. Upgraded firmware. And like I said all the shit was working perfectly for weeks. Oh yea and i have this cable modem: http://www.ambitbroadband.com/broadband/U10C018.php
I checked to see if it has a firewall too, it does not.

Thought it could be some loopback issue or something, but had friend try to connect from outside my lan.

any ideas? anyone ran into this before? been at it for a while and am bout to giveup

11/8/2005 11:43:55 PM

[Edited on November 9, 2005 at 12:31 AM. Reason : nm]

11/9/2005 12:28:02 AM

Your router by default uses 192.168.0.1

Your PC can't use this address as well.

11/10/2005 3:41:06 AM

Since you are using a private IP range anyhow, set all your statics in the .10-99 range and start your dhcp pool at .100 or something similiar.

11/10/2005 6:06:53 AM

^oops yea i had a typo there. My gateway is 192.168.0.1. The computer running the http/ftp virtual server is statically assigned 192.168.0.100 based on its mac address.

11/11/2005 5:25:41 AM