Topic: what else do I need to do?

[wbtedrick]

I've set the hostaddress for a new sub domain to point to another system on our local network   (another web server which works if addressed by local IP) but the server will not make the link to the local system from the web.  I get the same webpage when either url is used. I though the SME server would pass through to the internal server but something is wrong...

the host settings are:
www.theeagleftp.com  --self  --local  (works as it should)
ftp.theeagleftp.com  --self  --local  (works as it should)
mail.theeagleftp.com  --self  --local  (works as it should)
diningguide.theeagleftp.com -- local  --local  (pointing to 172.20.83.84 on our internal network)  goes to the www.theeagleftp.com  

  I've made the DNS changes with my provider and the names resolve as they should.  Do I need to port forward the 172.20.83.84?  What am I missing here..  I have several of these SME servers setup and have done some cross checking and all respond like this.. It is almost as though the changes are not taking place anywhere else but in the control panel..  any help is deeply appreciated..

[wbtedrick]

Am I alone on this?

[McMaGnuM]

As far as I've done this you need to use portforwarding to make it work...

You could use a redirecting page on the address that should go into the internal network.

/McMaGnuM

[Anonymous]

Port forwarding would simply move ALL web traffic to the internal server.

[McMaGnuM]

You would of course have to redirect the address in question to another port than 80.....

McMaGnuM

[smeghead]

try proxypass