Sign in with
Sign up | Sign in
Your question

Remote Desktop Question

Last response: in Windows XP
Share
August 26, 2005 5:03:09 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Let me start by saying i know almost nothing about networking. I've got two
computers connected through a linksys wrt54g router. I've been trying to
connect to a laptop running xp-pro (host) from a desktop running xp-home
(client). Both have firewalls which are configured to allow whatever from
each other. They share files and a printer and ping each other nicely. Here
is the error message I get sometimes while trying to log in:

"The client could not connect to the remote computer
Remote connections might not be enabled or the computer might be too busy to
accept new connections.
It is also possible that network problems are preventing your connection.
Please try connecting agian later. If the problem continues to occur,
contact your administrator."

Unfortunately I'm the administrator and I have no idea. I'm thinking its
either the router config. or more likely the software policing firewall on
the host (zonealarm). It still wont work with the fw disabled however. I
actually got it load halfway one time before froze up and crashed.

Can anyone give me any suggestions on how to get ths to work?
Anonymous
August 26, 2005 9:46:55 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

See this page for troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/Rem...

Make sure your calling the correct private static LAN IP for the laptop.

Its possible ZoneAlarm is causing the problem. If your using the free
version I don't believe you can configure ZA for port forwarding. You can, I
believe, configure ZA Pro for port forwarding...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"CK" <CK@discussions.microsoft.com> wrote in message
news:64DD3C39-36E7-473D-80E4-2C373F6B09C9@microsoft.com...
> Let me start by saying i know almost nothing about networking. I've got
> two
> computers connected through a linksys wrt54g router. I've been trying to
> connect to a laptop running xp-pro (host) from a desktop running xp-home
> (client). Both have firewalls which are configured to allow whatever from
> each other. They share files and a printer and ping each other nicely.
> Here
> is the error message I get sometimes while trying to log in:
>
> "The client could not connect to the remote computer
> Remote connections might not be enabled or the computer might be too busy
> to
> accept new connections.
> It is also possible that network problems are preventing your connection.
> Please try connecting agian later. If the problem continues to occur,
> contact your administrator."
>
> Unfortunately I'm the administrator and I have no idea. I'm thinking its
> either the router config. or more likely the software policing firewall on
> the host (zonealarm). It still wont work with the fw disabled however. I
> actually got it load halfway one time before froze up and crashed.
>
> Can anyone give me any suggestions on how to get ths to work?
August 26, 2005 4:04:02 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Thanks for the link. I'll check out that page and if I don't get it worked
out I'll post another reply here.
Thanks again,

"Sooner Al [MVP]" wrote:

> See this page for troubleshooting help...
>
> http://theillustratednetwork.mvps.org/RemoteDesktop/Rem...
>
> Make sure your calling the correct private static LAN IP for the laptop.
>
> Its possible ZoneAlarm is causing the problem. If your using the free
> version I don't believe you can configure ZA for port forwarding. You can, I
> believe, configure ZA Pro for port forwarding...
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
>
> "CK" <CK@discussions.microsoft.com> wrote in message
> news:64DD3C39-36E7-473D-80E4-2C373F6B09C9@microsoft.com...
> > Let me start by saying i know almost nothing about networking. I've got
> > two
> > computers connected through a linksys wrt54g router. I've been trying to
> > connect to a laptop running xp-pro (host) from a desktop running xp-home
> > (client). Both have firewalls which are configured to allow whatever from
> > each other. They share files and a printer and ping each other nicely.
> > Here
> > is the error message I get sometimes while trying to log in:
> >
> > "The client could not connect to the remote computer
> > Remote connections might not be enabled or the computer might be too busy
> > to
> > accept new connections.
> > It is also possible that network problems are preventing your connection.
> > Please try connecting agian later. If the problem continues to occur,
> > contact your administrator."
> >
> > Unfortunately I'm the administrator and I have no idea. I'm thinking its
> > either the router config. or more likely the software policing firewall on
> > the host (zonealarm). It still wont work with the fw disabled however. I
> > actually got it load halfway one time before froze up and crashed.
> >
> > Can anyone give me any suggestions on how to get ths to work?
>
>
>
Related resources
August 27, 2005 8:19:02 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I've gone through the documentation on the link you provided and I think I
have the issue narrowed down to a couple of possible things. The host is
connected wirelessly using a broadcom 802.11g chip. The event viewer logs on
the host under system show that the connection is dropped and restarted.
I've tried updating the driver using the one from windows update. Now the
client doesnt even get partially connected to the host. "The client could
not connect to the host..." Before, it would open up the RD window and show
a black screen for a while then crash with a message that the connection was
broken. There would also be an event logged under system that I mentioned
above. The zoneAlarm logs show that the connection was allowed between the
two computers so i think the problem may be some other setting on the host or
maybe the client. The client is running Norton Internet security fw that
should allow the connection.

On the client computer I have some of the gui stuff from using the network
setup wizard such that when i use the browse option on the RD connect
dialogue It wont let me browse the networks because "there are not any
terminal servers on the network" I have terminal services started on the
host and of course the allow desktop connections check box is checked.

What services need to be running in order to connect?
Is it possible to do this over wireless?

"Sooner Al [MVP]" wrote:

> See this page for troubleshooting help...
>
> http://theillustratednetwork.mvps.org/RemoteDesktop/Rem...
>
> Make sure your calling the correct private static LAN IP for the laptop.
>
> Its possible ZoneAlarm is causing the problem. If your using the free
> version I don't believe you can configure ZA for port forwarding. You can, I
> believe, configure ZA Pro for port forwarding...
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
>
> "CK" <CK@discussions.microsoft.com> wrote in message
> news:64DD3C39-36E7-473D-80E4-2C373F6B09C9@microsoft.com...
> > Let me start by saying i know almost nothing about networking. I've got
> > two
> > computers connected through a linksys wrt54g router. I've been trying to
> > connect to a laptop running xp-pro (host) from a desktop running xp-home
> > (client). Both have firewalls which are configured to allow whatever from
> > each other. They share files and a printer and ping each other nicely.
> > Here
> > is the error message I get sometimes while trying to log in:
> >
> > "The client could not connect to the remote computer
> > Remote connections might not be enabled or the computer might be too busy
> > to
> > accept new connections.
> > It is also possible that network problems are preventing your connection.
> > Please try connecting agian later. If the problem continues to occur,
> > contact your administrator."
> >
> > Unfortunately I'm the administrator and I have no idea. I'm thinking its
> > either the router config. or more likely the software policing firewall on
> > the host (zonealarm). It still wont work with the fw disabled however. I
> > actually got it load halfway one time before froze up and crashed.
> >
> > Can anyone give me any suggestions on how to get ths to work?
>
>
>
Anonymous
August 28, 2005 12:01:07 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Do you have another client that you can try to connect from? I suppose its
possible that Norton on your client is blocking the connection... I don't
use Norton so I can say for sure...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"CK" <CK@discussions.microsoft.com> wrote in message
news:20D15F4E-273C-4F04-BFE2-51C356761D40@microsoft.com...
> I've gone through the documentation on the link you provided and I think I
> have the issue narrowed down to a couple of possible things. The host is
> connected wirelessly using a broadcom 802.11g chip. The event viewer logs
> on
> the host under system show that the connection is dropped and restarted.
> I've tried updating the driver using the one from windows update. Now the
> client doesnt even get partially connected to the host. "The client could
> not connect to the host..." Before, it would open up the RD window and
> show
> a black screen for a while then crash with a message that the connection
> was
> broken. There would also be an event logged under system that I mentioned
> above. The zoneAlarm logs show that the connection was allowed between
> the
> two computers so i think the problem may be some other setting on the host
> or
> maybe the client. The client is running Norton Internet security fw that
> should allow the connection.
>
> On the client computer I have some of the gui stuff from using the network
> setup wizard such that when i use the browse option on the RD connect
> dialogue It wont let me browse the networks because "there are not any
> terminal servers on the network" I have terminal services started on the
> host and of course the allow desktop connections check box is checked.
>
> What services need to be running in order to connect?
> Is it possible to do this over wireless?
>
> "Sooner Al [MVP]" wrote:
>
>> See this page for troubleshooting help...
>>
>> http://theillustratednetwork.mvps.org/RemoteDesktop/Rem...
>>
>> Make sure your calling the correct private static LAN IP for the laptop.
>>
>> Its possible ZoneAlarm is causing the problem. If your using the free
>> version I don't believe you can configure ZA for port forwarding. You
>> can, I
>> believe, configure ZA Pro for port forwarding...
>>
>> --
>>
>> Al Jarvi (MS-MVP Windows Networking)
>>
>> Please post *ALL* questions and replies to the news group for the mutual
>> benefit of all of us...
>> The MS-MVP Program - http://mvp.support.microsoft.com
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights...
>>
>>
>> "CK" <CK@discussions.microsoft.com> wrote in message
>> news:64DD3C39-36E7-473D-80E4-2C373F6B09C9@microsoft.com...
>> > Let me start by saying i know almost nothing about networking. I've
>> > got
>> > two
>> > computers connected through a linksys wrt54g router. I've been trying
>> > to
>> > connect to a laptop running xp-pro (host) from a desktop running
>> > xp-home
>> > (client). Both have firewalls which are configured to allow whatever
>> > from
>> > each other. They share files and a printer and ping each other nicely.
>> > Here
>> > is the error message I get sometimes while trying to log in:
>> >
>> > "The client could not connect to the remote computer
>> > Remote connections might not be enabled or the computer might be too
>> > busy
>> > to
>> > accept new connections.
>> > It is also possible that network problems are preventing your
>> > connection.
>> > Please try connecting agian later. If the problem continues to occur,
>> > contact your administrator."
>> >
>> > Unfortunately I'm the administrator and I have no idea. I'm thinking
>> > its
>> > either the router config. or more likely the software policing firewall
>> > on
>> > the host (zonealarm). It still wont work with the fw disabled however.
>> > I
>> > actually got it load halfway one time before froze up and crashed.
>> >
>> > Can anyone give me any suggestions on how to get ths to work?
>>
>>
>>
August 30, 2005 1:44:02 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I don't have another client right now, maybe tomorrow I can try from school
but that will add more potential obstacles. My knowledge of networking has
quadrupled since my first post but that's still not saying much.

Should there be some service listening on port 3389?
Right now there isn't one on the host. Should I be concerned with port
forwarding even though both machines are behind a router?

(Ultra VCS works fine by the way)

"Sooner Al [MVP]" wrote:

> Do you have another client that you can try to connect from? I suppose its
> possible that Norton on your client is blocking the connection... I don't
> use Norton so I can say for sure...
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
>
> "CK" <CK@discussions.microsoft.com> wrote in message
> news:20D15F4E-273C-4F04-BFE2-51C356761D40@microsoft.com...
> > I've gone through the documentation on the link you provided and I think I
> > have the issue narrowed down to a couple of possible things. The host is
> > connected wirelessly using a broadcom 802.11g chip. The event viewer logs
> > on
> > the host under system show that the connection is dropped and restarted.
> > I've tried updating the driver using the one from windows update. Now the
> > client doesnt even get partially connected to the host. "The client could
> > not connect to the host..." Before, it would open up the RD window and
> > show
> > a black screen for a while then crash with a message that the connection
> > was
> > broken. There would also be an event logged under system that I mentioned
> > above. The zoneAlarm logs show that the connection was allowed between
> > the
> > two computers so i think the problem may be some other setting on the host
> > or
> > maybe the client. The client is running Norton Internet security fw that
> > should allow the connection.
> >
> > On the client computer I have some of the gui stuff from using the network
> > setup wizard such that when i use the browse option on the RD connect
> > dialogue It wont let me browse the networks because "there are not any
> > terminal servers on the network" I have terminal services started on the
> > host and of course the allow desktop connections check box is checked.
> >
> > What services need to be running in order to connect?
> > Is it possible to do this over wireless?
> >
> > "Sooner Al [MVP]" wrote:
> >
> >> See this page for troubleshooting help...
> >>
> >> http://theillustratednetwork.mvps.org/RemoteDesktop/Rem...
> >>
> >> Make sure your calling the correct private static LAN IP for the laptop.
> >>
> >> Its possible ZoneAlarm is causing the problem. If your using the free
> >> version I don't believe you can configure ZA for port forwarding. You
> >> can, I
> >> believe, configure ZA Pro for port forwarding...
> >>
> >> --
> >>
> >> Al Jarvi (MS-MVP Windows Networking)
> >>
> >> Please post *ALL* questions and replies to the news group for the mutual
> >> benefit of all of us...
> >> The MS-MVP Program - http://mvp.support.microsoft.com
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights...
> >>
> >>
> >> "CK" <CK@discussions.microsoft.com> wrote in message
> >> news:64DD3C39-36E7-473D-80E4-2C373F6B09C9@microsoft.com...
> >> > Let me start by saying i know almost nothing about networking. I've
> >> > got
> >> > two
> >> > computers connected through a linksys wrt54g router. I've been trying
> >> > to
> >> > connect to a laptop running xp-pro (host) from a desktop running
> >> > xp-home
> >> > (client). Both have firewalls which are configured to allow whatever
> >> > from
> >> > each other. They share files and a printer and ping each other nicely.
> >> > Here
> >> > is the error message I get sometimes while trying to log in:
> >> >
> >> > "The client could not connect to the remote computer
> >> > Remote connections might not be enabled or the computer might be too
> >> > busy
> >> > to
> >> > accept new connections.
> >> > It is also possible that network problems are preventing your
> >> > connection.
> >> > Please try connecting agian later. If the problem continues to occur,
> >> > contact your administrator."
> >> >
> >> > Unfortunately I'm the administrator and I have no idea. I'm thinking
> >> > its
> >> > either the router config. or more likely the software policing firewall
> >> > on
> >> > the host (zonealarm). It still wont work with the fw disabled however.
> >> > I
> >> > actually got it load halfway one time before froze up and crashed.
> >> >
> >> > Can anyone give me any suggestions on how to get ths to work?
> >>
> >>
> >>
>
>
>
Anonymous
August 30, 2005 8:47:55 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Absolutely...The host needs to be listening on TCP Port 3389. See the
"Troubleshooting" section of the page I pointed you to earlier. Make sure
Terminal Services status is "Started". If it is not start it. Configure it
for either "Manual" or "Automatic". You also may need to check the
dependencies tab by right-clicking on Terminal Services and selecting
"Properties"...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...


"CK" <CK@discussions.microsoft.com> wrote in message
news:F7F41C52-1B65-420F-9548-C8DF24A5CF2B@microsoft.com...
>I don't have another client right now, maybe tomorrow I can try from school
> but that will add more potential obstacles. My knowledge of networking
> has
> quadrupled since my first post but that's still not saying much.
>
> Should there be some service listening on port 3389?
> Right now there isn't one on the host. Should I be concerned with port
> forwarding even though both machines are behind a router?
>
> (Ultra VCS works fine by the way)
>
!