Remote Desktop Question

[Paul]

Hi,

Is there a way to use the Remote Desktop without an Internet
connection?

My server does have an Internet connection, but the client does not. I
would like the client to connect to the server using a modem and use
the desktop that way.

Is that possible with Windows? If not, are there other programs I can
use?

Thanks

Paul

 

[PapaFrank]

Paul do you mean Server has DSL or Cable ?

check out microsoft.public.windowsxp.work_remotely NG

 

[Paul]

Paul do you mean Server has DSL or Cable ?

check out microsoft.public.windowsxp.work_remotely NG

I'm not sure I understand why it matters. Here's what I want to do:

I have a PC that is connected to the Internet (using Cable). That PC
also has a regular modem connected to a regular phone line.

I have another PC that I want to use as the client. That PC is not
connected to the Internet at all but it does have a regular modem
connected to a regular phone line.

Is it possible to use the first PC as a remote desktop even though the
PC that I would use as a client is not connected to the Internet? I
would like to "dial up" to my first PC to use its desktop.

Thanks

 

[Sooner Al]

Yes...you can do that...Setup the XP Pro box as a RAS and you can dial directly into it...

**************************
Configure RAS on Windows XP
To configure the computer for incoming connections, follow these steps:
1.. Click Start, and then click Control Panel.
2.. Click Network and Internet Connections, and then click Network Connections.
3.. Double-click Create a new connection to start the New Connection Wizard.
4.. Under Network Connection Type, click Set up an advanced connection, and then click Next.
5.. Click Accept incoming connections, and then click Next.
6.. Click the modem from the list of devices, and then click Next.
7.. Select either of the options to allow Virtual Private Connections, and then click Next.
8.. Click to select the check boxes for the users whom you want to be able to authenticate when
the device connects to the computer, and then click Next.
9.. Make sure that the Internet Protocol (TCP/IP) check box is selected, click Next, and then
click Finish.


You modem should be setup for automatic answer. Check the modem users manual or the manufacturers
web site for help with that...

****************************
--
Al Jarvi (MS-MVP Windows Networking)


Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Bill Sanderson]

The Incoming Connections stuff (ras) should take care of setting the modem
up properly.

I'm not sure about XP, but some versions of RAS actually didn't set the
modem for auto-answer, but set it to detect rings, and then invoked an
answering routine upon detecting the rings.

One other note:

If you find the auto-answer is a problem, net start remoteaccess/net stop
remoteaccess command-line commands can be used to turn the auto-answer (or
whatever it is that actually answers the modem!) on and off, in a
scheduled or batch job.

 

[Paul]

Thanks for all the replies. I will try it.

Is there a website with instructions on how to configure RAS servers
and clients? I'll look, but it does not look too complicated.

Will I have access to the server's desktop in the same way as the
Remote Desktop Connection Windows XP offers when using the Internet?
Or are there differences between RAS and this?

Also, is the network of the server available to the client connected
using RAS?

Thanks

 

[Bill Sanderson]

It is so simple that some folks find the simplicity confusing.

Remote Desktop works the same way, but there are a couple of tips that may
help with that question and the next.

Either as part of the initial setup of the Incoming Connection, or
afterwards, go to Properties of TCP/IP of the Incoming Connection.

This allows you to choose how IP addresses are give out to Incoming client
connections.

My suggestion is to set this to give a fixed range (perhaps 5) of IP
addresses in the same subnet as the LAN the host machine is on, but outside
the range given out by whatever router or DHCP mechanism presently exists.

Note that some router DHCP's won't give out IP addresses to XP Incoming
clients, and thus you will get 169.x.y.z addresses for the connection.

So-how does this help? 1) you use the IP address as the name of the host
machine in connecting to Remote Desktop--right-click the icon for the
connection, and go to status, details to see the Server IP address.

2) If you set up the fixed range, your connection will usually get the same
address which makes connecting to RD easier.

3) If you've set up the address range correctly, and if this subnet is
different from the subnet your client machine is on, you will get access to
the rest of the network the host is on.

 

[Atlantis]

I'm not sure why someone didn't suggest to Paul that he use a crossover
cable (ports permitting) or, assuming his DSL cable connects to a DSL
Router of some sort, plug his client PC via Cat 5 into a port on the
DSL router. Thereby having a LAN.

RDC can be used as normal ... and he can share his internet connection
with his client PC.