GW, If you're trying to access the web server from the 192.168.1.x network, your client's browser should simply point to http://192.168.1.244. It should not point to the 192.168.10.45:81 location because the traffic never reaches the router.
John Go Wow wrote: > Yeah I can view my inside internal webserver through my router using > NAT, what I cant do is to view the same webserver from internal lan. > If I want to view it I have to issue its internal ip and I cant go > through the router. > > My eth0 >> 192.168.10.45 <http://192.168.10.45> (acting as WAN) > My eth1 >> 192.168.1.1 <http://192.168.1.1> (My Internal Network) > My Webserver >> 192.168.1.244 <http://192.168.1.244> > > From any system which is not a part of my vyatta router if I put in > the address 192.168.10.45:81 <http://192.168.10.45:81> I'm getting > redirected to 192.168.1.244:80 <http://192.168.1.244:80> which is my > webserver, so far so good. But when I type in the address > 192.168.10.45:81 <http://192.168.10.45:81> from one of my internal LAN > system it throws back the "unable to connect error" error how do I get > it fixed? > ------------------------------------------------------------------------ > > _______________________________________________ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
