• May 15, 2025, 11:43:47 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: virtual server and port forwarding not working  (Read 3738 times)

dj1990

  • Level 1 Member
  • *
  • Posts: 6
virtual server and port forwarding not working
« on: September 06, 2010, 08:16:59 AM »

Hi,
I've been struggling with this for a few days now and I'm stuck. I've read the manual, searched the forum and tried a lot of things ... I'd be grateful for some help.

I have a DIR-655 running 1.34NA. I use Windows7 PCs with TW/roadrunner service.

I want one of my PCs to be a web server and I've set up everything on the LAN side and the website works on the LAN side at http://192.168.0.198:8080.

But, when I enable virtual server and set up the private/public ports, the attempted external access times out. I am trying this from a friend's house, so it is external. I'm using http://my.ip.add.ress:8080.

On the positive side, from the friend's house I can ping my router and also log in as administrator, so I know the router is alive and accessible from the internet.

Also, after I try to access the webpage externally, I look at http://192.168.0.1/Status/Internet_Sessions.shtml and there is an entry with the appropriate public and private ports with status SS ... meaning that there has been an attempt to start a session. So it seems I'm close.

I've tried both virtual server and port forwarding with the same results.

Any ideas? Thank you.

dj
Logged

dj1990

  • Level 1 Member
  • *
  • Posts: 6
Re: virtual server and port forwarding not working
« Reply #1 on: September 06, 2010, 05:34:27 PM »

So I solved it ... it was a firewall issue. I had disabled ZoneAlarm to test the connection, but I didn't realize that Windows Firewall automatically turns itself back on when ZoneAlarm quits. So, I thought I was testing the configuration without a firewall, but I wasn't. Once I punched a hole in the Windows Firewall, everything worked as it should.

Sorry for the false alarm, but maybe someone will learn from my mistake.

dj
Logged