OK, I'm plowing ahead like a madman after getting the server patched.
(detours topic breifly.....the server which never even blinked nor came up
for air once in the last 3 years has self destructed 3 times since patching.
1. Compressed Exchange stores problem. I take partial blame for that one. 2.
The WINS database up and left during a routine reboot. No idea why. 3. The
server magically lost connection to all its drives today. Couldn't bring up
Device Manager, couldn't open Services. Simple reboot seems to have restored
whatever burped. And now, back to our story....)

I have searched all over with regards to Remote Desktop Sharing on Windows
2000. Some say it exists, some say it existed, some say it never happened,
some say Terminal server is the only way......blah blah blah.

I'm happy to do the research if somebody can point my silly head in the
right direction. I have VPN up and running. How do I get to use RDP to
Windows 2000 machines? I'm trying to roll out some XP machines too, but I
think that ones pretty self explanitory when it comes to Remote desktop.
(still can't solve the HORRIBLY slow network issue though....)

So there you have it, a challange for all those shiny new MVP's out there.

Can't stay clean forever! ;)

Re: Did my due Diligence by Merv

Merv
Wed Jan 28 16:38:03 CST 2004

You can't RDP (called RDC now) to a Win2K workstation (RDP is only supported
by WinXP Pro and Win2K/2K3 servers). You're choices appear to be:

Win2K
Netmeeting
VNC (with VPN for security reasons)
TightVNC (with VPN for security reasons)
PCAnywhere
Other commercial remote control apps

TightVNC with a VPN works well and is easy to set up (and free). I've had
some mouse cursor control problems with Netmeeting.

--
Merv Porter [SBS MVP]
===================================

"IBC" <it@ibcengineering.com> wrote in message
news:eH#Y7ee5DHA.2188@TK2MSFTNGP10.phx.gbl...
> OK, I'm plowing ahead like a madman after getting the server patched.
> (detours topic breifly.....the server which never even blinked nor came up
> for air once in the last 3 years has self destructed 3 times since
patching.
> 1. Compressed Exchange stores problem. I take partial blame for that one.
2.
> The WINS database up and left during a routine reboot. No idea why. 3. The
> server magically lost connection to all its drives today. Couldn't bring
up
> Device Manager, couldn't open Services. Simple reboot seems to have
restored
> whatever burped. And now, back to our story....)
>
> I have searched all over with regards to Remote Desktop Sharing on Windows
> 2000. Some say it exists, some say it existed, some say it never happened,
> some say Terminal server is the only way......blah blah blah.
>
> I'm happy to do the research if somebody can point my silly head in the
> right direction. I have VPN up and running. How do I get to use RDP to
> Windows 2000 machines? I'm trying to roll out some XP machines too, but I
> think that ones pretty self explanitory when it comes to Remote desktop.
> (still can't solve the HORRIBLY slow network issue though....)
>
> So there you have it, a challange for all those shiny new MVP's out there.
>
> Can't stay clean forever! ;)
>
>
>



Re: Did my due Diligence by David

David
Wed Jan 28 18:57:04 CST 2004

Take a look at NetOps also.
Very Fast.

Regards,
David R. Hibbelns

"Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
news:uGIseZf5DHA.2692@TK2MSFTNGP09.phx.gbl...
> You can't RDP (called RDC now) to a Win2K workstation (RDP is only
supported
> by WinXP Pro and Win2K/2K3 servers). You're choices appear to be:
>
> Win2K
> Netmeeting
> VNC (with VPN for security reasons)
> TightVNC (with VPN for security reasons)
> PCAnywhere
> Other commercial remote control apps
>
> TightVNC with a VPN works well and is easy to set up (and free). I've had
> some mouse cursor control problems with Netmeeting.
>
> --
> Merv Porter [SBS MVP]
> ===================================
>
> "IBC" <it@ibcengineering.com> wrote in message
> news:eH#Y7ee5DHA.2188@TK2MSFTNGP10.phx.gbl...
> > OK, I'm plowing ahead like a madman after getting the server patched.
> > (detours topic breifly.....the server which never even blinked nor came
up
> > for air once in the last 3 years has self destructed 3 times since
> patching.
> > 1. Compressed Exchange stores problem. I take partial blame for that
one.
> 2.
> > The WINS database up and left during a routine reboot. No idea why. 3.
The
> > server magically lost connection to all its drives today. Couldn't bring
> up
> > Device Manager, couldn't open Services. Simple reboot seems to have
> restored
> > whatever burped. And now, back to our story....)
> >
> > I have searched all over with regards to Remote Desktop Sharing on
Windows
> > 2000. Some say it exists, some say it existed, some say it never
happened,
> > some say Terminal server is the only way......blah blah blah.
> >
> > I'm happy to do the research if somebody can point my silly head in the
> > right direction. I have VPN up and running. How do I get to use RDP to
> > Windows 2000 machines? I'm trying to roll out some XP machines too, but
I
> > think that ones pretty self explanitory when it comes to Remote desktop.
> > (still can't solve the HORRIBLY slow network issue though....)
> >
> > So there you have it, a challange for all those shiny new MVP's out
there.
> >
> > Can't stay clean forever! ;)
> >
> >
> >
>
>



Re: Did my due Diligence by Merv

Merv
Wed Jan 28 19:11:03 CST 2004

OK... NetOp Remote Control

http://www.netop.com/main.asp?fl=1

"NetOps" to me has a slightly different meaning...

Network Operations (NetOps) for the Global Information Grid (GIG)
http://www.disa.mil/ops/netops.html

;-)

--
Merv Porter [SBS MVP]
===================================
"David R. HIbbeln" <dhibbeln@nospam.net> wrote in message
news:#ZEXQLg5DHA.2188@TK2MSFTNGP10.phx.gbl...
> Take a look at NetOps also.
> Very Fast.
>
> Regards,
> David R. Hibbelns
>
> "Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
> news:uGIseZf5DHA.2692@TK2MSFTNGP09.phx.gbl...
> > You can't RDP (called RDC now) to a Win2K workstation (RDP is only
> supported
> > by WinXP Pro and Win2K/2K3 servers). You're choices appear to be:
> >
> > Win2K
> > Netmeeting
> > VNC (with VPN for security reasons)
> > TightVNC (with VPN for security reasons)
> > PCAnywhere
> > Other commercial remote control apps
> >
> > TightVNC with a VPN works well and is easy to set up (and free). I've
had
> > some mouse cursor control problems with Netmeeting.
> >
> > --
> > Merv Porter [SBS MVP]
> > ===================================
> >
> > "IBC" <it@ibcengineering.com> wrote in message
> > news:eH#Y7ee5DHA.2188@TK2MSFTNGP10.phx.gbl...
> > > OK, I'm plowing ahead like a madman after getting the server patched.
> > > (detours topic breifly.....the server which never even blinked nor
came
> up
> > > for air once in the last 3 years has self destructed 3 times since
> > patching.
> > > 1. Compressed Exchange stores problem. I take partial blame for that
> one.
> > 2.
> > > The WINS database up and left during a routine reboot. No idea why. 3.
> The
> > > server magically lost connection to all its drives today. Couldn't
bring
> > up
> > > Device Manager, couldn't open Services. Simple reboot seems to have
> > restored
> > > whatever burped. And now, back to our story....)
> > >
> > > I have searched all over with regards to Remote Desktop Sharing on
> Windows
> > > 2000. Some say it exists, some say it existed, some say it never
> happened,
> > > some say Terminal server is the only way......blah blah blah.
> > >
> > > I'm happy to do the research if somebody can point my silly head in
the
> > > right direction. I have VPN up and running. How do I get to use RDP to
> > > Windows 2000 machines? I'm trying to roll out some XP machines too,
but
> I
> > > think that ones pretty self explanitory when it comes to Remote
desktop.
> > > (still can't solve the HORRIBLY slow network issue though....)
> > >
> > > So there you have it, a challange for all those shiny new MVP's out
> there.
> > >
> > > Can't stay clean forever! ;)
> > >
> > >
> > >
> >
> >
>
>



Re: Did my due Diligence by Kevin3NF

Kevin3NF
Wed Jan 28 21:38:37 CST 2004

www.dameware.com

works great for 2000/nt/xp...not at all for 98...no idea on me, xphome

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

"Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
news:eWmeoSg5DHA.2732@TK2MSFTNGP09.phx.gbl...
> OK... NetOp Remote Control
>
> http://www.netop.com/main.asp?fl=1
>
> "NetOps" to me has a slightly different meaning...
>
> Network Operations (NetOps) for the Global Information Grid (GIG)
> http://www.disa.mil/ops/netops.html
>
> ;-)
>
> --
> Merv Porter [SBS MVP]
> ===================================
> "David R. HIbbeln" <dhibbeln@nospam.net> wrote in message
> news:#ZEXQLg5DHA.2188@TK2MSFTNGP10.phx.gbl...
> > Take a look at NetOps also.
> > Very Fast.
> >
> > Regards,
> > David R. Hibbelns
> >
> > "Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
> > news:uGIseZf5DHA.2692@TK2MSFTNGP09.phx.gbl...
> > > You can't RDP (called RDC now) to a Win2K workstation (RDP is only
> > supported
> > > by WinXP Pro and Win2K/2K3 servers). You're choices appear to be:
> > >
> > > Win2K
> > > Netmeeting
> > > VNC (with VPN for security reasons)
> > > TightVNC (with VPN for security reasons)
> > > PCAnywhere
> > > Other commercial remote control apps
> > >
> > > TightVNC with a VPN works well and is easy to set up (and free). I've
> had
> > > some mouse cursor control problems with Netmeeting.
> > >
> > > --
> > > Merv Porter [SBS MVP]
> > > ===================================
> > >
> > > "IBC" <it@ibcengineering.com> wrote in message
> > > news:eH#Y7ee5DHA.2188@TK2MSFTNGP10.phx.gbl...
> > > > OK, I'm plowing ahead like a madman after getting the server
patched.
> > > > (detours topic breifly.....the server which never even blinked nor
> came
> > up
> > > > for air once in the last 3 years has self destructed 3 times since
> > > patching.
> > > > 1. Compressed Exchange stores problem. I take partial blame for that
> > one.
> > > 2.
> > > > The WINS database up and left during a routine reboot. No idea why.
3.
> > The
> > > > server magically lost connection to all its drives today. Couldn't
> bring
> > > up
> > > > Device Manager, couldn't open Services. Simple reboot seems to have
> > > restored
> > > > whatever burped. And now, back to our story....)
> > > >
> > > > I have searched all over with regards to Remote Desktop Sharing on
> > Windows
> > > > 2000. Some say it exists, some say it existed, some say it never
> > happened,
> > > > some say Terminal server is the only way......blah blah blah.
> > > >
> > > > I'm happy to do the research if somebody can point my silly head in
> the
> > > > right direction. I have VPN up and running. How do I get to use RDP
to
> > > > Windows 2000 machines? I'm trying to roll out some XP machines too,
> but
> > I
> > > > think that ones pretty self explanitory when it comes to Remote
> desktop.
> > > > (still can't solve the HORRIBLY slow network issue though....)
> > > >
> > > > So there you have it, a challange for all those shiny new MVP's out
> > there.
> > > >
> > > > Can't stay clean forever! ;)
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>