RE: Terminal Services crash? or something else?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Glad you solved your problem!

In case that you still worry about the greyed out options on the TS
service: this is by design. Documented here:

278657 - Terminal Services Cannot Be Manipulated
http://support.microsoft.com/?kbid=278657

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?UHVk?= <Pud@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 07 apr
2006 in microsoft.public.win2000.termserv.clients:

Resolved! It wasn't Terminal Services which was the problem.
The Web Server service had stopped for some reason. Restarting
the Web Server service gave users access again.




"Pud" wrote:

Something I forgot to mention .... the reason I
uninstalled/reinstalled TS on Tuesday was because I could not
'Start/Stop/Restart' as all options were greyed out. I did try
setting the startup to manual but as soon as I started teh
service after rebooting the options were greyed out and users
still had no access.

After reinstalling the options were still greyed out.

Any help appreciated.


"Pud" wrote:

A company I support (5 hrs a week) have a 2000 Domain with
about a dozen local users, 6 users in a remote office and 4
remote home users. The remote office uses their own 2000
server in a different domain and they pick up their mail via
Exchange on both servers - the main server collects SMTP via
ISP. Remote (non-office) collect their mail via Outlook Web
Access (via Terminal Services). All remote users use
Navision via TS. Access for all remote users is via browser
(http:// ip address / terminals).

Late last week all remote users lost access to Terminal
Services. The browser returned: 'The page cannot be
displayed' (IE) or 'Error: Host Not Accessible' (Firefox).
On Tuesday I uninstalled/reinstalled Terminal Services and
the problem was resolved. Today (Thursday) the problem has
returned - all remote users are unable to login via Terminal
Services.

SMTP email is still going to the remote office, and FTP
access is still available so we know the router/firewall are
ok. No changes have been made to Firewall config.

Where/how can I identify where the problem is? How can I
resolve it permanently without having to re-install TS on a
regular basis/
.



Relevant Pages

  • Re: Connecting a remote workstation to a domain
    ... Terminal Server to go with the SBS server. ... I can remotely join XP Pro computers at the remote ... either way it loads her cached roaming profile ... I need the local printers at the remote office to be set up ...
    (microsoft.public.windows.server.sbs)
  • Re: ip addresses for wireless connection
    ... How much do you trust the security of this wireless link? ... what you say and install a DMZ with the remote workstations on it, ... > the existing SBS2K server that I support. ... > another hub/switch at the new remote office. ...
    (microsoft.public.windows.server.sbs)
  • Re: The Desktop Strikes Back [was Re: Newbie FAQ #2: Wheres the GUI?]
    ... while programs executed on a remote server. ... save X terminals. ... while SunRays fix the session state ...
    (comp.lang.lisp)
  • Re: Connecting a remote workstation to a domain
    ... to the remote office but the remote office computers were already in ... profile pre-configured on the server LAN then copied to the Default User ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN - Network Novice Questions
    ... Terminal Server - I know not recommended but we have to cut corners on ... company is installing a VoIP system at the remote office and will also ... will supply the router at the remote location. ...
    (microsoft.public.windows.terminal_services)