Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Remote Desktop to a Windows 2000 Server machine.

Remote Desktop to a Windows 2000 Server machine.

Forum Windows 2000/NT : Windows 2000/NT General Discussion - Remote Desktop to a Windows 2000 Server machine.

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

Archived from groups: microsoft.public.win2000.general (More info?)

 

Up till yesterday, I was able to remote desktop our Windows 2000 Server.
This is no longer the case. I can still get to the shared directorys so I
know its connected to our network correctly but it still gives me the "Could
be busy or not there" message.

Is there a service or something I need to do to the machine to have it take
remote connects again?

Sponsored Links
Register or log in to remove.

Archived from groups: microsoft.public.win2000.general (More info?)

 

"Shawn Donovan" <ShawnDonovan@discussions.microsoft.com> wrote in message
news:FC08F01D-9398-493B-8209-C63A829D9460@microsoft.com...
> Up till yesterday, I was able to remote desktop our Windows 2000 Server.
> This is no longer the case. I can still get to the shared directorys so I
> know its connected to our network correctly but it still gives me the
"Could
> be busy or not there" message.
>
> Is there a service or something I need to do to the machine to have it
take
> remote connects again?

- Check your firewalls
- Make sure that the Terminal Server service is running on the host

Reply to Anonymous

Archived from groups: microsoft.public.win2000.general (More info?)

 

Thats the thing, there is no firewall in between and it has worked up till a
few days ago. Perhaps reinstall the Terminal Services?

"Pegasus (MVP)" wrote:

>
> "Shawn Donovan" <ShawnDonovan@discussions.microsoft.com> wrote in message
> news:FC08F01D-9398-493B-8209-C63A829D9460@microsoft.com...
> > Up till yesterday, I was able to remote desktop our Windows 2000 Server.
> > This is no longer the case. I can still get to the shared directorys so I
> > know its connected to our network correctly but it still gives me the
> "Could
> > be busy or not there" message.
> >
> > Is there a service or something I need to do to the machine to have it
> take
> > remote connects again?
>
> - Check your firewalls
> - Make sure that the Terminal Server service is running on the host
>
>
>

Reply to Anonymous
Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Remote Desktop to a Windows 2000 Server machine.
Go to:

There are 424 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them
  • 01:00 meywd won the Freshman badge
  • 01:00 nayega won the Freshman badge
  • 01:00 gpfear won the Freshman badge
  • 01:00 Conrad925 won the Freshman badge
  • 01:00 skythra won the Freshman badge
  • 01:00 Ckaz won the Freshman badge
  • 01:00 james59 won the Uniformed badge
  • 01:00 snarl won the Uniformed badge
  • 01:00 patlabor44 won the Uniformed badge
  • 01:00 Kiren won the Uniformed badge