Forwarding ports to internal server

Hello all,

First, I would like to thank you all in advanced for any help you may
provide; now on to the issue I am having.

I am running Server 2008, using it to host a virtual machine, configured as
a web server. I am unable to forwarded incoming connections to port 80
(HTTP) to the IP address of the internal server. I have been able to do
similar in Server 2003, but for some odd reason I am unable to do so now.

Can anyone instruct me or point me in the right direction here.

Host Sever is running Server 2008 with a single IP Address
The Guest server is running Server 2003 with a non routable IP Address.

The host server can ping the internal server, and connect to the HTTP site
w/o issue.

Thanks Again
Mr. Smtih

Where did you configure port forwarding? Do you have a router?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Mr. Smith" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello all,
>
> First, I would like to thank you all in advanced for any help you may
> provide; now on to the issue I am having.
>
> I am running Server 2008, using it to host a virtual machine, configured
> as a web server. I am unable to forwarded incoming connections to port 80
> (HTTP) to the IP address of the internal server. I have been able to do
> similar in Server 2003, but for some odd reason I am unable to do so now.
>
> Can anyone instruct me or point me in the right direction here.
>
> Host Sever is running Server 2008 with a single IP Address
> The Guest server is running Server 2003 with a non routable IP Address.
>
> The host server can ping the internal server, and connect to the HTTP site
> w/o issue.
>
> Thanks Again
> Mr. Smtih

The server is an edge server and has a single public IP Address. I am
running a virtual machine as a guest on this server, that I would like
remote users to connect to. Although I am using VMware Server to run my
virtual machine, the principle is still the same as if I was to run this in
hypervisor


*UPDATE*
I was unable to find a way to do this in Server 2008, even attempting to use
Routing and Remote Access and use its port forwarding capabilities failed.
I was however able to find a solution in VMware Server's Virtual Network
Editor.

1. Opening Virtual Network Editor
2. Select the NAT tab
3. Stop The NAT Service from here
4. Click Edit - This takes you to the NAT Settings for your VM Network
5. Click Port Forwarding
6. Click Add - here you can choose to add the TCP or UDP port on the host
and map it back to your guest virtual machine.
7. Click OK, then OK again, and on the Virtual Network Editor , start the
NAT Service


While this has solved my issue, it does not offer me a solution of how do I
forward ports from my external interface to an internal IP Address on Server
2008.






"Robert L. (MS-MVP)" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Where did you configure port forwarding? Do you have a router?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Mr. Smith" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hello all,
>>
>> First, I would like to thank you all in advanced for any help you may
>> provide; now on to the issue I am having.
>>
>> I am running Server 2008, using it to host a virtual machine, configured
>> as a web server. I am unable to forwarded incoming connections to port
>> 80 (HTTP) to the IP address of the internal server. I have been able to
>> do similar in Server 2003, but for some odd reason I am unable to do so
>> now.
>>
>> Can anyone instruct me or point me in the right direction here.
>>
>> Host Sever is running Server 2008 with a single IP Address
>> The Guest server is running Server 2003 with a non routable IP Address.
>>
>> The host server can ping the internal server, and connect to the HTTP
>> site w/o issue.
>>
>> Thanks Again
>> Mr. Smtih
>