Remote Desktop Connection not Logging On

[Guest]

I have set up Remote Desktop Connection on my home computer and am able to
see it when I enter the IP address from the mstsc prompt, but when I enter in
the username and passwordit keeps telling me it cannot log me on that I need
to check the username and domain and ensure I am typing the password
correctly. I have done this like a thousand times and everytime I do I get
the same message, I know I am typing everything correctly so why wont it
connect me?

BTW I am running Media Edition V 2002 and am on a wireless network, not sure
if that has anything to do with it or not.

 

[Shenan Stanley]

I have set up Remote Desktop Connection on my home computer and am
able to see it when I enter the IP address from the mstsc prompt,
but when I enter in the username and passwordit keeps telling me it
cannot log me on that I need to check the username and domain and
ensure I am typing the password correctly. I have done this like a
thousand times and everytime I do I get the same message, I know I
am typing everything correctly so why wont it connect me?

BTW I am running Media Edition V 2002 and am on a wireless network,
not sure if that has anything to do with it or not.

- Administrative level user (or at least in the Remote Desktop users group)?
- What is your username? Does it contain spaces/special characters?
- Are you sure caps-lock/num-lock is not on? (Can be problematic with
laptops especially.)
- Have you tried another user?
- The password is something other than blank, right?

Create a whole new user with a decent password and make sure they are a
member of the "Remote Desktop" users group.
Try that user.

 

[Guest]

- Administrative level user (or at least in the Remote Desktop users
group)? Yes

- What is your username? Does it contain spaces/special characters? Username = Jason Meyer, and I am the computer administrator

- Are you sure caps-lock/num-lock is not on? (Can be problematic with
laptops especially.) Yes I am sure the caps lock is not on, I have tried it from both a laptop and desktop and am getting the same problem.

- Have you tried another user? No I have not this would defeat the purpose because all of my documents and what not that I need to be able to access are in my user profile and it would be too much of a hassel to have to create another user and then transfer everything.

- The password is something other than blank, right? Correct

Create a whole new user with a decent password and make sure they are a
member of the "Remote Desktop" users group. Try that user. I will try that for testing purposes, bit it will not solve my problem because again all that I need to access are under my user profile.

Something else interesting happened this morning, while I was testing this
all last night I was using two different computers in my house and while it
pulled the IP Address I got the cant log on message. When I got to work this
morning I decided to try it from my work computer and got a message that says
"the client could not connect to the remote computer. Remote connection
might be enabled or the computer might be too busy to accept new
connections... etc..."

I called home and ensured my computer was turned on and no one was using it.
Ironically enough I have also set this up in the other direction so that I
can log onto my work computer from home and have no problems, I just cant
seem to log on to my computer at home, from either my work computer or
another computer on my home network, it's very frustrating. If you would
like to contact me directly you can e-mail me at (e-mail address removed) or call me
at 702-275-9128.

Thanks for your help,
Jason

 

[Shenan Stanley]

I have set up Remote Desktop Connection on my home computer and am
able to see it when I enter the IP address from the mstsc prompt,
but when I enter in the username and passwordit keeps telling me it
cannot log me on that I need to check the username and domain and
ensure I am typing the password correctly. I have done this like a
thousand times and everytime I do I get the same message, I know I
am typing everything correctly so why wont it connect me?

BTW I am running Media Edition V 2002 and am on a wireless network,
not sure if that has anything to do with it or not.

We have to get this to work internally before we can work on it externally.
You actually created a new user and it still told you it could not log on as
that user. We have ruled out user profiles.
You do connect (get a request for username/password) when inside the same
network, so the remote desktop part is working - it is just not letting you
authenticate. That means your firewall settings are likely correct and
remote desktop *is* turned on.

- Your home machine's IP address - is it a private IP (usually 192.168.#.#)
or public?
- If "private" - what type of router are you using?
- You've said "it pulled the IP address" <- what does that mean? You are
actually using the name of the machine or searching? Or are you typing the
IP address in manually?

From outside your network (from work), the problem could be that you have
not configured your router to forward traffic to the proper internal
machines. Or it could even be as simple as you were using the internal IP
address - I do not know yet.

 

[Guest]

We have to get this to work internally before we can work on it externally.

You actually created a new user and it still told you it could not log on as
that user. We have ruled out user profiles.
You do connect (get a request for username/password) when inside the same
network, so the remote desktop part is working - it is just not letting you
authenticate. That means your firewall settings are likely correct and
remote desktop *is* turned on. Correct!!!

- Your home machine's IP address - is it a private IP (usually 192.168.#.#)
or public?

Not sure I know exactly what you are referring to, The IP I am using is the
one I got off the linksys screen when I log on. So for example, I pulled up
the Internet Explorer, typed in 192.168.1.1 and got my Linksys router
settings. I went to the status screen and got the IP address that it showed.
For work usiong the same process my Internet IP address is 24.234.###.###
(used the # as place holder for the real numbers I enter in), which is what
enter in as the computer name when I pull up the Remote Desktop Connection
screen, with my username and password, connects no problem. For my home it
is showing the Internet IP address as 68.108.##.##. So when I am trying to
connect remotely from work I am entering this as computer name with my log on
as the username and the correct password, and I am getting the message as I
described as before. I pinged the IP address from within the network and it
sent and received all packets no problem. When I ping the IP address from
work, all packets fail, not sure if that is useful or not. I also set up the
Gaming and Applications screen in linksys with the following settings in the
respective boxes: rem 80 3389 Both 192.168.1.101 enabled checked (101 being
the computer I am trying to access). I have not messed with any of the
security settings within the Linksys application.

- If "private" - what type of router are you using?

Linksys WT54G (I think) and I updated all the firmware too.

- You've said "it pulled the IP address" <- what does that mean? You are
actually using the name of the machine or searching? Or are you typing the
IP address in manually?

Typing in the IP address for the computer name.

From outside your network (from work), the problem could be that you have
not configured your router to forward traffic to the proper internal
machines. Or it could even be as simple as you were using the internal IP
address - I do not know yet.

I hope the information above was helpful, I think I did everything as the
directions told me to do and everything I did the same as when I set it up to
connect from home to work. I am thinking it is either something to do with
the security/firewall of the router, something to do with the Norton 2006, or
a glitch in the Media Edition of Windows XP. Either way if you can get me
around it and connected you will be my hero, I will be patient as I await
your response .

Jason

 

[Guest]

Jason, don't feel like the lone ranger. I have the same problem. However,
mine is a bit simpler since I don't have to deal outside my home network. I
have 2 notebooks and 1 desktop PC on my 3 unit network. I have one notebook
that no one can log into however, the problem notebook can login the the
desktop and the other notebook. So one unit is giving me the sh___s. I have
played around with changing password, setting up a new user for
troubleshooting etc. and pretty much did all the things that Shenan
prescribed to no avail. I have spent so much time on this it's ridiculous.
Think I'll resort to PCAnywhere Network connection option and abandon MS
Remote Desktop.

 

[Shenan Stanley]

Jason, don't feel like the lone ranger. I have the same problem.
However, mine is a bit simpler since I don't have to deal outside
my home network. I have 2 notebooks and 1 desktop PC on my 3 unit
network. I have one notebook that no one can log into however, the
problem notebook can login the the desktop and the other notebook.
So one unit is giving me the sh___s. I have played around with
changing password, setting up a new user for troubleshooting etc.
and pretty much did all the things that Shenan prescribed to no
avail. I have spent so much time on this it's ridiculous. Think
I'll resort to PCAnywhere Network connection option and abandon MS
Remote Desktop.

I'd suggest UltraVNC first - before PCAnywhere.

Worst case - you try it and don't like it, you are out time - since it is
free.
With PCAnywhere - you are out time and money right out the box. =)

 

[Guest]

I'd suggest UltraVNC first - before PCAnywhere.

Worst case - you try it and don't like it, you are out time - since it is
free.
With PCAnywhere - you are out time and money right out the box. =)

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way



thanks for the suggestion Shenan. I will try UtraVNC. I hope it runs better than RealVNC. That one was a bit sluggish oin XP machines when I used it about a year ago. Ron

 

[Guest]

Thank you both for the comments, I am not ready to throw in the towel yet and
am still hoping that Shenan can help me solve the mystery, but if not I will
try that other application you mentioned.

It's just so frustrating to not be able to get something to work that you
know should. Ron thatnks for the sympathy/empathy, it makes me feel better to
know I am not alone here

 

[Guest]

Jason, I'm the same as you. I know it works but why not in this instance.
Don't usually give up on issues like this but I've exhausted all my thoughts
and energy on this MS remote desktop application and no one seems to have a
clue as to why. I will install the UltraVNC freebie and give it a try. It's
cheap and if it does the job I will be more than happy to make a donation to
the developers fund. Ron

 

[Jay Dawg]

So Shenan have you given up on us?

Jason, I'm the same as you. I know it works but why not in this instance.
Don't usually give up on issues like this but I've exhausted all my thoughts
and energy on this MS remote desktop application and no one seems to have a
clue as to why. I will install the UltraVNC freebie and give it a try. It's
cheap and if it does the job I will be more than happy to make a donation to
the developers fund. Ron

 

[Guest]

Ok, I've struggled with Remote Desktop enough to feel your pain, however
getting it correctly working is much better than using PcAnywhere etc. I
have a 3 workstation peer to peer network and I can access all 3 systems,
from just about ANY computer running Windows XP because Remote Desktop is
installed by default on the vast majority of systems. This has saved my
behind a number of times when I need to access my files and forgot to bring
my laptop. (I just borrow anybody's computer that has a network connection,
and most of them time I can connect right in.) Plus it is free, (not
counting the cost of Win XP of course).

I would be willing to bet that your problem is either in your router
configuration or in Windows firewall. I have my router configured to open
the appropriate port "3389" for the default Remote desktop configuration.
You also need to check the DHCP table to make sure it is being opened for the
proper "local" address. Since your router acts as a DHCP server, it is
possible that your local ip addressis changing when your reboot or lose
power. Linksys has a static DHCP setting as I recall, where you can specify
that each of your private addresses remains the same from bootup to bootup,
this is how I have my system set up. Also, as a test, disable your firewall
and check for connectivity. If still no go, then disable Norton Internet
Security (I hate Norton these days and no longer use any Symantec Products).
If disabling NIS causes it to work, I believe the "worm protection" or
whatever they call it, basically it is a firewall like setting, needs to be
setup to exclude port 3389. Hope this helps. Don't give up, the results are
definitely worth it.

 

[Shenan Stanley]

We have to get this to work internally before we can work on it
externally. You actually created a new user and it still told you
it could not log on as that user. We have ruled out user profiles.
You do connect (get a request for username/password) when inside
the same network, so the remote desktop part is working - it is
just not letting you authenticate. That means your firewall
settings are likely correct and remote desktop *is* turned on.

- Your home machine's IP address - is it a private IP (usually
192.168.#.#) or public?

- If "private" - what type of router are you using?

- You've said "it pulled the IP address" <- what does that mean?
You are actually using the name of the machine or searching? Or
are you typing the IP address in manually?

From outside your network (from work), the problem could be that
you have not configured your router to forward traffic to the
proper internal machines. Or it could even be as simple as you
were using the internal IP address - I do not know yet.

Not sure I know exactly what you are referring to, The IP I am
using is the one I got off the linksys screen when I log on. So
for example, I pulled up the Internet Explorer, typed in
192.168.1.1 and got my Linksys router settings. I went to the
status screen and got the IP address that it showed. For work
usiong the same process my Internet IP address is 24.234.###.###
(used the # as place holder for the real numbers I enter in), which
is what enter in as the computer name when I pull up the Remote
Desktop Connection screen, with my username and password, connects
no problem. For my home it is showing the Internet IP address as
68.108.##.##. So when I am trying to connect remotely from work I
am entering this as computer name with my log on as the username
and the correct password, and I am getting the message as I
described as before. I pinged the IP address from within the
network and it sent and received all packets no problem. When I
ping the IP address from work, all packets fail, not sure if that
is useful or not. I also set up the Gaming and Applications screen
in linksys with the following settings in the respective boxes: rem
80 3389 Both 192.168.1.101 enabled checked (101 being the computer
I am trying to access). I have not messed with any of the security
settings within the Linksys application.

Linksys WT54G (I think) and I updated all the firmware too.

Typing in the IP address for the computer name.

I hope the information above was helpful, I think I did everything
as the directions told me to do and everything I did the same as
when I set it up to connect from home to work. I am thinking it is
either something to do with the security/firewall of the router,
something to do with the Norton 2006, or a glitch in the Media
Edition of Windows XP. Either way if you can get me around it and
connected you will be my hero, I will be patient as I await your
response .

Okay.

1) Sitting at the computer you will be remoting into... do the following:
- Windows-Key+R
- type in:
cmd /k ipconfig
- click OK
- your internal IP is listed there.
2) Close the command prompt window.
3) From another computer on the same network, try to remote desktop into
the first computer (by the IP Address you got above.)
4) Post the results here (your IP address (if it is 192.168.xxx.xxx <- in
other words, a private IP) and any messages you get from the remote
attempt.)
5) Note the exact time on the remote system when you try to remote to it...
(Assuming the IP is statically set at 1.101?)

Next...

1) Sitting at the computer you tried to remote into... do the following:
- Windows-Key+R
- type in:
control userpasswords2
- click OK
2) In the "User Accounts" window, make sure you are looking under the
"Advanced" tab.
3) Click on the "Advanced" button to open the Local Users and Groups window.
4) Select the "Users" folder on the left to bring up more information on the
right.
5) Take special notice of your "name" and if it actually has a space or any
special characters.
6) Double-click on your username on the right side.
7) Select the "Member Of" tab and list the groups here:
8) OK and close your way out of all those windows.

Next...

1) Sitting at the computer you tried to remote into... do the following:
- Windows-Key+R
- type in:
eventvwr
- click OK
2) In event viewer, look under "Security" for the exact time you tried and
see if there are any messages concerning success or failure for a logon.
Try under system and application as well.

Somewhere you mentioned "Norton" --> knowing that this resource hog has
caused other people trouble with many settings - how willing would you be to
uninstall Norton 100% and configure just the Windows firewall? Just
disabling the Norton Internet Firewall component may not be enough. If you
don't want to do that - you obviously have more than one system - do both
have Norton Internet Security? If not - can you setup the other system to
allow remote desktop?