Hi,
We are running a SBS2000 network with an attached Win2k
server. We need to temporarily set up this seperate win2k
server to allow terminal server (we have a 3rd party
contractor who needs access to the server from outside our
network.) I have never run terminal server on the sbs2000
box let alone on the seperate win2k server. I'm not sure
where to start. How should I go about setting this up?
Any advice, links etc would be appreciated.

Re: Not sure where to start (Terminal Server) by Mark

Mark
Tue Feb 24 12:38:50 CST 2004

You need to do 1 of 2 things....

1) do a lot of reading on loopback policies and spend a good portion of the
day locking it down and testing it

or

3) buy a 3rd party app like AppLauncher or Citrix and lock it down that way.
Mine is about 90% cheaper and you will be running in 5 minutes.

--
Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com



"nic" <anonymous@discussions.microsoft.com> wrote in message
news:0a0b01c3fb04$47e13b90$a001280a@phx.gbl...
> Hi,
> We are running a SBS2000 network with an attached Win2k
> server. We need to temporarily set up this seperate win2k
> server to allow terminal server (we have a 3rd party
> contractor who needs access to the server from outside our
> network.) I have never run terminal server on the sbs2000
> box let alone on the seperate win2k server. I'm not sure
> where to start. How should I go about setting this up?
> Any advice, links etc would be appreciated.



Re: Not sure where to start (Terminal Server) by nic

nic
Tue Feb 24 13:14:13 CST 2004

Are you saying it would be better to provide console
control to the consultant via installing a 3rd party
application on the server (instead of setting up terminal
server etc.) Our company has WebEx which allows console
control over the web. I was somewhat hesitant to install
the client on the win2k server but it would make things
easier.


>-----Original Message-----
>You need to do 1 of 2 things....
>
>1) do a lot of reading on loopback policies and spend a
good portion of the
>day locking it down and testing it
>
>or
>
>3) buy a 3rd party app like AppLauncher or Citrix and
lock it down that way.
>Mine is about 90% cheaper and you will be running in 5
minutes.
>
>--
>Sincerely,
>Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I
4&2000
>www.MCSE2000.com
>www.AppLauncher.com
>
>
>
>"nic" <anonymous@discussions.microsoft.com> wrote in
message
>news:0a0b01c3fb04$47e13b90$a001280a@phx.gbl...
>> Hi,
>> We are running a SBS2000 network with an attached Win2k
>> server. We need to temporarily set up this seperate
win2k
>> server to allow terminal server (we have a 3rd party
>> contractor who needs access to the server from outside
our
>> network.) I have never run terminal server on the
sbs2000
>> box let alone on the seperate win2k server. I'm not
sure
>> where to start. How should I go about setting this up?
>> Any advice, links etc would be appreciated.
>
>
>.
>

Re: Not sure where to start (Terminal Server) by Javier

Javier
Tue Feb 24 13:53:31 CST 2004

Does your contractor needs access to that server (to configure something)?
or to a Terminal Server session (i.e. App Mode)?

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"nic" <anonymous@discussions.microsoft.com> wrote in message
news:0a9001c3fb0a$63845ed0$a001280a@phx.gbl...
> Are you saying it would be better to provide console
> control to the consultant via installing a 3rd party
> application on the server (instead of setting up terminal
> server etc.) Our company has WebEx which allows console
> control over the web. I was somewhat hesitant to install
> the client on the win2k server but it would make things
> easier.
>
>
> >-----Original Message-----
> >You need to do 1 of 2 things....
> >
> >1) do a lot of reading on loopback policies and spend a
> good portion of the
> >day locking it down and testing it
> >
> >or
> >
> >3) buy a 3rd party app like AppLauncher or Citrix and
> lock it down that way.
> >Mine is about 90% cheaper and you will be running in 5
> minutes.
> >
> >--
> >Sincerely,
> >Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I
> 4&2000
> >www.MCSE2000.com
> >www.AppLauncher.com
> >
> >
> >
> >"nic" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:0a0b01c3fb04$47e13b90$a001280a@phx.gbl...
> >> Hi,
> >> We are running a SBS2000 network with an attached Win2k
> >> server. We need to temporarily set up this seperate
> win2k
> >> server to allow terminal server (we have a 3rd party
> >> contractor who needs access to the server from outside
> our
> >> network.) I have never run terminal server on the
> sbs2000
> >> box let alone on the seperate win2k server. I'm not
> sure
> >> where to start. How should I go about setting this up?
> >> Any advice, links etc would be appreciated.
> >
> >
> >.
> >



Re: Not sure where to start (Terminal Server) by nic

nic
Tue Feb 24 14:46:44 CST 2004

The contractor needs access to the server (to configure a
Cisco router for a point-to-point frame relay
connection). I believe he will be primarily using a
hyperTerminal session but might need access to other
things.

I mentioned WebEx before (very similar to terminal
server). Through it I can allow desktop or application
control. It would be very easy to set up.


>-----Original Message-----
>Does your contractor needs access to that server (to
configure something)?
>or to a Terminal Server session (i.e. App Mode)?
>
>--
>Javier [SBS MVP]
>
><< SBS ROCKS !!! >>
>
>"nic" <anonymous@discussions.microsoft.com> wrote in
message
>news:0a9001c3fb0a$63845ed0$a001280a@phx.gbl...
>> Are you saying it would be better to provide console
>> control to the consultant via installing a 3rd party
>> application on the server (instead of setting up
terminal
>> server etc.) Our company has WebEx which allows console
>> control over the web. I was somewhat hesitant to
install
>> the client on the win2k server but it would make things
>> easier.
>>
>>
>> >-----Original Message-----
>> >You need to do 1 of 2 things....
>> >
>> >1) do a lot of reading on loopback policies and spend a
>> good portion of the
>> >day locking it down and testing it
>> >
>> >or
>> >
>> >3) buy a 3rd party app like AppLauncher or Citrix and
>> lock it down that way.
>> >Mine is about 90% cheaper and you will be running in 5
>> minutes.
>> >
>> >--
>> >Sincerely,
>> >Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I
>> 4&2000
>> >www.MCSE2000.com
>> >www.AppLauncher.com
>> >
>> >
>> >
>> >"nic" <anonymous@discussions.microsoft.com> wrote in
>> message
>> >news:0a0b01c3fb04$47e13b90$a001280a@phx.gbl...
>> >> Hi,
>> >> We are running a SBS2000 network with an attached
Win2k
>> >> server. We need to temporarily set up this seperate
>> win2k
>> >> server to allow terminal server (we have a 3rd party
>> >> contractor who needs access to the server from
outside
>> our
>> >> network.) I have never run terminal server on the
>> sbs2000
>> >> box let alone on the seperate win2k server. I'm not
>> sure
>> >> where to start. How should I go about setting this
up?
>> >> Any advice, links etc would be appreciated.
>> >
>> >
>> >.
>> >
>
>
>.
>

Re: Not sure where to start (Terminal Server) by Javier

Javier
Tue Feb 24 15:04:28 CST 2004

Ok... I don't know if that would be a good practice or not (I suppose it
would be ok if you really trust them). However, doing what you want is very
easy... simply publish the TS server via ISA and give them a
username/password.

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"nic" <anonymous@discussions.microsoft.com> wrote in message
news:0d3601c3fb17$5051bee0$a101280a@phx.gbl...
> The contractor needs access to the server (to configure a
> Cisco router for a point-to-point frame relay
> connection). I believe he will be primarily using a
> hyperTerminal session but might need access to other
> things.
>
> I mentioned WebEx before (very similar to terminal
> server). Through it I can allow desktop or application
> control. It would be very easy to set up.
>
>
> >-----Original Message-----
> >Does your contractor needs access to that server (to
> configure something)?
> >or to a Terminal Server session (i.e. App Mode)?
> >
> >--
> >Javier [SBS MVP]
> >
> ><< SBS ROCKS !!! >>
> >
> >"nic" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:0a9001c3fb0a$63845ed0$a001280a@phx.gbl...
> >> Are you saying it would be better to provide console
> >> control to the consultant via installing a 3rd party
> >> application on the server (instead of setting up
> terminal
> >> server etc.) Our company has WebEx which allows console
> >> control over the web. I was somewhat hesitant to
> install
> >> the client on the win2k server but it would make things
> >> easier.
> >>
> >>
> >> >-----Original Message-----
> >> >You need to do 1 of 2 things....
> >> >
> >> >1) do a lot of reading on loopback policies and spend a
> >> good portion of the
> >> >day locking it down and testing it
> >> >
> >> >or
> >> >
> >> >3) buy a 3rd party app like AppLauncher or Citrix and
> >> lock it down that way.
> >> >Mine is about 90% cheaper and you will be running in 5
> >> minutes.
> >> >
> >> >--
> >> >Sincerely,
> >> >Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I
> >> 4&2000
> >> >www.MCSE2000.com
> >> >www.AppLauncher.com
> >> >
> >> >
> >> >
> >> >"nic" <anonymous@discussions.microsoft.com> wrote in
> >> message
> >> >news:0a0b01c3fb04$47e13b90$a001280a@phx.gbl...
> >> >> Hi,
> >> >> We are running a SBS2000 network with an attached
> Win2k
> >> >> server. We need to temporarily set up this seperate
> >> win2k
> >> >> server to allow terminal server (we have a 3rd party
> >> >> contractor who needs access to the server from
> outside
> >> our
> >> >> network.) I have never run terminal server on the
> >> sbs2000
> >> >> box let alone on the seperate win2k server. I'm not
> >> sure
> >> >> where to start. How should I go about setting this
> up?
> >> >> Any advice, links etc would be appreciated.
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >



Re: Not sure where to start (Terminal Server) by anonymous

anonymous
Tue Feb 24 15:28:22 CST 2004

Thanks, that is the problem. I'm sure it is easy but I
don't quite understand (i'm not too bright). I've seen
articles on opening up ISA for TS but besides that I am
lost. Due they need to install a client app on their
machine or is it over the web? I read an article where
you installed TS and then went to
http://localhost/myconsole. I installed TS on the server
but there is no website named myconsole. (gives 404
error). Using localhost (or internal server name) isn't a
solution anyways since the consultant is outside the
network. How can he connect to our server? These might
be obvious answers but I've never seen TS work so I'm not
really clear on the steps. Thanks for your help

>-----Original Message-----
>Ok... I don't know if that would be a good practice or
not (I suppose it
>would be ok if you really trust them). However, doing
what you want is very
>easy... simply publish the TS server via ISA and give
them a
>username/password.
>
>--
>Javier [SBS MVP]
>
><< SBS ROCKS !!! >>
>
>"nic" <anonymous@discussions.microsoft.com> wrote in
message
>news:0d3601c3fb17$5051bee0$a101280a@phx.gbl...
>> The contractor needs access to the server (to configure
a
>> Cisco router for a point-to-point frame relay
>> connection). I believe he will be primarily using a
>> hyperTerminal session but might need access to other
>> things.
>>
>> I mentioned WebEx before (very similar to terminal
>> server). Through it I can allow desktop or application
>> control. It would be very easy to set up.
>>
>>
>> >-----Original Message-----
>> >Does your contractor needs access to that server (to
>> configure something)?
>> >or to a Terminal Server session (i.e. App Mode)?
>> >
>> >--
>> >Javier [SBS MVP]
>> >
>> ><< SBS ROCKS !!! >>
>> >
>> >"nic" <anonymous@discussions.microsoft.com> wrote in
>> message
>> >news:0a9001c3fb0a$63845ed0$a001280a@phx.gbl...
>> >> Are you saying it would be better to provide console
>> >> control to the consultant via installing a 3rd party
>> >> application on the server (instead of setting up
>> terminal
>> >> server etc.) Our company has WebEx which allows
console
>> >> control over the web. I was somewhat hesitant to
>> install
>> >> the client on the win2k server but it would make
things
>> >> easier.
>> >>
>> >>
>> >> >-----Original Message-----
>> >> >You need to do 1 of 2 things....
>> >> >
>> >> >1) do a lot of reading on loopback policies and
spend a
>> >> good portion of the
>> >> >day locking it down and testing it
>> >> >
>> >> >or
>> >> >
>> >> >3) buy a 3rd party app like AppLauncher or Citrix
and
>> >> lock it down that way.
>> >> >Mine is about 90% cheaper and you will be running
in 5
>> >> minutes.
>> >> >
>> >> >--
>> >> >Sincerely,
>> >> >Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5,
MCSE+I
>> >> 4&2000
>> >> >www.MCSE2000.com
>> >> >www.AppLauncher.com
>> >> >
>> >> >
>> >> >
>> >> >"nic" <anonymous@discussions.microsoft.com> wrote in
>> >> message
>> >> >news:0a0b01c3fb04$47e13b90$a001280a@phx.gbl...
>> >> >> Hi,
>> >> >> We are running a SBS2000 network with an attached
>> Win2k
>> >> >> server. We need to temporarily set up this
seperate
>> >> win2k
>> >> >> server to allow terminal server (we have a 3rd
party
>> >> >> contractor who needs access to the server from
>> outside
>> >> our
>> >> >> network.) I have never run terminal server on the
>> >> sbs2000
>> >> >> box let alone on the seperate win2k server. I'm
not
>> >> sure
>> >> >> where to start. How should I go about setting
this
>> up?
>> >> >> Any advice, links etc would be appreciated.
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>
>.
>

Re: Not sure where to start (Terminal Server) by Javier

Javier
Tue Feb 24 16:21:05 CST 2004

No problem... now that we know what you want is easier to help :-)

First of all... let's make this clear: What you want is not Terminal Server
in App Mode (which is what most people refer to when they talk about TS on a
Server) instead you want Terminal Server in Remote Admin mode. By default
Windows 2000 installs in this mode... and you don't really have to do
anything to get it working.

First thing you should do is download the RDP client to a workstation inside
the lan or use an XP Pro workstation... which has the client preloaded
(Start->Programs->Accessories->Communications->Remote Desktop Connection).
You can download the client here:
http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp

Now open the RDP client and make sure you can connect to the Win2k Server.
You will see the Win2kSrv desktop as if you were sitting in front of the
server (except for that little bar on the top).

After you do this... then the last part comes into play: Publish the server
through ISA (assuming that you are using ISA with 2 NICs). First open the
ISA console (Start->Programs->MS ISA Server-> ISA Management->Servers and
Arrays-> %servername%).

1) Create a new protocol definition for Terminal Server (using TCP 3389
Inbound)... unless you have this already (I don't think it exists for
inbound by default). Policy Elements-> Protocol Definitions-> New

2) Publish the server... you can do this by running the Server Publishing
Wizard (Publishing-> right-click Server Publishing Rules-> New-> Rule).
Follow the Wizard instructions... you will need to enter the IP address of
the Win2k Server, and select the protocol created on #1 from the list.

3) If you have a Firewall/Router in front of ISA make sure that you forward
TCP 3389 to the external interface of the SBS box.

That should be it... I hope I this is clear enough (and I'm not missing any
steps!). You can test this setup from anywhere on the internet by using the
same RDP client (which BTW is what the external company is going to use to
connect to your server).

Please post back if you have more questions... or just to let us know how it
went :-)

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>



Re: Not sure where to start (Terminal Server) by Mark

Mark
Tue Feb 24 20:44:10 CST 2004

if it is just a 1 time thing that is MUCH different!

--
Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com



"nic" <anonymous@discussions.microsoft.com> wrote in message
news:0a9001c3fb0a$63845ed0$a001280a@phx.gbl...
> Are you saying it would be better to provide console
> control to the consultant via installing a 3rd party
> application on the server (instead of setting up terminal
> server etc.) Our company has WebEx which allows console
> control over the web. I was somewhat hesitant to install
> the client on the win2k server but it would make things
> easier.
>
>
> >-----Original Message-----
> >You need to do 1 of 2 things....
> >
> >1) do a lot of reading on loopback policies and spend a
> good portion of the
> >day locking it down and testing it
> >
> >or
> >
> >3) buy a 3rd party app like AppLauncher or Citrix and
> lock it down that way.
> >Mine is about 90% cheaper and you will be running in 5
> minutes.
> >
> >--
> >Sincerely,
> >Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I
> 4&2000
> >www.MCSE2000.com
> >www.AppLauncher.com
> >
> >
> >
> >"nic" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:0a0b01c3fb04$47e13b90$a001280a@phx.gbl...
> >> Hi,
> >> We are running a SBS2000 network with an attached Win2k
> >> server. We need to temporarily set up this seperate
> win2k
> >> server to allow terminal server (we have a 3rd party
> >> contractor who needs access to the server from outside
> our
> >> network.) I have never run terminal server on the
> sbs2000
> >> box let alone on the seperate win2k server. I'm not
> sure
> >> where to start. How should I go about setting this up?
> >> Any advice, links etc would be appreciated.
> >
> >
> >.
> >



RE: Not sure where to start (Terminal Server) by anonymous

anonymous
Wed Feb 25 05:01:08 CST 2004

Or, you could just install VNC and let them access the server for the time they need to configure the router. After that, just disable or remove it. It's free and simple.

www.realvnc.or


Re: Not sure where to start (Terminal Server) by IBC

IBC
Wed Feb 25 09:20:16 CST 2004

According to the "TightVNC" web page VNC uses only 56Kb encryption for the
password ONLY, after authentication, there is no encryption. That sounds
pretty bad to me. If you use it inside VPN, you're probably OK though.

"The only really secure computer is one without a network. VNC requires a
password when a viewer tries to connect to a server. This password is
encrypted to deter snooping, but the following graphical data, the VNC
protocol, is not. In many ways, VNC is more secure than remote login
programs such as telnet where the password is and the following data are
sent in the clear as ascii characters. Many people find it perfectly
acceptable to use VNC like this behind a corporate firewall, across a VPN,
or between computers within the home. However, if the computer or network is
connected to the internet, we strongly advise the use of additional
security. See how to make VNC secure using SSH. You might want to know how
to use VNC with a firewall."


"Dennes" <anonymous@discussions.microsoft.com> wrote in message
news:B6C70890-DCA3-4569-B41B-DEF88A70D18E@microsoft.com...
> Or, you could just install VNC and let them access the server for the time
they need to configure the router. After that, just disable or remove it.
It's free and simple..
>
> www.realvnc.org
>



Re: Not sure where to start (Terminal Server) by nic

nic
Wed Feb 25 11:05:53 CST 2004

Thanks! that was very helpful. I installed the client on
an internal workstation and could connect to the server.
I also set up the server publishing rule. Two quick
questions though.
1) From outside the domain how do I connect? I know I
need to install the client on an outside computer, but it
won't know the computer name. I assume in the domain
section I supply the external IP address of our domain? I
will test it this evening at home but just want to make
sure I'm on the right track. (I just want to make sure I
don't need to first VPN or anything like that)

2) If I want to publish 2 servers (i.e. the sbs2000 and
seperate win2k server) do I need to have 2 external IP
addresses? I tried to set up 2 publishing rules but it
wouldn't allow the second. This question isn't that
important, I was mostly just curious. So in other words,
does each internal published server need a unique external
IP?

Once again thanks for explaining it so well. It makes
much more sense (I was lost before).

>-----Original Message-----
>No problem... now that we know what you want is easier to
help :-)
>
>First of all... let's make this clear: What you want is
not Terminal Server
>in App Mode (which is what most people refer to when they
talk about TS on a
>Server) instead you want Terminal Server in Remote Admin
mode. By default
>Windows 2000 installs in this mode... and you don't
really have to do
>anything to get it working.
>
>First thing you should do is download the RDP client to a
workstation inside
>the lan or use an XP Pro workstation... which has the
client preloaded
>(Start->Programs->Accessories->Communications->Remote
Desktop Connection).
>You can download the client here:
>http://www.microsoft.com/windowsxp/pro/downloads/rdclientd
l.asp
>
>Now open the RDP client and make sure you can connect to
the Win2k Server.
>You will see the Win2kSrv desktop as if you were sitting
in front of the
>server (except for that little bar on the top).
>
>After you do this... then the last part comes into play:
Publish the server
>through ISA (assuming that you are using ISA with 2
NICs). First open the
>ISA console (Start->Programs->MS ISA Server-> ISA
Management->Servers and
>Arrays-> %servername%).
>
>1) Create a new protocol definition for Terminal Server
(using TCP 3389
>Inbound)... unless you have this already (I don't think
it exists for
>inbound by default). Policy Elements-> Protocol
Definitions-> New
>
>2) Publish the server... you can do this by running the
Server Publishing
>Wizard (Publishing-> right-click Server Publishing Rules-
> New-> Rule).
>Follow the Wizard instructions... you will need to enter
the IP address of
>the Win2k Server, and select the protocol created on #1
from the list.
>
>3) If you have a Firewall/Router in front of ISA make
sure that you forward
>TCP 3389 to the external interface of the SBS box.
>
>That should be it... I hope I this is clear enough (and
I'm not missing any
>steps!). You can test this setup from anywhere on the
internet by using the
>same RDP client (which BTW is what the external company
is going to use to
>connect to your server).
>
>Please post back if you have more questions... or just to
let us know how it
>went :-)
>
>--
>Javier [SBS MVP]
>
><< SBS ROCKS !!! >>
>
>
>.
>

Re: Not sure where to start (Terminal Server) by Javier

Javier
Wed Feb 25 11:45:00 CST 2004

Good to see we are on the right track :-)

Inline...

> 1) From outside the domain how do I connect? I know I
> need to install the client on an outside computer, but it
> won't know the computer name. I assume in the domain
> section I supply the external IP address of our domain? I
> will test it this evening at home but just want to make
> sure I'm on the right track. (I just want to make sure I
> don't need to first VPN or anything like that)

You have a couple of options->

1) You can put the external IP address of your domain (what you said).
2) You can ask whomever is hosting your DNS to create a host (A) record
pointing to that IP (ie. remote.yourdomain.com). Then you use that host
instead of the IP address (purely cosmetical... but I usually don't remember
IP addresses very well).

You don't need to VPN first... actually if you VPN first you wouldn't need
to publish the server thru ISA. But you will be exposing probably more than
you want to those guys.

> 2) If I want to publish 2 servers (i.e. the sbs2000 and
> seperate win2k server) do I need to have 2 external IP
> addresses? I tried to set up 2 publishing rules but it
> wouldn't allow the second. This question isn't that
> important, I was mostly just curious. So in other words,
> does each internal published server need a unique external
> IP?

Good question! The problem is that if you cannot tell ISA to forward request
for the same port at two different computers.

However, there are several ways to do this. I think the simplest one would
be to change one of the ports on the server. So, instead of using the TS
"standard" TCP 3389... change one of the servers to 3388 (or any unused
port). The disadvantage to this is that you need to specify the port when
using the client to connect.

The previous setup doesn't require two IPs... however, I'm pretty sure that
with 2 IPs you could tell ISA to redirect requests from different IPs to
different servers and keep them on the same port. I haven't done this, but
it shouldn't be too difficult to do (at least in theory).

Finally, you can always VPN in first and connect two both servers without
doing anything fancy.

If you are interested I can research a little more on how to do any of this.
Also, check www.isaserver.org for tutorials on ISA.

> Once again thanks for explaining it so well. It makes
> much more sense (I was lost before).

No problem! Glad to help... post back if you have any questions.

Cheers,

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>



Re: Not sure where to start (Terminal Server) by kostia_artemiev

kostia_artemiev
Thu Feb 26 03:21:51 CST 2004

Why are you still using such unhandy thing as Hyper Terminal? Recently
I've found an interesting program - Flash Terminal. It is really Hyper
Terminal killer. With Flash Terminal you can chat and exchange files
via modem (including v.90, ISDN, ADSL, GPRS) and null-modem
simultaneously without Internet! You can exchange up to 255 files at
once with unlimited transfer resuming after connection break. Program
includes large amount of nice avatars.
Direct link for downloading:
http://www.qwertystudios.com/FlashTerminalSetup.zip
Direct link for Win95 version downloading:
http://www.qwertystudios.com/FlashTerminalSetup_w95.zip
Developers site:
http://www.qwertystudios.com/
More info:
http://www.qwertystudios.com/products.php.html