Page 1 of 2 12 LastLast
Results 1 to 10 of 14
  1. #1
    falvrez
    Guest

    Default Terminal Server - 2 problems...

    Afternoon all

    Have recently installed terminal server on our windows 2000 server, running, funnily enough, Windows 2000 server.

    The user at the remote site can access the accounting program that she wants to no problem but there are two issues which I can't find an immediate solution for:

    1: She can't print to the printer on her own network. At this building (where the server is located) we are running a domain, but at her building they are running a peer to peer network.

    As I say she can log in with terminal server but I can get her access to the printer on her network.
    I have been through the steps of having her log in to terminal server, then me on the server going through the add printer process - but the ports only show any locallly installed printers that she has (which is zero). If she does log on to ternminal server then (if I install a dummy local printer on her PC) the new printer appears automatically on the server as a new printer with the session open.

    According to all I have read on the MS website, "Terminal Services provides printer redirection, which routes printing jobs from the terminal server to a printer attached to the client computer or to a network printer available to the client computer."
    Oh yeah? How...? Am I missing something here?

    2: I can't get her removable USB drive to log on as a mapped drive. She wants to be able to back up the accounting program direclty to her PC when she is running terminal server so that she can xsfer the data to her laptop, but when she goes to backup only the local drives appear, even thouh I have mapped her removable drive into the server first.\
    And yes, all settings for terminal server configuration are set correctly (well, as far as I can see).

    Any ideas/

    All help gratefully accepted, even abuse

  2. #2
    Graham L
    Guest

    Default Re: Terminal Server - 2 problems...

    At a guess, a peer-to--peer network isn't a network by even Microsoft's standards. (It's a totally insecure thing you have when you don't have a network.)

    That's likely to be the printer problem. How does she connect to your network? Does the P-P group share the same Ethernet ? It might be simplest to hang a printer server to the printer, and have the Terminal Server server own it.

    I suspect dynamically changeable hardware might be a security problem too. But I don't know. ;-) Can't she live with backing up to her hard disk, then whacking the files to the USB device when not being a Terminal?

  3. #3
    nzStan
    Guest

    Default Re: Terminal Server - 2 problems...

    > 1: She can't print to the printer on her own network.
    > At this building (where the server is located) we are
    > running a domain, but at her building they are
    > running a peer to peer network.

    Is the printer running off a jetdirect print server or as shared printer on a workstation? If using a print server then you will need to install the print server software on the terminal server eg HPJetdirect/NetGear/Dlink etc. Once the print server software is installed on the server then as long as your server's print spooler can see the printer, your users should be able to print to it.

    If she is sharing the printer off her workstation then the printer need to be shared with the right permissions to allow the Terminal Server to spool to it.

    > 2: I can't get her removable USB drive to log on as a
    > mapped drive. She wants to be able to back up the
    > accounting program direclty to her PC when she is
    > running terminal server so that she can xsfer the
    > data to her laptop, but when she goes to backup only
    > the local drives appear, even thouh I have mapped her
    > removable drive into the server first.\
    > And yes, all settings for terminal server
    > configuration are set correctly (well, as far as I
    > can see).
    Did you share her removable USB drive? Then you should be able to map to the shared drive name.


    I'll hold off on the abuse. Good luck.

  4. #4
    falvrez
    Guest

    Default Re: Terminal Server - 2 problems...

    Thanks for the quick responses Graham and Stan

    >That's likely to be the printer problem. How does she connect to your network? Does the P-P group share the same Ethernet ? It might be simplest to hang a printer server to the printer, and have the Terminal Server server own it.

    Yes PP network are all on the same ethernet and workgroup. I don't think hanging a printer server to the printer will help as the problem is that TS doesn't seem to recognise *any* networked printers (even it's own when running in TS).


    >Is the printer running off a jetdirect print server or as shared printer on a workstation?
    It's shared off a workstation. I realise that drivers may be a problem if the same drivers were not available to the server, but the server itself has access(and is installed) to exactly the same make and model of printer at our end of town.

    >If she is sharing the printer off her workstation then the printer need to be shared with the right permissions to allow the Terminal Server to spool to it.
    Not sure what you mean here Stan - she has permission to share the printer (it is her default) or do you mean that the TS server needs to have permission access to the network printer at the client end?

    >Did you share her removable USB drive? Then you should be able to map to the shared drive name.
    Yes and added permissions which I was I'm not sure why she can't see it over TS...direclty at the server the drive is visible but from her end, no..

    Thanks again.

  5. #5
    nzStan
    Guest

    Default Re: Terminal Server - 2 problems...

    Feels like a network security/authentication problem so I'll throw in a wildcard.

    Try naming the workgroup the same as your terminal server domain????

    or

    If possible make your workstations login to the same domain as the Terminal Server.

    What workstation are we talking about btw, are they W2K, NT, W98, W95, WFWG311?

    I have a W2K server runing TS (30 users) and a mixture of client PCs from 98 to W2K. Most printers are working off print servers and a couple are shared printers (deskjets) off a couple of workstations.

    Also have a Citrix Terminal server for 50 users but Citrix handle all the local printers and drives seamlessly.

  6. #6
    falvrez
    Guest

    Default Re: Terminal Server - 2 problems...

    Hi Stan

    Will try renaming workgroup on Monday.
    Re making workgroup client login to domain - would be nice, but have yet to work it out! Am sure I am doing everything right but there is no way the client PC (wink2k) wants to find teh domain server for some reason....blowed if I know why.
    That's why the easy and quick solution was to install TS and run that - and hey it does work well, except for this printer and drive issue.

    It sounds as though you have a similar setup to mine - how many clients log into your PC through TS, and for what purpose? (if you don't mind me asking of course). Do any of the clients who are using TS print to a local (networked) printer that's not attached to their PC?

  7. #7
    nzStan
    Guest

    Default Re: Terminal Server - 2 problems...

    > It sounds as though you have a similar setup to mine
    > - how many clients log into your PC through TS, and
    > for what purpose? (if you don't mind me asking of
    > course).
    The new W2K TS is running a specialist application (umm lets call it inventory control, but a very complex one). All users have to log in to the TS to run the application cos we can't be stuffed going around 30 PCs updating the application everytime the vendor send us an update.

    > Do any of the clients who are using TS print
    > to a local (networked) printer that's not attached to
    > their PC?
    All our printers use HP Jetdirect print servers (or built in JD network card). A bit pricey but they work like a charm and worth the money. I have one lady who has a HP Deskjet on her PC which is shared and is used by others to print color outputs.


    To set up your W2K PC to join a domain try

    Start, Control Panel, Settings, System,
    Network Identification, Properties and change it to Domain


  8. #8
    falvrez
    Guest

    Default Re: Terminal Server - 2 problems...

    >To set up your W2K PC to join a domain try

    Um yeah I'm a little (way!) past that...

    I need to change the settings on the client so it knows where to look for the DNS server (which is remote over VPN).
    So I have changed the client's IP settings to relect the ip address of the DNS server and *then* gone into "Network Identification, Properties and change it to Domain" etc but network connection can't seem to find the DNS server even though I can ping it and of course I'm running TS on the client to the DNS server.
    On the local network it is of course so easy to join the doman but over the VPN is where I'm hainvg problems,
    Have tried temporairy disconnecting both hardware firewalls but no change - and if I can ping teh machine surely this would not be an issue?


  9. #9
    Marshell
    Guest

    Default Re: Terminal Server - 2 problems...

    Technet says the following

    Print Terminal Server Applications to Local Printer
    Terminal Services provides printer redirection which routes print jobs from the terminal server to a printer that is attached to your local computer. There are two ways to provide access to local printers: automatic and manual printer redirection. Use manual redirection when your local printer requires a driver that is not available on the Windows 2000 Server. To print to your local printer from programs that are running on the terminal server, use the appropriate method.

    back to the top
    Automatic Printer Redirection
    Printer redirection is automatic when the local printer uses a driver that is installed on the Windows 2000 server. When you log on to a session on the terminal server, any local printers that are attached to LPT, COM and USB ports and that are installed on the client computer are automatically detected and a local queue is created on the server. The client computer printer settings for the default printer and some properties (such as printing on both sides of the page) are used by the server.


    When a client disconnects or ends the session, the printer queue is deleted and any incomplete or pending print jobs are lost. Information about the client's local printers and settings are saved on the client computer. On subsequent logons, the printer queue is created by using the information that is stored on the client computer.


    If a printer driver is not found on the server, an event is logged and the client printer is not created. To make the printer available, the driver must be manually installed on the server.


    back to the top
    Manual Printer Redirection
    Printers that are attached to LPT and COM ports on the client's local computer can be manually redirected, although manual redirection of printers that are connected through USB ports is not supported.


    To manually redirect a client printer, contact your administrator and provide the name of your computer (or IP address for a Windows-based terminal). The client must be connected to the terminal server during manual redirection.


    After the initial manual redirection, printers will be automatically redirected during subsequent logons.


    NOTE: Redirected printers are available for use with applications running on the server. Redirected printers appear in the Printers folder in Control Panel and are named in this format: Client Printer Name/Client Computer Name/Session Number.

    When you disconnect or log off from a session, the printer queue is deleted and incomplete or pending print jobs are lost.

  10. #10
    falvrez
    Guest

    Default Re: Terminal Server - 2 problems...

    Thanks for the response, Mike.

    >Print Terminal Server Applications to Local Printer
    Terminal Services provides printer redirection which routes print jobs from the terminal server to a printer that is attached to your local computer. There are two ways to provide access to local printers: automatic and manual printer redirection. Use manual redirection when your local printer requires a driver that is not available on the Windows 2000 Server. To print to your local printer from programs that are running on the terminal server, use the appropriate method.


    This same info is on one of the MS pages, but it doesn't help at all.
    Sure, if I load a dummy (local) printer driver on the client, and that client logs into TS, then their local printer appears on the TS server as a new printer, and drops off when they log out of TS. This is, as it says in your info, how is it supposed to work.

    But the problem is that the client has no local printer - just the default network printer that she uses. The TS server does not "see" her default (on the network) printer, even though on the same TS webpage it says "Terminal Services provides printer redirection, which routes printing jobs from the terminal server to a printer attached to the client computer or to a network printer available to the client computer."

    Same scenario when I use manual redirection.

Similar Threads

  1. .pdf creation on Terminal Server
    By nofam in forum PressF1
    Replies: 11
    Last Post: 22-02-2008, 01:21 PM
  2. HELP. Windows server 2003 + Terminal Server
    By cityhunter2000 in forum PressF1
    Replies: 0
    Last Post: 12-08-2005, 12:36 PM
  3. HELP Terminal server with Jetstream
    By cityhunter2000 in forum PressF1
    Replies: 11
    Last Post: 12-08-2005, 11:45 AM
  4. Terminal server
    By smale in forum PressF1
    Replies: 1
    Last Post: 08-03-2003, 05:42 PM
  5. Replies: 0
    Last Post: 18-06-2001, 10:35 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •