apache and d-link 524 router ...

hello,

recently fried a network everywhere wireless router with a firmware
upgrade. bought a d-link 524 wireless router and i can no longer access
my server from the wan. terminology differs between routers, i simply
set up a virtual server at port 80, gave the private ip etc, basically
used their template and added the private ip address. sounds pretty
straight forward reading their instructions (which are awful!) but
nothing seems to work. do i use dmz, any special firewall settings - it
automatically allowed server connections to the box i entered in virtual
server. any new apache setting? i'm basically a desktop user who keeps
it as simple as possible. everything worked fine with the old router and
default apache settings. using dyndns for the domain name. this worked
too with the other router. there's a dyndns setting in the d-link which
i don't understand at all. i have a feeling this is pretty simple to do
if i could get it in plain english.

thanks for your patience.

try typing in your public http://xxx.xxx.xxx.xxx and see what happens.
If you get to your site you are having issues with your DDNS. If not it
is probably still something with the router.

(E-Mail Removed) wrote:
> try typing in your public http://xxx.xxx.xxx.xxx and see what happens.
> If you get to your site you are having issues with your DDNS. If not it
> is probably still something with the router.
>

sorry i forgot to mention i did that, got my dynamic ip no. from the
router then typed that in the browser - still didn't work. i'm going to
call d-link tech tomorrow but i'm not expecting much help. thanks for
the reply.

The only other thing I could think of would server permissions hitting
the web server.

you should be able to ping your dydns address and it should resolve to
your public IP address if the dns is working properly.

jcw248 wrote:
> you should be able to ping your dydns address and it should resolve to
> your public IP address if the dns is working properly.
>

talked to D-Link today, apparently it's a security risk (they say) to be
able to access my server from the public ip/domain name. they were able
to access the server and so was a friend. so, i guess that's all there
is to it. my old network everywhere router used to let me do it. thanks
for the help.