Prev: Normal.dot Permissions Issue
Next: Using GPO to force local profiles on a terminal server
From: Rob Leitman [MSFT] on 30 Sep 2009 15:35

"WildPacket" <WildPacket(a)discussions.microsoft.com> wrote in message
news:AC250A34-B5BC-4F8D-B02D-DBE04C82A34A(a)microsoft.com...
> Rob Thanks.
>
> "I THINK" I did. Let me run it by you .....
>
> On the TS Remoteapp Manger Properties -> Under TSGateway tab in the server
> name field I have the same name as the CN on the certificate ...???
>
> And on the Terminal Server tab in the server name field I have the same
> name
> as the CN on the certificate
>
> Is that right????

Is the radio button on "Use these TS Gateway server settings"? Did you try
unchecking "Bypass TS Gateway server for local addresses"?

Rob


From: WildPacket on 30 Sep 2009 16:18
Yes ...tried that.

There are 2 NICs in the server ...
one on wan side and one on lan side ...could this be causing issue???





"Rob Leitman [MSFT]" wrote:

>
> "WildPacket" <WildPacket(a)discussions.microsoft.com> wrote in message
> news:AC250A34-B5BC-4F8D-B02D-DBE04C82A34A(a)microsoft.com...
> > Rob Thanks.
> >
> > "I THINK" I did. Let me run it by you .....
> >
> > On the TS Remoteapp Manger Properties -> Under TSGateway tab in the server
> > name field I have the same name as the CN on the certificate ...???
> >
> > And on the Terminal Server tab in the server name field I have the same
> > name
> > as the CN on the certificate
> >
> > Is that right????
>
> Is the radio button on "Use these TS Gateway server settings"? Did you try
> unchecking "Bypass TS Gateway server for local addresses"?
>
> Rob
>
>
>
From: Rob Leitman [MSFT] on 1 Oct 2009 16:03

"WildPacket" <WildPacket(a)discussions.microsoft.com> wrote in message
news:6DB445B8-9280-468A-B5E4-F422E42A7215(a)microsoft.com...
> Yes ...tried that.
>
> There are 2 NICs in the server ...
> one on wan side and one on lan side ...could this be causing issue???

There's no reason for the client to use RDP. Can you View Source in the
browser and tell me what the RDP file in there looks like? It will be
encoded, but still readable.

Rob


From: WildPacket on 2 Oct 2009 10:28
Rob: Thanks I will look at the code and let you know.

Spent 5 hours with Microsoft tech support and they are still not able to fix
this ... will continue working again with them today ...

They seem to be concerned about the machine name not matching the CN name on
the certificate .... but they are were not 100%.

My internal machine name is:
TERMINAL001.domain.local

And CN on the cert:
Terminal.domain.com

but it works fine ....as long as the RDP is opened... so I think its nothing
to do with the names here in my situation ....








"Rob Leitman [MSFT]" wrote:

>
> "WildPacket" <WildPacket(a)discussions.microsoft.com> wrote in message
> news:6DB445B8-9280-468A-B5E4-F422E42A7215(a)microsoft.com...
> > Yes ...tried that.
> >
> > There are 2 NICs in the server ...
> > one on wan side and one on lan side ...could this be causing issue???
>
> There's no reason for the client to use RDP. Can you View Source in the
> browser and tell me what the RDP file in there looks like? It will be
> encoded, but still readable.
>
> Rob
>
>
>
From: WildPacket on 2 Oct 2009 10:30
What should be I looking for in the source code???






"Rob Leitman [MSFT]" wrote:

>
> "WildPacket" <WildPacket(a)discussions.microsoft.com> wrote in message
> news:6DB445B8-9280-468A-B5E4-F422E42A7215(a)microsoft.com...
> > Yes ...tried that.
> >
> > There are 2 NICs in the server ...
> > one on wan side and one on lan side ...could this be causing issue???
>
> There's no reason for the client to use RDP. Can you View Source in the
> browser and tell me what the RDP file in there looks like? It will be
> encoded, but still readable.
>
> Rob
>
>
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Normal.dot Permissions Issue
Next: Using GPO to force local profiles on a terminal server