Forwarding external port to a internal port - blanking out

M

marley1

Supreme [H]ardness
Joined
Jul 18, 2000
Messages
5,447
Hey guys, I am blanking out on this, one of my smaller clients just got some door access controllers installed, these are all ip based.

currently they are going internally to:
https://192.168.1.20
https://192.168.1.21
https://192.168.1.22

then they can access the door they want, they now want to access these externally.

i have done this before on older routers by doing a virtual server and having say port 8443 external go to 443 internal for 192.168.1.20, and say 8444 external to go to 443 internal for 192.168.1.21, etc.

i am using a D-Link DIR-655 and when i set that up, for https://wanip:8443, it prompts me for the certificate error, i click continue to website and its blank.

when i do a straight port forward, external 443 to internal 443, and 192.168.1.20, and go to https://wanip, i get the certificate error, click continue and I am working.

I know sometimes with these D-Links you gotta do some other tweaking but I am blanking out.

Any ideas?

Thanks!
 
Maybe 8443 is defaulting to something internal on the DStink...try a different external port like 8881 and remap to 443 internal.
 
same thing, it loads the certificate then just stops, any other ideas?
 
yeah these things are great for wireless, but i have had pain in ass time getting some port fowards or vpn going. may swap it out for a wrt54gl with tomato or something
 
swapped to a tomato based Buffalo unit, same thing...

it should be able to work no?
 
You must log in or register to reply here.
Back
Top