A
AndrewKim
I am trying to share a Terminal Services client creator folder on my
Terminal server so that other computers can launch setup file and install
the client from their computers.
The setup file is located in a computer named megadeus-dc (and yes, this is
my DC also), and the path goes like this:
c:\WINNT\system32\clients\tsclient\win32\disks\disk1\setup.exe
And I believe this is the default folder assigned to the client creator when
you install Terminal Services on Win2k server.
Now I have made c:\WINNT\system32\clients\tsclient\win32 folder a shared
folder named 'Terminal Client', and permission is give to 'everyone' group.
Problem is, when I try launching setup.exe from a client machine, the
following error message pops up.
'Cannot find file \\megadeus-dc\Terminal Client\disks\disk1\setup.exe (or
one of its components). Check to ensure the path and filename are correct
and that all required libraries are available.', where 'megadeus-dc' is my
terminal server / DC.
And on the blue title bar it says 'can't run 16-bit windows program'.
Now this could be very misleading, but I am launching the Terminal Services
client for 32-bit as you can see from the path, and from a win2k prof.
client machine.
And what really throws me off is that when I change the share name to that
of the actual folder name, which is 'win32' in this case, the problem
suddenly disappears altogether. But when I use any other share name than
the actual folder name the error message shows up.
It is only setup.exe and acmsetup.exe that doesn't work - all other files in
the same folder can be read and accessed from any client machine, which
gives me an impression that this is not the network path problem, but rather
a default path problem, if there is one, within setup.exe.
You can, of course, see the contents inside the folder from any machine.
If anyone knows a proper solution to this, or has anything to say I'd really
appreciate them. Thanks in advance!
Terminal server so that other computers can launch setup file and install
the client from their computers.
The setup file is located in a computer named megadeus-dc (and yes, this is
my DC also), and the path goes like this:
c:\WINNT\system32\clients\tsclient\win32\disks\disk1\setup.exe
And I believe this is the default folder assigned to the client creator when
you install Terminal Services on Win2k server.
Now I have made c:\WINNT\system32\clients\tsclient\win32 folder a shared
folder named 'Terminal Client', and permission is give to 'everyone' group.
Problem is, when I try launching setup.exe from a client machine, the
following error message pops up.
'Cannot find file \\megadeus-dc\Terminal Client\disks\disk1\setup.exe (or
one of its components). Check to ensure the path and filename are correct
and that all required libraries are available.', where 'megadeus-dc' is my
terminal server / DC.
And on the blue title bar it says 'can't run 16-bit windows program'.
Now this could be very misleading, but I am launching the Terminal Services
client for 32-bit as you can see from the path, and from a win2k prof.
client machine.
And what really throws me off is that when I change the share name to that
of the actual folder name, which is 'win32' in this case, the problem
suddenly disappears altogether. But when I use any other share name than
the actual folder name the error message shows up.
It is only setup.exe and acmsetup.exe that doesn't work - all other files in
the same folder can be read and accessed from any client machine, which
gives me an impression that this is not the network path problem, but rather
a default path problem, if there is one, within setup.exe.
You can, of course, see the contents inside the folder from any machine.
If anyone knows a proper solution to this, or has anything to say I'd really
appreciate them. Thanks in advance!
