Digital Subscriber Line Remote Desktop: One Way, But Not The Other?

Bookmark this page:  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Remote Desktop: One Way, But Not The Other? (PeteCresswell) 12-01-07
Posted by (PeteCresswell) on December 1, 2007, 8:54 am
Please log in for more thread options
I'm on a router connected to Verizon's FIOS.

The other person's PC is connected directly to a Verizon DSL
modem.

If I issue a Remote Assistance invitation to the other PC, it can
get to my desktop: no problem.

OTOH, if they issue an invitation to me, I'm unable to connect to
their desktop.

All the appropriate checkboxes seem tb checked.

I'm wondering it if might be something connected with the other
PC not being behind a router.

?
--
PeteCresswell

Posted by Robert Redelmeier on December 1, 2007, 9:42 am
Please log in for more thread options
> I'm on a router connected to Verizon's FIOS.
>
> The other person's PC is connected directly to a Verizon DSL
> modem.
>
> If I issue a Remote Assistance invitation to the other PC, it can
> get to my desktop: no problem.
>
> OTOH, if they issue an invitation to me, I'm unable to connect to
> their desktop.
>
> All the appropriate checkboxes seem tb checked.
>
> I'm wondering it if might be something connected with the other
> PC not being behind a router.


Exactly. Your router also acts like a firewall and rejects _all_
incoming packets _except_ those from an established TCP session.
These TCP sessions are established by outbound requests.

Obviously a big security win.

You can allow some packets inbound according to your router
configuration pages. Usually under "servers" or "port forwarding".
Make sure the servers on those ports do not have vulnerabilities.

-- Robert



Posted by (PeteCresswell) on December 1, 2007, 1:51 pm
Please log in for more thread options
Per Robert Redelmeier:
>Exactly. Your router also acts like a firewall and rejects _all_
>incoming packets _except_ those from an established TCP session.
>These TCP sessions are established by outbound requests.
>
>Obviously a big security win.
>
>You can allow some packets inbound according to your router
>configuration pages. Usually under "servers" or "port forwarding".
>Make sure the servers on those ports do not have vulnerabilities.

Most of that is going right over my head.

But at a gross level, it sounds backwards - like my PC sb the one
resistant to allowing access by the other one instead of the way
it is - which is that the other PC won't allow mine to access it.

Also, somewhere under Assistance Request it seems to assert that
it takes card of Windows Firewall automagically. Of course, no
mention is made of the router..... so maybe we're back to my not
fully understanding what you said above.
--
PeteCresswell

Posted by Robert Redelmeier on December 2, 2007, 9:08 am
Please log in for more thread options
> But at a gross level, it sounds backwards - like my PC sb the one
> resistant to allowing access by the other one instead of the way
> it is - which is that the other PC won't allow mine to access it.

No, your PC isn't resisting access. Your hardware firewall will
not allow the request in because it started from outside. It
only allows data in that is on a connection started from the inside.

> Also, somewhere under Assistance Request it seems to assert that
> it takes card of Windows Firewall automagically.

MS-Windows firewall is a software appendage onto the MS-Windows OS.
It can certainly be programmed to pass RA. But how will your
external router (a small computer) know anything about MS-RA?
It just shovels packets.

-- Robert


Posted by (PeteCresswell) on December 2, 2007, 9:48 am
Please log in for more thread options
Per Robert Redelmeier:
>No, your PC isn't resisting access. Your hardware firewall will
>not allow the request in because it started from outside. It
>only allows data in that is on a connection started from the inside.

But it's the *other* end that has the problem. My PC allows
access. The other end, however, resists access - and it is not
behind a router, unless the DSL modem counts as such.
--
PeteCresswell

Similar ThreadsPosted
Remote Desktop: One Way, But Not The Other? December 1, 2007, 8:54 am
Still can't access remote admin on D-Link DI-804 July 12, 2004, 1:33 am
Help remote server will only accept access from static IP December 17, 2006, 2:06 am
DSL Speeds (Desktop vs Laptop) November 2, 2005, 1:17 am