Server 2008 TS Web Access Remote systems cannot connect from the Internet

[Guest Jon Osborn]

Please forgive I am new to TS Web access on 2008. We have installed a test

server and installed TS and IIS on it. We are looking to publish programs

to TS Web Access, have a hole poked in the fire wall to allow Internet users

to access our "site" and use their programs from home. I have TS Web access

working great on the internal network but when the same laptop is at home

and we connect to our TS Web Access server from outside the network we get

an error that states "The Remote Computer could not be found". What could

have done wrong? Do we need to open more ports for RDC? I was under the

impression we just need port 80 & 443 open.

 

 

 

Thanks,

 

Jon

[Guest Jeff Pitsch]

Re: Server 2008 TS Web Access Remote systems cannot connect from the Internet

 

You need TSGateway installed as well. Otherwise you will only get the

internal address returned. TSGateway acts as a middleman between the

internal servers and the external client. TSWeb does not. install

TSGateway and configure that for external access.

 

--

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"Jon Osborn" <josborn@pcsii.com> wrote in message

news:uwuhxsTDJHA.2060@TK2MSFTNGP05.phx.gbl...

>

>

> Please forgive I am new to TS Web access on 2008. We have installed a

> test server and installed TS and IIS on it. We are looking to publish

> programs to TS Web Access, have a hole poked in the fire wall to allow

> Internet users to access our "site" and use their programs from home. I

> have TS Web access working great on the internal network but when the same

> laptop is at home and we connect to our TS Web Access server from outside

> the network we get an error that states "The Remote Computer could not be

> found". What could have done wrong? Do we need to open more ports for

> RDC? I was under the impression we just need port 80 & 443 open.

>

>

>

> Thanks,

>

> Jon

>

>

>

[Guest Jon Osborn]

Re: Server 2008 TS Web Access Remote systems cannot connect from the Internet

 

I do have TSGateway installed and with a Self-Signed Certificate. I went

thought the TSG Checklist and I am pretty sure I did everything correct. Is

the anything specific I need to check on? Log files?

 

Thanks,

Jon

 

 

"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

news:OOmU4FVDJHA.4176@TK2MSFTNGP04.phx.gbl...

> You need TSGateway installed as well. Otherwise you will only get the

> internal address returned. TSGateway acts as a middleman between the

> internal servers and the external client. TSWeb does not. install

> TSGateway and configure that for external access.

>

> --

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

> "Jon Osborn" <josborn@pcsii.com> wrote in message

> news:uwuhxsTDJHA.2060@TK2MSFTNGP05.phx.gbl...

>>

>>

>> Please forgive I am new to TS Web access on 2008. We have installed a

>> test server and installed TS and IIS on it. We are looking to publish

>> programs to TS Web Access, have a hole poked in the fire wall to allow

>> Internet users to access our "site" and use their programs from home. I

>> have TS Web access working great on the internal network but when the

>> same laptop is at home and we connect to our TS Web Access server from

>> outside the network we get an error that states "The Remote Computer

>> could not be found". What could have done wrong? Do we need to open

>> more ports for RDC? I was under the impression we just need port 80 &

>> 443 open.

>>

>>

>>

>> Thanks,

>>

>> Jon

>>

>>

>>

>

>

[Guest Jeff Pitsch]

Re: Server 2008 TS Web Access Remote systems cannot connect from the Internet

 

Ok, I didn't see anything in your original post specifying TSGateway.

 

Are you coming in over port 80 or port 443 to the TSGateway? When coming in

externally you should never need port 80 open. If you are coming in over

port 80, try https instead.

 

--

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"Jon Osborn" <josborn@pcsii.com> wrote in message

news:uOHt7heDJHA.3908@TK2MSFTNGP04.phx.gbl...

>I do have TSGateway installed and with a Self-Signed Certificate. I went

>thought the TSG Checklist and I am pretty sure I did everything correct.

>Is the anything specific I need to check on? Log files?

>

> Thanks,

> Jon

>

>

> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

> news:OOmU4FVDJHA.4176@TK2MSFTNGP04.phx.gbl...

>> You need TSGateway installed as well. Otherwise you will only get the

>> internal address returned. TSGateway acts as a middleman between the

>> internal servers and the external client. TSWeb does not. install

>> TSGateway and configure that for external access.

>>

>> --

>> Jeff Pitsch

>> Microsoft MVP - Terminal Services

>>

>> "Jon Osborn" <josborn@pcsii.com> wrote in message

>> news:uwuhxsTDJHA.2060@TK2MSFTNGP05.phx.gbl...

>>>

>>>

>>> Please forgive I am new to TS Web access on 2008. We have installed a

>>> test server and installed TS and IIS on it. We are looking to publish

>>> programs to TS Web Access, have a hole poked in the fire wall to allow

>>> Internet users to access our "site" and use their programs from home. I

>>> have TS Web access working great on the internal network but when the

>>> same laptop is at home and we connect to our TS Web Access server from

>>> outside the network we get an error that states "The Remote Computer

>>> could not be found". What could have done wrong? Do we need to open

>>> more ports for RDC? I was under the impression we just need port 80 &

>>> 443 open.

>>>

>>>

>>>

>>> Thanks,

>>>

>>> Jon

>>>

>>>

>>>

>>

>>

>

>

[Guest Jon Osborn]

Re: Server 2008 TS Web Access Remote systems cannot connect from the Internet

 

I tryied both and I get the same error.

 

Thanks

 

"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

news:eQGXJ4eDJHA.4816@TK2MSFTNGP06.phx.gbl...

> Ok, I didn't see anything in your original post specifying TSGateway.

>

> Are you coming in over port 80 or port 443 to the TSGateway? When coming

> in externally you should never need port 80 open. If you are coming in

> over port 80, try https instead.

>

> --

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

> "Jon Osborn" <josborn@pcsii.com> wrote in message

> news:uOHt7heDJHA.3908@TK2MSFTNGP04.phx.gbl...

>>I do have TSGateway installed and with a Self-Signed Certificate. I went

>>thought the TSG Checklist and I am pretty sure I did everything correct.

>>Is the anything specific I need to check on? Log files?

>>

>> Thanks,

>> Jon

>>

>>

>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

>> news:OOmU4FVDJHA.4176@TK2MSFTNGP04.phx.gbl...

>>> You need TSGateway installed as well. Otherwise you will only get the

>>> internal address returned. TSGateway acts as a middleman between the

>>> internal servers and the external client. TSWeb does not. install

>>> TSGateway and configure that for external access.

>>>

>>> --

>>> Jeff Pitsch

>>> Microsoft MVP - Terminal Services

>>>

>>> "Jon Osborn" <josborn@pcsii.com> wrote in message

>>> news:uwuhxsTDJHA.2060@TK2MSFTNGP05.phx.gbl...

>>>>

>>>>

>>>> Please forgive I am new to TS Web access on 2008. We have installed a

>>>> test server and installed TS and IIS on it. We are looking to publish

>>>> programs to TS Web Access, have a hole poked in the fire wall to allow

>>>> Internet users to access our "site" and use their programs from home.

>>>> I have TS Web access working great on the internal network but when the

>>>> same laptop is at home and we connect to our TS Web Access server from

>>>> outside the network we get an error that states "The Remote Computer

>>>> could not be found". What could have done wrong? Do we need to open

>>>> more ports for RDC? I was under the impression we just need port 80 &

>>>> 443 open.

>>>>

>>>>

>>>>

>>>> Thanks,

>>>>

>>>> Jon

>>>>

>>>>

>>>>

>>>

>>>

>>

>>

>

>

[Guest slj333]

Re: Server 2008 TS Web Access Remote systems cannot connect from

 

Re: Server 2008 TS Web Access Remote systems cannot connect from

 

Jon,

When you try to connect remotely, does the TS Web Access page load and can

you log in?

Is your firewall set to Nat on port 443 from your public ip to the TS 2008

box's private ip, and on port 80 from the public ip to the private? Does your

ts 2008 box resolve dns to the same name internally as well as externally??

e.g. ts.mycompany.com resolves on outside to public ip and inside to private

ip?

 

steve

 

"Jon Osborn" wrote:

> I tryied both and I get the same error.

>

> Thanks

>

> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

> news:eQGXJ4eDJHA.4816@TK2MSFTNGP06.phx.gbl...

> > Ok, I didn't see anything in your original post specifying TSGateway.

> >

> > Are you coming in over port 80 or port 443 to the TSGateway? When coming

> > in externally you should never need port 80 open. If you are coming in

> > over port 80, try https instead.

> >

> > --

> > Jeff Pitsch

> > Microsoft MVP - Terminal Services

> >

> > "Jon Osborn" <josborn@pcsii.com> wrote in message

> > news:uOHt7heDJHA.3908@TK2MSFTNGP04.phx.gbl...

> >>I do have TSGateway installed and with a Self-Signed Certificate. I went

> >>thought the TSG Checklist and I am pretty sure I did everything correct.

> >>Is the anything specific I need to check on? Log files?

> >>

> >> Thanks,

> >> Jon

> >>

> >>

> >> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

> >> news:OOmU4FVDJHA.4176@TK2MSFTNGP04.phx.gbl...

> >>> You need TSGateway installed as well. Otherwise you will only get the

> >>> internal address returned. TSGateway acts as a middleman between the

> >>> internal servers and the external client. TSWeb does not. install

> >>> TSGateway and configure that for external access.

> >>>

> >>> --

> >>> Jeff Pitsch

> >>> Microsoft MVP - Terminal Services

> >>>

> >>> "Jon Osborn" <josborn@pcsii.com> wrote in message

> >>> news:uwuhxsTDJHA.2060@TK2MSFTNGP05.phx.gbl...

> >>>>

> >>>>

> >>>> Please forgive I am new to TS Web access on 2008. We have installed a

> >>>> test server and installed TS and IIS on it. We are looking to publish

> >>>> programs to TS Web Access, have a hole poked in the fire wall to allow

> >>>> Internet users to access our "site" and use their programs from home.

> >>>> I have TS Web access working great on the internal network but when the

> >>>> same laptop is at home and we connect to our TS Web Access server from

> >>>> outside the network we get an error that states "The Remote Computer

> >>>> could not be found". What could have done wrong? Do we need to open

> >>>> more ports for RDC? I was under the impression we just need port 80 &

> >>>> 443 open.

> >>>>

> >>>>

> >>>>

> >>>> Thanks,

> >>>>

> >>>> Jon

> >>>>

> >>>>

> >>>>

> >>>

> >>>

> >>

> >>

> >

> >

>

>

>

[Guest Ken Lulue]

Ports open

 

Ports open

 

do you have 3389 open to the server as well? The way I understand it, you are still using terminal services, so you need that port open as well.

[Guest slj333]

RE: Ports open

 

RE: Ports open

 

No, you do not need to open port 3389 to the outside as long as you are using

TS Gateway.

 

"Ken Lulue" wrote:

> do you have 3389 open to the server as well? The way I understand it, you are still using terminal services, so you need that port open as well.

>