Cannot Connect To File System. Service Not Started

  • Thread starter Thread starter Ifeanyi O. Asonye
  • Start date Start date
I

Ifeanyi O. Asonye

ERROR:"cannot connect to file system. service not started"

This pop up on the screen when I connect using the RDP
Client on Windows 2000 Client Terminal to the Terminal
Server over the Internet. Then I will receive error
opening a particular file program.

I also connect successfully using a Windows 98 RDP Client
and both win2k Clients all may get this error and with all
user accounts. Is it possible the Windows 98 will have
anything to do with this problem ?



Please feel free to email suggestions for the fix to
(e-mail address removed)
 
From those Windows 2000 clients, can either of them ping
the terminal server or telnet to port 3389 of the terminal
server?

-M
 
Yes. The port forwarding is setup on the router to forward
3389 connections to the internal and external IP Addresses
of the Terminal Server.

Basically, the router is configured to discard ping
commands. Each and every client can make a successful
connection to the server and log on using Terminal
Services RDP. The error still pops up on the
screen. "cannot connect to file systems, service not
running" There is still some problem opening certain files
on the server.
 
When exactly does this error popup? Does it always
popup? Are there any eventlog entries that accompany this
problem?

-M
 
Back
Top