Remote Desktop asks for Terminal Server to validate user/password

  • Thread starter Thread starter t.jacobs
  • Start date Start date
T

t.jacobs

My situation is similar.
My desktop is running WinXPPro and is member of my TomNet workgroup.
My laptop is running WinXPPro and is member of the same TomNet
workgroup.
Both machines are connected wirelessly to a router.
Both machines are configured to operate without a password.
I too would like to me able to operate the desktop (which is in the
attic) from the laptop (on the kitchen table).
I have enable both machines to allow Remote Desktop connections.
When I create an RD connection, in the Computer field I click Browse to
locate the desktop.
The name of my workgroup is shown, but when I click the + to expand it
into all (rather: both) ps's connected, I get the reply:
The TOMNET domain/workgroup does not contain any Terminal servers.

Furthermore: when I try and connect to the desktop using its ip
address, I get a warning that the system might be too busy to accept
new connections. The only thing it's doing is waiting for me to
connect. The message also suggests that there may be network problems,
but when using Explorer I can easily browse the contents of the drives
I have shared.

Any suggestions what I might do to improve on this situation?

Thx
 
t.jacobswrote:
My situation is similar.
Click to expand...

Similar to what? You did not replyt to anything...
My desktop is running WinXPPro and is member of my TomNet workgroup.
My laptop is running WinXPPro and is member of the same TomNet
workgroup.
Click to expand...

Well - being a member of the same workgroup does not mean much at all...
But okay.
Both machines are connected wirelessly to a router.
Both machines are configured to operate without a password.
Click to expand...

In a remote desktop newsgroup - this is starting out badly. "... without a
password ..."
I too would like to me able to operate the desktop (which is in the
attic) from the laptop (on the kitchen table).
Click to expand...

"... too ..."???!!
Agaion - you replied to nothing. You created a new post - your own thread.
What is this "too"?
I have enable both machines to allow Remote Desktop connections.
Click to expand...

That's part of it... sure.
You also need to configure your firewall and give the user you will be
connecting with a password. No password generally means no remote desktop.
(In reference to Microsoft RDC.)
When I create an RD connection, in the Computer field I click
Browse to locate the desktop.
The name of my workgroup is shown, but when I click the + to expand
it into all (rather: both) ps's connected, I get the reply:
The TOMNET domain/workgroup does not contain any Terminal servers.
Click to expand...

So - don't do that. I hate network browsing. It's network intensive,
worthless traffic. Put the IP address of the machine into the Remote
Desktop Client and connect.
Furthermore: when I try and connect to the desktop using its ip
address, I get a warning that the system might be too busy to accept
new connections. The only thing it's doing is waiting for me to
connect.
Click to expand...

Do you have any accounts with passwords?
Have you configured the firewall to allow remote desktop connections?
The message also suggests that there may be network
problems, but when using Explorer I can easily browse the contents
of the drives I have shared.
Click to expand...

Well - you have your firewall configured to allow File and Print sharing
(hoppefully only within your private network?)
Any suggestions what I might do to improve on this situation?
Click to expand...

Check your firewall settings, set a password for the users (if you need it
to boot right into Windows - use TweakUI to make it automatically log the
user in at startup..)
 
Shenan said:
t.jacobswrote:

Similar to what? You did not replyt to anything...
Click to expand...

I intended to reply to a similar thread. Which obviously failed.
Well - being a member of the same workgroup does not mean much at all...
But okay.


In a remote desktop newsgroup - this is starting out badly. "... without a
password ..."
Click to expand...

My home network is not accessible for the Big Bad World. My router
keeps the gate closed.
"... too ..."???!!
Agaion - you replied to nothing. You created a new post - your own thread.
What is this "too"?
Click to expand...
Again: you already remarked that I didn't succeed in replying to a
previous thread. No need to make your point any stiffer than you
already did.
That's part of it... sure.
You also need to configure your firewall and give the user you will be
connecting with a password. No password generally means no remote desktop.
(In reference to Microsoft RDC.)


So - don't do that. I hate network browsing. It's network intensive,
worthless traffic. Put the IP address of the machine into the Remote
Desktop Client and connect.
Click to expand...
Microsoft stuff doesn't always turn out as user friendly as intended.
Why wouldn't I browse if I am invited to do so?
Do you have any accounts with passwords?
Click to expand...
No - until now there has never been any need. This is my home network,
isn't it?
Have you configured the firewall to allow remote desktop connections? Yes, I have.


Well - you have your firewall configured to allow File and Print sharing
(hoppefully only within your private network?) Of course.


Check your firewall settings, set a password for the users (if you need it
to boot right into Windows - use TweakUI to make it automatically log the
user in at startup..)
Click to expand...

Would it be useful to create a "Remote User" with a password, so I can
connect remotely as him, and allowing me to use the system "normally"
without having to go through the process of supplying a password each
time I log in?

-t-
 
Normally you can not browse for other PCs in a work group using the Remote
Desktop connectoid browse function. You can apply a registry hack to get
around that issue though...

READ THESE TWO KB ARTICLE FIRST!!!!!!

http://support.microsoft.com/default.aspx?scid=kb;EN-US;256986
http://support.microsoft.com/default.aspx?scid=kb;EN-US;322756

The hack...

http://support.microsoft.com/default.aspx?scid=kb;en-us;281307

By design you need a user ID that is an administrator or be a member of the
Remote Desktop users group *AND* have a password...

--

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...

My situation is similar.
My desktop is running WinXPPro and is member of my TomNet workgroup.
My laptop is running WinXPPro and is member of the same TomNet
workgroup.
Both machines are connected wirelessly to a router.
Both machines are configured to operate without a password.
I too would like to me able to operate the desktop (which is in the
attic) from the laptop (on the kitchen table).
I have enable both machines to allow Remote Desktop connections.
When I create an RD connection, in the Computer field I click Browse to
locate the desktop.
The name of my workgroup is shown, but when I click the + to expand it
into all (rather: both) ps's connected, I get the reply:
The TOMNET domain/workgroup does not contain any Terminal servers.

Furthermore: when I try and connect to the desktop using its ip
address, I get a warning that the system might be too busy to accept
new connections. The only thing it's doing is waiting for me to
connect. The message also suggests that there may be network problems,
but when using Explorer I can easily browse the contents of the drives
I have shared.

Any suggestions what I might do to improve on this situation?

Thx
 
TomJ said:
Would it be useful to create a "Remote User" with a password, so I
can connect remotely as him, and allowing me to use the system
"normally" without having to go through the process of supplying a
password each time I log in?
Click to expand...

.... Only if you don't care about having the same look/feel/setup as the user
who you normally log into the machine while sitting in front of it OR you
have hacked the registry so they share the same profile. Otherwise it is
just as easy to setup an auologon.

Also - the "router" is not 100% foolproof - not even close actually. It is
still a good idea to have passwords set on your machine even if you are the
only one who lives in your safe-house. Sooner or later you are likely to
have visitors - whether they are in person or virtual. =)
 
Back
Top