Disconnection

  • Thread starter Thread starter DAVID
  • Start date Start date
D

DAVID

Hello everybody,

In my life, i have done 5 differents installation of
Windows 2000 with terminal server. 3 of them works very
well, 2 does not work. Every installation is the same: an
IBM server with W2k, Zyxel routers and ADSL line.
In the first of the 2 installations that failed, i have
tried everything: last service pack, keep alive mechanism,
disconnection settings, etc I have try lots of solutions
for months and months In the last installation that
failed, i have tried nothing because the first one is for
me a nigthmare (we have finaly lost the customer because
of this !!!!).

So now here is the question: i have analyse the 2
installations that failed: they have something in common:

Both systems are win NT4 server upgrade to W2k server !!
All pure w2k system works fine !!!! So maybe someone got
the solution ? Should i install a full w2k server to
resolve ?

Thanx very much.
 
An upgrade install is always a nice thing to do, but
according to the best practices, you should always do a
normal install with a fresh disk for the best results.
For all you know, the previous admin on those NT machines
may have done some really funny things with their systems,
which would have caused a problem during the upgrade.

-M
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Disconnected sessions 1
Moving W2K3 TS CAL from W2K to a W2K3 server 1
License Server 2
Installa TSE 1
upgraded xp from home to pro 2
Whoops!! 3
Don't see local printers 1
Network Powerline 3

Back
Top