Chuck Stuettgen wrote:

I am getting the following error trying to start a client in vmware. Could not init font path element tcp/172.16.92.1:7100, removing from
list.

server error: could not open default font 'fixed'



LTSP is running as a VM on SUSE 9.3
The client is also running as a VM.
Ok,

Some types of traffic between VMWare guest machines may be problematic.

Some limits I should mention about VMWare. I probably painted it as a really cool solution before without any warts. One odd problem I've found with VMWare is that sometimes the guest OS exhibits difficulties communitating over TCP/IP to the host OS's servers - EXAMPLE: My Host OS, Mandriva Linux 10.1's Samba daemon is reachable by win98 & winXP guest OS's but it somehow fails when retrieving large files. My workaround was to have another linux box act as a "reflector" for Samba. So the reflector (a real machine on the network) mounts the samba share then exports it via samba, then the guest OS connects to the share on the reflector.

So, some testing of the network connectivity between these two VMWare Virtual guest hosts may be in order.

Also, you might try using fonts over NFS instead of using the font server approach

   USE_XFS = N

as Jim pointed out in an earlier message.

-Joe Baker




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
     https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to