L
Lee Smith
I have been using remote access for several months now and love it. However
in the last few weeks I have ran into a bit of a snag and I am unable to
figure out what has caused it and was hopping perhaps some on has seen this
and knows how to resolve it.
I just built a new system and installed remote access on it and the moved
the old system off to the side. At first I thought it may be the new system
but after some testing I found I am having the same problem on both systems
now.
The one thing I changed in the old system is the video card. I did see the
post about NVIDIA and I looked for that. On the new system it was running
but not on the old one. So I do not think that is the cause of my problem
First let me say both computers have 2 users. One is a local user (no
password) and the second user is one setup for remote access with a
password. The machines are called GAME and GAME1. The problem I am seeing
when I try to connect to GAME or GAME1 from any remote XP system is I get
the logon screen. I type in the username/password and hit connect. I see
something flash up and go away so fast I am unable to read it. Then the
screen sits on a blue screen like it normally does wile waiting to sign in.
This last for about 30 seconds then instead of logging in I just get dumped
back to the desktop. There is no error or any sort of info given to explain
why I did not connect.
After realizing I had a problem from the outside world I tried just logging
on to GAME from GAME1 and I also tried logging onto GAME1 from GAME. In
both cases the same problem happens, screen sits there like it is logging on
for about 30 seconds then it just goes back to the desktop. This tells me
it is not a router/IP problem.
I have found if I try to log on while the non remote user is logged on it
pops up the do you want to allow screen and if I don't respond after so long
the screen goes to the XP logon screen but I do not get logged on. I know
for a fact I used to just hit yes (don't know what was happening on screen
because was remote) but after so long I would get logged in. While testing
at home I have also noticed if I am sitting on the XP login screen with no
one logged on and try to connect with the other system it shows that the
REMOTE user is logged on for those 30 seconds while I wait for it to try to
connect. When I go back to my desktop and not connect the XP logon screen
on other computer goes back to no user logged on. Also while on the systems
at home during the 30 seconds while I am waiting for the logon to work I
hear the sounds as if I just logged on my speakers.
Now here is the icing on the cake. If I log on to XP as the REMOTE USER
then try to connect from the other machine I get in every time. This is the
same on both systems.
So I know remote connection is working but the only way I can log in now
remotely is to make sure I leave the machine logged on as the REMOTE USER.
I know for a fact this is new and I didn't used to have to do that. I can
do this but it is a pain.
I hope some one has a clue what this may be or even better how to fix!
I'll be watching posts or feel free to email me direct at
(e-mail address removed)
Lee
in the last few weeks I have ran into a bit of a snag and I am unable to
figure out what has caused it and was hopping perhaps some on has seen this
and knows how to resolve it.
I just built a new system and installed remote access on it and the moved
the old system off to the side. At first I thought it may be the new system
but after some testing I found I am having the same problem on both systems
now.
The one thing I changed in the old system is the video card. I did see the
post about NVIDIA and I looked for that. On the new system it was running
but not on the old one. So I do not think that is the cause of my problem
First let me say both computers have 2 users. One is a local user (no
password) and the second user is one setup for remote access with a
password. The machines are called GAME and GAME1. The problem I am seeing
when I try to connect to GAME or GAME1 from any remote XP system is I get
the logon screen. I type in the username/password and hit connect. I see
something flash up and go away so fast I am unable to read it. Then the
screen sits on a blue screen like it normally does wile waiting to sign in.
This last for about 30 seconds then instead of logging in I just get dumped
back to the desktop. There is no error or any sort of info given to explain
why I did not connect.
After realizing I had a problem from the outside world I tried just logging
on to GAME from GAME1 and I also tried logging onto GAME1 from GAME. In
both cases the same problem happens, screen sits there like it is logging on
for about 30 seconds then it just goes back to the desktop. This tells me
it is not a router/IP problem.
I have found if I try to log on while the non remote user is logged on it
pops up the do you want to allow screen and if I don't respond after so long
the screen goes to the XP logon screen but I do not get logged on. I know
for a fact I used to just hit yes (don't know what was happening on screen
because was remote) but after so long I would get logged in. While testing
at home I have also noticed if I am sitting on the XP login screen with no
one logged on and try to connect with the other system it shows that the
REMOTE user is logged on for those 30 seconds while I wait for it to try to
connect. When I go back to my desktop and not connect the XP logon screen
on other computer goes back to no user logged on. Also while on the systems
at home during the 30 seconds while I am waiting for the logon to work I
hear the sounds as if I just logged on my speakers.
Now here is the icing on the cake. If I log on to XP as the REMOTE USER
then try to connect from the other machine I get in every time. This is the
same on both systems.
So I know remote connection is working but the only way I can log in now
remotely is to make sure I leave the machine logged on as the REMOTE USER.
I know for a fact this is new and I didn't used to have to do that. I can
do this but it is a pain.
I hope some one has a clue what this may be or even better how to fix!
I'll be watching posts or feel free to email me direct at
(e-mail address removed)
Lee