Linux/Remote Desktop Connection question

[Kenazo]

We have a Windows 2003 terminal server set up in the office, and I'm wondering if there isn't a way to get all the local computers to run linux and thus save a substantial chunk on operating costs. Right now any new computer we add we're buying WinXP Pro for it, which adds a lot to the cost of an otherwise cheap computer (no need for good systems here)

 

[EmperorRob]

Have you tried tsclient and rdesktop?

 

[FoBoT]

yes, rdesktop is included with red hat, it works great
also , there is a cd linux distro that will boot up a PC directly into a RDP session, you can either pre-populate the windows server info or the user can enter it on boot up. so you could use a slow PC with just a CD drive and no hard drive if you are only remoting into a windows server

 

[Kenazo]

Originally posted by: FoBoT
yes, rdesktop is included with red hat, it works great
also , there is a cd linux distro that will boot up a PC directly into a RDP session, you can either pre-populate the windows server info or the user can enter it on boot up. so you could use a slow PC with just a CD drive and no hard drive if you are only remoting into a windows server

The option of just using a crap computer w/ a CD drive could be quite tempting. We have tons of old 300mhz era computers that we could revitalize a little and put into service. Thanks for the info.

Do you happen to know which distro would fit the bill for that?

<-Linux newb.

 

[FoBoT]

i have a copy of the CD at home, i used to carry one in my laptop bag, but i don't see it. let me see if i can find it on

http://distrowatch.com/

i remember it start with a "P" and is an acronym or something

 

[Kenazo]

PHLAK?

 

[FoBoT]

here it is

http://pxes.sourceforge.net/

http://pxes.sourceforge.net/features.html

http://pxes.sourceforge.net/presentations/PXES-10000_feet_overview/index.html

 

[jfall]

I do a decent amount of server admin work on many different Windows boxes, always use rdesktop and never had a problem

 

[Kenazo]

So this pxes distro, will it let me bring local disk/cd-roms to the remote desktop, like the Remote Desktop client provided by Microsoft?

 

[Kenazo]

Anyway, more questions. Keep in mind I'm a complete linux newb.

Here's How my remote desktop connection is set up (on winxppro):

computer: termserv
username: kenazo
password: whatever
domain:

There is no domain listed in the connections options. Of course when the Terminal Server 2003 window pops up it has a domain listed there.

Now, when I'm booting off the PXES disk, it prompts me for the following (after having chosen RDP as my bootup type)

Terminal Server Name [wts]:
Domain:
Color depth [8]:


So, I enter "termserv", since that's our terminal server's name per the windows clients, color depth I did 8, and Domain i left blank.

Then I get the following:
Terminal Server Name [wts]:
Domain:
Color Depth:
Extra Options[-s="com1;/dev/tts/0"]:

Again I enter termserv/nothing/8/nothing


I then end up at a GUI and get a warning message with the following:

Warning:
Cannot resolve DNS name "termserv" in rdesktop.sh.

NSLookup:
nslookup:termserv:host name lookup failure

Resolver:
nameserver: 192.168.0.21

So, looks like it's not finding the "termserv" computer that the same computer, when it runs windows has no problem finding. Is the nameserver blocking linux clients from attempting to connect to it? How would I remedy this?

Thanks in advance.

 

[Kenazo]

Anyone know what i did wrong?

 

[Childs]

You are specifying a name, but your dns server cacn't resolve it. Try using the IP address, or add a host record to your dns server for termserv.

 

[Kenazo]

Why can the computer resolve it when it's running Windows then? Wouldn't it be unable to find it under windows as well, or does Linux do things differently?

 

[Childs]

Originally posted by: Kenazo
Why can the computer resolve it when it's running Windows then? Wouldn't it be unable to find it under windows as well, or does Linux do things differently?

Because in Windows you are probably using smb to browse your network. Depending on how your network is set up, you maybe using something like a WINS resolver. The Linux software you are using most likely is not using smb.

Another thing to do is simply put the windows machine's IP address in your Linux hosts file. The linux machine needs to know where the name termserv is. The networking mechanism for linux and windows is the same, its just that windows is set up to talk to other windows machines easier than it does with other OSes. Now, when you're Windows machines aren't on the same subnet, and you don't have your DNS setup, you will run into the same situation you are facing when connecting to the linux box. That is, you need to be able to resolve names to IP addresses, or simply use the IP addresses.

 

[Kenazo]

Awesome! I don't know why I didn't think of just using the IP. d'oh.


Two new questions...

1. My screen refresh rate within the RDP window feels to be about 60hz (giving me a headache). How do I change the refresh rate in Linux?

2. How do I get the floppy and CD rom from my local machine into my termserv session? When I configure the RDP session there are a wack of options however, none of them really address how to get my local drives onto my session.


Thanks!