In linux you can use socat(http://www.dest-unreach.org/socat/ - in debian you can do an apt-get install socat ;) to redirect this named pipe to a socket. In Windows there exists a tool: Named Pipe TCP Proxy Utility (http://shvechkov.tripod.com/nptp.html). Basically what you do is (the example below is done in linux (debian) but for windows the procedure is somehow the same):
- You create a serial port in your vmware configuration with the following settings:

- Use named pipe
- This is the server
- The other end is an application.
You specify the location of your named pipe, for example: /tmp/vm-serial0 - Fire up your appliance.
- You'll see the /tmp/vm-serial0 named pipe created in the host OS.
- Use socat to set up the socket listener :
socat -d -d -d /tmp/serial0 tcp-listen:9998
A listening socket will be created at localhost on port 9998. The -d parameters gives verbose logging. - Open a new terminal and do a telnet to localhost on port 9998:
telnet localhost 9998 - You're connected to the serial console of your vm'ed appliance.
