RE: Windows Server 2000 SQL

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Patrick Rouse [MVP] (anonymous_at_discussions.microsoft.com)
Date: 02/24/04 

Date: Mon, 23 Feb 2004 21:11:06 -0800

All you need to do is install the Remote Desktop "Client" on the computers that will be logging onto the Terminal Server. It can be downloaded here:

http://www.workthin.com/tsdown.htm

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
     
     ----- jfox wrote: -----
     
     I am putting up and running a Microsoft Small Business
     Server 2000 with SQL and Terminal Services using a
     wireless network.
     
     I also have an old Novell 4.10 network using an ethernet
     BNC (thin net) daisey chained network.
     
     The MSNSB server is working okay and has workstations
     running Windows 2000 Pro in its network. The Novell
     server is working okay and has workstations running
     Windows 95, 98 SE, and 2000 Pro in its network.
     
     I have four machines that are in the Novell network in
     which I have installed wireless network cards in addition
     to their thin net BNC cards. These workstations can "see"
     the new network server and through the wireless router
     have access to the internet over the wireless network. I
     tried to install Terminal Services on one of the machines
     running Windows 98 SE and it erred out saying it either
     did not have enough memory or disk space - both not true
     7.8 gig or disk left and 97% of 384 MB of RAM free.
     
     We are moving installing a completely new software package
     that runs in Terminal Services mode on the MSNSB network
     replacing most everything on the Novell network. I would
     like to be able to access both networks from all the
     machines during the training and transition period.
     
     What must I do to enable this? The documentation says to
     refer to Windows 2000 Server documentation - I cannot find
     anything mentioned in any documentation I have.
     
     My thoughts were to install Terminal Services on the
     machines currently in the Novell network and install
     ethernet BNC cards (I found some PCI cards) in the
     machines currently on the MSNSB network. Not being able
     to install Terminal Services on the 98 SE machine has
     stalled that plan and I cannot seem to find anyone with
     knowledge to get around the problem.
     
     Any thoughts would be appreciated.
     

Relevant Pages

  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • Re: network slows down after SP2 install
    ... These machines cannot even run the program locally being disconnected from the server with a local copy of the database. ... Install SP2 for WIN XP and latest service pack for Office 2003 on ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: network slows down after SP2 install
    ... the machines updated from W2K still open and read the ... Locate the "Microsoft network server: ... Install SP2 for WIN XP and latest service pack for Office 2003 on ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Vista, SBS 2003 and RAS not working
    ... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.windowsxp.network_web)