Prev: NIC Having Multiple IP Addresses?
Next: Problem with hardcoded NFS mount point
From: sealtechnologies on 31 Jul 2006 00:43
Hi:

We have implemented a thin client setup in our office. There is a
terminal server runnning win server 2003 std edition and 5 client
machines. All of them are on the same network and subnet by a switch.
The IP address of the terminal server is 192.168.0.1 while the client
machines get theirs via DHCP (from the terminal server machine), given
range is 192.168.0.11 to 192.168.0.15. This setup works wonderfully,
with all client machines able to connect to the T.S. via RDP and run
all applications that are on the terminal server superbly and even
accessing internet.

Once in a while, the client machines (after getting the boot files from
the local T.S.) need to connect via RDP to a terminal server outside
the network, of I.P. address, say, 203.220.19.89. This does not happen
and the message displayed is "network not available" :(

Could someone please help? Thanks.

Regards,

From: Michael Heiming on 31 Jul 2006 01:36
In comp.os.linux.networking sealtechnologies(a)gmail.com:
> Hi:

> We have implemented a thin client setup in our office. There is a
> terminal server runnning win server 2003 std edition and 5 client
> machines. All of them are on the same network and subnet by a switch.

How is this related to linux?

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry(a)urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 108: The air conditioning water supply pipe
ruptured over the machine room
 | 
Pages: 1
Prev: NIC Having Multiple IP Addresses?
Next: Problem with hardcoded NFS mount point