Remote Desktop Connection Not Working - PLEASE HELP (I'M Begging)!!!

  • Thread starter Thread starter Avi Gallant
  • Start date Start date
A

Avi Gallant

Hello everybody,

I have been working for three days at this point to get remote desktop
connection to work. After spending 4 hours, just trying to upgrade
from XP Home to XP PRO, I finally got passed that step. Than I spent
another day trying to find the little checkbox under the network
connections that would disable the XP firewall. Here is where I am at
now:

Home Computer running XP PRO. Have gone into control panel > system >
remote > and checked box to allow users to connect remotely.

Away computer running Windows 98 with Remote desktop connection
software installed.

Both computers are running SBC DSL service and neither have a router.
I NOW can tracert and ping the home computer. I enter in the ip
address and it appears to be connecting. I than enter in my user name
and password. It says now loading personal settings and than I get
this error:
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 again. If problem continues to
occur, contact your administrator?
Click to expand...

The first time this whole sequence occured, a small picture appeared
in the upper right hand corner. It appeared to be a monitor with a
line running to something that looked like a pipe or netwrok sign.
There was an X running through this line connecting the monitor and
"pipe".

I have read several posts about "opening" up a port but I have no idea
how to do this or why I would need to do this since I am not using ANY
router.

I ask for anybody's help who has experienced similiar problems. I am
very frusturated at this point of why something that should take 10
minutes has taken three days.

Avi
 
The small picture is the icon for autoreconnecting. You seem to have some
problem with your network connection. What autoreconnection does it when the
network connection is dropped due to some reason, it tries to reconnect to
the session without the user having to enter the credentials again.

Try this. Open CMD.exe and run the command "ping -t <IPaddress of your home
WinXP machine>". Now start remote desktop session and see if there any drops
in the network connection in the command prompt.
 
Mahadev,

I ran the test you told me to do (ping -t) During the test, when I
tried to connect using remote desktop, the connection that was
previously sending and receiving packets went to "request timed out".
(in the command window) The remote desktop once again came up with
the blinking red box in the upper right corner and I got a message as
well on this screen that the request had timed out.

NOW what????

Avi




Mahadev Alladi said:
The small picture is the icon for autoreconnecting. You seem to have some
problem with your network connection. What autoreconnection does it when the
network connection is dropped due to some reason, it tries to reconnect to
the session without the user having to enter the credentials again.

Try this. Open CMD.exe and run the command "ping -t <IPaddress of your home
WinXP machine>". Now start remote desktop session and see if there any drops
in the network connection in the command prompt.


--
Mahadev Alladi [MS]
---
This posting is provided "AS IS" with no warranties, and confers no rights.
---

Avi Gallant said:
Hello everybody,

I have been working for three days at this point to get remote desktop
connection to work. After spending 4 hours, just trying to upgrade
from XP Home to XP PRO, I finally got passed that step. Than I spent
another day trying to find the little checkbox under the network
connections that would disable the XP firewall. Here is where I am at
now:

Home Computer running XP PRO. Have gone into control panel > system >
remote > and checked box to allow users to connect remotely.

Away computer running Windows 98 with Remote desktop connection
software installed.

Both computers are running SBC DSL service and neither have a router.
I NOW can tracert and ping the home computer. I enter in the ip
address and it appears to be connecting. I than enter in my user name
and password. It says now loading personal settings and than I get
this error:
The client could not connect to the remote computer.

The first time this whole sequence occured, a small picture appeared
in the upper right hand corner. It appeared to be a monitor with a
line running to something that looked like a pipe or netwrok sign.
There was an X running through this line connecting the monitor and
"pipe".

I have read several posts about "opening" up a port but I have no idea
how to do this or why I would need to do this since I am not using ANY
router.

I ask for anybody's help who has experienced similiar problems. I am
very frusturated at this point of why something that should take 10
minutes has taken three days.

Avi
Click to expand...
Click to expand...
 
Mahadev,

I ran the test you told me to do (ping -t) During the test, when I
tried to connect using remote desktop, the connection that was
previously sending and receiving packets went to "request timed out".
(in the command window) The remote desktop once again came up with
the blinking red box in the upper right corner and I got a message as
well on this screen that the request had timed out.

NOW what????

Avi




Mahadev Alladi said:
The small picture is the icon for autoreconnecting. You seem to have some
problem with your network connection. What autoreconnection does it when the
network connection is dropped due to some reason, it tries to reconnect to
the session without the user having to enter the credentials again.

Try this. Open CMD.exe and run the command "ping -t <IPaddress of your home
WinXP machine>". Now start remote desktop session and see if there any drops
in the network connection in the command prompt.


--
Mahadev Alladi [MS]
---
This posting is provided "AS IS" with no warranties, and confers no rights.
---

Avi Gallant said:
Hello everybody,

I have been working for three days at this point to get remote desktop
connection to work. After spending 4 hours, just trying to upgrade
from XP Home to XP PRO, I finally got passed that step. Than I spent
another day trying to find the little checkbox under the network
connections that would disable the XP firewall. Here is where I am at
now:

Home Computer running XP PRO. Have gone into control panel > system >
remote > and checked box to allow users to connect remotely.

Away computer running Windows 98 with Remote desktop connection
software installed.

Both computers are running SBC DSL service and neither have a router.
I NOW can tracert and ping the home computer. I enter in the ip
address and it appears to be connecting. I than enter in my user name
and password. It says now loading personal settings and than I get
this error:
The client could not connect to the remote computer.

The first time this whole sequence occured, a small picture appeared
in the upper right hand corner. It appeared to be a monitor with a
line running to something that looked like a pipe or netwrok sign.
There was an X running through this line connecting the monitor and
"pipe".

I have read several posts about "opening" up a port but I have no idea
how to do this or why I would need to do this since I am not using ANY
router.

I ask for anybody's help who has experienced similiar problems. I am
very frusturated at this point of why something that should take 10
minutes has taken three days.

Avi
Click to expand...
Click to expand...
 
Still have not come up with any answers. Just trying to keep the
thread alive so I didn't waste $200 on getting Windows XP PRO for
nothing. Thanks.

Avi


Mahadev,

I ran the test you told me to do (ping -t) During the test, when I
tried to connect using remote desktop, the connection that was
previously sending and receiving packets went to "request timed out".
(in the command window) The remote desktop once again came up with
the blinking red box in the upper right corner and I got a message as
well on this screen that the request had timed out.

NOW what????

Avi




Mahadev Alladi said:
The small picture is the icon for autoreconnecting. You seem to have some
problem with your network connection. What autoreconnection does it when the
network connection is dropped due to some reason, it tries to reconnect to
the session without the user having to enter the credentials again.

Try this. Open CMD.exe and run the command "ping -t <IPaddress of your home
WinXP machine>". Now start remote desktop session and see if there any drops
in the network connection in the command prompt.


--
Mahadev Alladi [MS]
---
This posting is provided "AS IS" with no warranties, and confers no rights.
---

Avi Gallant said:
Hello everybody,

I have been working for three days at this point to get remote desktop
connection to work. After spending 4 hours, just trying to upgrade
from XP Home to XP PRO, I finally got passed that step. Than I spent
another day trying to find the little checkbox under the network
connections that would disable the XP firewall. Here is where I am at
now:

Home Computer running XP PRO. Have gone into control panel > system >
remote > and checked box to allow users to connect remotely.

Away computer running Windows 98 with Remote desktop connection
software installed.

Both computers are running SBC DSL service and neither have a router.
I NOW can tracert and ping the home computer. I enter in the ip
address and it appears to be connecting. I than enter in my user name
and password. It says now loading personal settings and than I get
this error:
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 again. If problem continues to
occur, contact your administrator?

The first time this whole sequence occured, a small picture appeared
in the upper right hand corner. It appeared to be a monitor with a
line running to something that looked like a pipe or netwrok sign.
There was an X running through this line connecting the monitor and
"pipe".

I have read several posts about "opening" up a port but I have no idea
how to do this or why I would need to do this since I am not using ANY
router.

I ask for anybody's help who has experienced similiar problems. I am
very frusturated at this point of why something that should take 10
minutes has taken three days.

Avi
Click to expand...
Click to expand...
Click to expand...
 
I've not heard of this problem before. Meanwhile, can you check the eventlog
of the server (your home machine) and see if you can find any relevent info
that can help us here.

--
Mahadev Alladi [MS]
---
This posting is provided "AS IS" with no warranties, and confers no rights.
---

Avi Gallant said:
Still have not come up with any answers. Just trying to keep the
thread alive so I didn't waste $200 on getting Windows XP PRO for
nothing. Thanks.

Avi


(e-mail address removed) (Avi Gallant) wrote in message
Mahadev,

I ran the test you told me to do (ping -t) During the test, when I
tried to connect using remote desktop, the connection that was
previously sending and receiving packets went to "request timed out".
(in the command window) The remote desktop once again came up with
the blinking red box in the upper right corner and I got a message as
well on this screen that the request had timed out.

NOW what????

Avi




"Mahadev Alladi[MS]" <[email protected]> wrote in message
The small picture is the icon for autoreconnecting. You seem to have some
problem with your network connection. What autoreconnection does it when the
network connection is dropped due to some reason, it tries to reconnect to
the session without the user having to enter the credentials again.

Try this. Open CMD.exe and run the command "ping -t <IPaddress of your home
WinXP machine>". Now start remote desktop session and see if there any drops
in the network connection in the command prompt.


--
Mahadev Alladi [MS]
---
This posting is provided "AS IS" with no warranties, and confers no rights.
---

Hello everybody,

I have been working for three days at this point to get remote desktop
connection to work. After spending 4 hours, just trying to upgrade
from XP Home to XP PRO, I finally got passed that step. Than I spent
another day trying to find the little checkbox under the network
connections that would disable the XP firewall. Here is where I am at
now:

Home Computer running XP PRO. Have gone into control panel > system
remote > and checked box to allow users to connect remotely.

Away computer running Windows 98 with Remote desktop connection
software installed.

Both computers are running SBC DSL service and neither have a router.
I NOW can tracert and ping the home computer. I enter in the ip
address and it appears to be connecting. I than enter in my user name
and password. It says now loading personal settings and than I get
this error:
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 again. If problem continues to
occur, contact your administrator?

The first time this whole sequence occured, a small picture appeared
in the upper right hand corner. It appeared to be a monitor with a
line running to something that looked like a pipe or netwrok sign.
There was an X running through this line connecting the monitor and
"pipe".

I have read several posts about "opening" up a port but I have no idea
how to do this or why I would need to do this since I am not using ANY
router.

I ask for anybody's help who has experienced similiar problems. I am
very frusturated at this point of why something that should take 10
minutes has taken three days.

Avi
Click to expand...
Click to expand...
Click to expand...
 
Back
Top