RE: Local Devices
"C. Falconer" <[email protected]>
| Newsgroups | gmane.linux.pxes.devel |
|---|---|
| Organization | Avonside Girls' High School |
| Message-ID | <[email protected]> |
Yes - that is a function of DHCP and DNS... Its not really related to the PXEs config at all. If you allocate a static IP for each machine you want to access, then enter that IP/name into your DNS server then users can refer to \\name\fd Unfortunately I can't think of an easy way to do a generic \\thismachine\fd You don't really want a huge list of links to "floppy drive on workstation 1/2/3/...." -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Pickup, Jordan Sent: Thursday, 29 April 2004 2:17 p.m. To: [email protected] Subject: [pxes-devel] Local Devices I have set up PXES 0.8-9 to connect to via RDP to a windows 2003 server. Everything is working great. When connected to the server, I have managed to connect to my local devices via the fd, hd, cdrom, and flash shares using network paths like \\172.20.2.39\fd, where 172.20.2.39 is the IP address of the thin client computer, and logging on to the share as root. Is there any way to refer to the client by name, instead of by IP? I would like to auto-map the devices to a drive letter (or at least provide the users with instructions on how to map them), but it is difficult if they have to find their IP first. It would make sense if there was a name mapped to the thin client computer, but I've tried guessing and searching the mailing list with no success. I would like a method to access the floppy drive that I could use from all of my PXES thin clients. Is there such a method? ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149&alloc_id66&op=click