RDP not Connecting from External Requests

[Guest David]

Utterly confused.

 

I have a Win2003SBS R2 and a Win2003Std R2 with a TS role connected on their

LAN adaptors (SBS 192.168.16.2 and Std .5) each with an internet connection

(SBS - 10.0.0.2 : Std on 172.16.0.100).

 

I can make a connection from a LAN PC using 172.16.0.100 & 192.168.16.5 but

I cannot connect from an external client. Wireshark reports incoming traffic

on 3389 when initiating an external request and I can see traffic on 80 when

I try to telnet. No outgoing traffic is generated from the TS server in

response. I can browse to the web so port 80 outgoing is functioning.

 

The TS logs show successful logon attempts from LAN clients but no entries

for remote failures.

 

I have not yet been able to activate TS licensing as the SP2 CD for the SBS

has been misplaced but I am still 175+ days within the grace period.

 

What is spectacularly irritating is that it was working yesterday - and

please don't ask what I changed because I didn't!

--

David @ Solsletta

[Guest Bart Van Vugt]

RE: RDP not Connecting from External Requests

 

Is your default gateway set correct?

 

"David" wrote:

> Utterly confused.

>

> I have a Win2003SBS R2 and a Win2003Std R2 with a TS role connected on their

> LAN adaptors (SBS 192.168.16.2 and Std .5) each with an internet connection

> (SBS - 10.0.0.2 : Std on 172.16.0.100).

>

> I can make a connection from a LAN PC using 172.16.0.100 & 192.168.16.5 but

> I cannot connect from an external client. Wireshark reports incoming traffic

> on 3389 when initiating an external request and I can see traffic on 80 when

> I try to telnet. No outgoing traffic is generated from the TS server in

> response. I can browse to the web so port 80 outgoing is functioning.

>

> The TS logs show successful logon attempts from LAN clients but no entries

> for remote failures.

>

> I have not yet been able to activate TS licensing as the SP2 CD for the SBS

> has been misplaced but I am still 175+ days within the grace period.

>

> What is spectacularly irritating is that it was working yesterday - and

> please don't ask what I changed because I didn't!

> --

> David @ Solsletta

[Guest David]

RE: RDP not Connecting from External Requests

 

Thanks for the response. It's set to 172.16.0.1 the router IP.

--

David @ Solsletta

 

 

"Bart Van Vugt" wrote:

> Is your default gateway set correct?

>

> "David" wrote:

>

> > Utterly confused.

> >

> > I have a Win2003SBS R2 and a Win2003Std R2 with a TS role connected on their

> > LAN adaptors (SBS 192.168.16.2 and Std .5) each with an internet connection

> > (SBS - 10.0.0.2 : Std on 172.16.0.100).

> >

> > I can make a connection from a LAN PC using 172.16.0.100 & 192.168.16.5 but

> > I cannot connect from an external client. Wireshark reports incoming traffic

> > on 3389 when initiating an external request and I can see traffic on 80 when

> > I try to telnet. No outgoing traffic is generated from the TS server in

> > response. I can browse to the web so port 80 outgoing is functioning.

> >

> > The TS logs show successful logon attempts from LAN clients but no entries

> > for remote failures.

> >

> > I have not yet been able to activate TS licensing as the SP2 CD for the SBS

> > has been misplaced but I am still 175+ days within the grace period.

> >

> > What is spectacularly irritating is that it was working yesterday - and

> > please don't ask what I changed because I didn't!

> > --

> > David @ Solsletta

[Guest David]

RE: RDP not Connecting from External Requests

 

It turns out to be a gateway error - thanks. The gateway on 172.16.0.100 was

set to 172.16.0.1 - correct. The gateway on 192.168.16.5 was set to

192.168.16.1. The TS server was receiving requests on 172. but replying on

192. - the SBS on 192. did not recognise the traffic and discarded it so it

didn't reach the router. Wrong path anyway. Unfotunately MS Business

Critical couldn't find it but Cisco did.

--

David @ Solsletta

 

 

"Bart Van Vugt" wrote:

> Is your default gateway set correct?

>

> "David" wrote:

>

> > Utterly confused.

> >

> > I have a Win2003SBS R2 and a Win2003Std R2 with a TS role connected on their

> > LAN adaptors (SBS 192.168.16.2 and Std .5) each with an internet connection

> > (SBS - 10.0.0.2 : Std on 172.16.0.100).

> >

> > I can make a connection from a LAN PC using 172.16.0.100 & 192.168.16.5 but

> > I cannot connect from an external client. Wireshark reports incoming traffic

> > on 3389 when initiating an external request and I can see traffic on 80 when

> > I try to telnet. No outgoing traffic is generated from the TS server in

> > response. I can browse to the web so port 80 outgoing is functioning.

> >

> > The TS logs show successful logon attempts from LAN clients but no entries

> > for remote failures.

> >

> > I have not yet been able to activate TS licensing as the SP2 CD for the SBS

> > has been misplaced but I am still 175+ days within the grace period.

> >

> > What is spectacularly irritating is that it was working yesterday - and

> > please don't ask what I changed because I didn't!

> > --

> > David @ Solsletta