Weird Issue connecting to TS

[Guest steves100@hotmail.com]

I have a client with a weird issue trying to connect to TS from a remote

office.

 

They have a persistant VPN tunnel running using their router. The tunnel

is up and active, can ping the server.

 

When they try to use remote desktop connect, they never get a log in box.

either using IP or name (it was working last week). But, they can connect

to the PDC using remote desktop. 192.168.10.2 works, 192.168.10.3 does

not resolve.

 

You can connect from anywhere else, I have tested local network and VPN

from anywhere but remote office. No issue.

 

They have reset all the networking components, nothing. Ping yes, remote

desktop no.

 

Anyhelp would be appreciated.

[Guest Nitin K]

RE: Weird Issue connecting to TS

 

Does telnet 192.168.10.3 3389 (assuming the default TS port on the machine in

question is not changed!) work from that remote client?

 

At your remote office, do all servers/clients experience an issue while

accessing 192.168.10.3 via RDP?

 

"steves100@hotmail.com" wrote:

> I have a client with a weird issue trying to connect to TS from a remote

> office.

>

> They have a persistant VPN tunnel running using their router. The tunnel

> is up and active, can ping the server.

>

> When they try to use remote desktop connect, they never get a log in box.

> either using IP or name (it was working last week). But, they can connect

> to the PDC using remote desktop. 192.168.10.2 works, 192.168.10.3 does

> not resolve.

>

> You can connect from anywhere else, I have tested local network and VPN

> from anywhere but remote office. No issue.

>

> They have reset all the networking components, nothing. Ping yes, remote

> desktop no.

>

> Anyhelp would be appreciated.

[Guest steves100@hotmail.com]

RE: Weird Issue connecting to TS

 

Yes all the workstations are having the same issues.

 

I just tried to telent to port 3389 from my laptop with a good vpn session.

 

I tried to telnet from my laptop with a good connection from home, is it

correct to get a clear screen? I'll try from the remote office later.

 

Steve

 

"Nitin K" wrote:

> Does telnet 192.168.10.3 3389 (assuming the default TS port on the machine in

> question is not changed!) work from that remote client?

>

> At your remote office, do all servers/clients experience an issue while

> accessing 192.168.10.3 via RDP?

>

> "steves100@hotmail.com" wrote:

>

> > I have a client with a weird issue trying to connect to TS from a remote

> > office.

> >

> > They have a persistant VPN tunnel running using their router. The tunnel

> > is up and active, can ping the server.

> >

> > When they try to use remote desktop connect, they never get a log in box.

> > either using IP or name (it was working last week). But, they can connect

> > to the PDC using remote desktop. 192.168.10.2 works, 192.168.10.3 does

> > not resolve.

> >

> > You can connect from anywhere else, I have tested local network and VPN

> > from anywhere but remote office. No issue.

> >

> > They have reset all the networking components, nothing. Ping yes, remote

> > desktop no.

> >

> > Anyhelp would be appreciated.

[Guest Nitin K]

RE: Weird Issue connecting to TS

 

Yes.

 

You should get a clear screen with a cursor blinking.

 

Now you know how it looks when you telnet from a working machine...

 

if the same doesn't happen from the ones in question, it indicates that the

port 3389 is blocked and/or outgoing traffic on that port is not allowed at a

firewall/router on the remote site.

 

Does the remote site have ISA server installed? if yes do check for the

existence of the appropriate rule for outbound traffic on port 3389!

 

"steves100@hotmail.com" wrote:

> Yes all the workstations are having the same issues.

>

> I just tried to telent to port 3389 from my laptop with a good vpn session.

>

> I tried to telnet from my laptop with a good connection from home, is it

> correct to get a clear screen? I'll try from the remote office later.

>

> Steve

>

> "Nitin K" wrote:

>

> > Does telnet 192.168.10.3 3389 (assuming the default TS port on the machine in

> > question is not changed!) work from that remote client?

> >

> > At your remote office, do all servers/clients experience an issue while

> > accessing 192.168.10.3 via RDP?

> >

> > "steves100@hotmail.com" wrote:

> >

> > > I have a client with a weird issue trying to connect to TS from a remote

> > > office.

> > >

> > > They have a persistant VPN tunnel running using their router. The tunnel

> > > is up and active, can ping the server.

> > >

> > > When they try to use remote desktop connect, they never get a log in box.

> > > either using IP or name (it was working last week). But, they can connect

> > > to the PDC using remote desktop. 192.168.10.2 works, 192.168.10.3 does

> > > not resolve.

> > >

> > > You can connect from anywhere else, I have tested local network and VPN

> > > from anywhere but remote office. No issue.

> > >

> > > They have reset all the networking components, nothing. Ping yes, remote

> > > desktop no.

> > >

> > > Anyhelp would be appreciated.