Re: Remote Desktop doesn't work outside of my network...

From: Travis (Travis_at_discussions.microsoft.com)
Date: 07/31/04


Date: Sat, 31 Jul 2004 16:50:57 -0700

I am having a very similar problem. I was able to use RDC
for awhile and then recently I get to the login screen
and login. My desktop begins to load and then the host
computer displays "Closing Network Connections" and RDC
closes. Just like Jake it works from other internal LAN
computers fine, but not out of network even though it did
until recently. Thanks in advance for your help!

>-----Original Message-----
>That's a new error.... :(
>
>Hmm.. Let me think.
>
>Jeffrey Randow (Windows Networking & Smart Display MVP)
>jeffreyr-support@remotenetworktechnology.com
>
>Please post all responses to the newsgroups for the
benefit
>of all USENET users. Messages sent via email may or may
not
>be answered depending on time availability....
>
>Remote Networking Technology Support Site -
>http://www.remotenetworktechnology.com
>Windows XP Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
>
>On Wed, 7 Jul 2004 19:48:02 -0700, "Jake"
><Jake@discussions.microsoft.com> wrote:
>
>>Jeffrey:
>>
>>Thanks for responding to my post.
>>
>>To answer your question, I was able to remote connect
to my desktop from several different computers within my
LAN. When trying to remote from outside the LAN using
comcast internet from three different locations (two
coworkers and myself, all connected to the internet via
comcast) the same thing happens: user name, password,
enter, screen freezes for thirty seconds or so and then
the RDC program closes. I checked the DNS and Wins
settings on the desktop and there is nothing out of the
ordinary...I am stumped.
>>
>>Anyone have any experience with this?
>>
>>"Jeffrey Randow (MVP)" wrote:
>>
>>> What happens if someone logs onto your desktop from
inside the LAN?
>>> It shouldn't behave differently... The error you are
seeing means
>>> that (more than likely) your DNS and/or WINS settings
on the desktop
>>> are not configured properly and that you can't find a
DC for your
>>> domain.
>>>
>>> Jeffrey Randow (Windows Networking & Smart Display
MVP)
>>> jeffreyr-support@remotenetworktechnology.com
>>>
>>> Please post all responses to the newsgroups for the
benefit
>>> of all USENET users. Messages sent via email may or
may not
>>> be answered depending on time availability....
>>>
>>> Remote Networking Technology Support Site -
>>> http://www.remotenetworktechnology.com
>>> Windows XP Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
>>>
>>> On Fri, 25 Jun 2004 20:20:01 -0700, "Jake"
>>> <Jake@discussions.microsoft.com> wrote:
>>>
>>> >I can use remote desktop to my computer at work from
within my company's network but not outside of it. My
computer at work is configured for firewall passage. I
can remote to other computers within my company's network
from outside of the network. Other computer's outside of
my company's network cannot access my work computer
either. I get the login screen, enter my username and
password and after I press enter the screen freezes for
about 30seconds and then closes. The event view error is
as follows: "Windows cannot obtain the domain controller
name for your computer network. (A socket was attempted
to an unreachable host.). Group Policy processing
aborted." Event ID: 1054.
>>> >
>>> >I have read some fixes others have put out but not
sure which on to take. My work computer is a compaq
running XP Pro.
>>> >
>>> >Any suggestions?
>>>
>>>
>
>.
>



Relevant Pages

  • Re: Installing multiple SBS VPN clients
    ... please check the Local area network routing only. ... reachable from the remote access server. ... Check to ensure the SBS Server is using a static IP address on its LAN ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: How Can I Allow Access From The Internet to Only Selected Users?
    ... big the lan is. ... for some users on my network for years. ... When the systems box opens,click the tab that says remote. ... "select remote users" and enter in th administrators group. ...
    (microsoft.public.windows.terminal_services)
  • Re: Easiest way to access workstation remotely (Win XP)
    ... Depending on where your at, ie. a remote corporate site for example, its possible the network administrators may block TCP Port 3389 (Remote Desktop) outbound as a security measure, ie. they don't want users to connect an untrusted system like their home PCs to the work trusted system. ... PCAnyWhere is just like Remote Desktop [RDC] except RDC is built-into XP and is *FREE*. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop Connection - Client could not connect...
    ... To test from a PC on your LAN to another PC on your LAN you can *NOT* use the public IP, ... To call from the remote site use the public IP of the router, ... well for me when I call my home network using Remote Desktop. ... >>> Remote Connection might not be... ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Users (VPN) cant access Shares
    ... Change the LAN scheme on your SBS network. ... something like 192.168.15.x or you have to make sure that every remote ...
    (microsoft.public.windows.server.sbs)

Loading