From: "Cliff Scott" <virtualized_ecs_users@2rosenthals.com>
Message-Id: <200909142218.n8EMIZJf091491@smtp9.trip.net>
Date: Mon, 14 Sep 2009 17:18:32 -0500
To: "Virtualized eCS Users Mailing List" <virtualized_ecs_users@2rosenthals.com>
Reply-To: "Cliff Scott" <cliff185@intergate.com>
In-Reply-To: <list-2877490@2rosenthals.com>
References: <list-2877490@2rosenthals.com>
Subject: Re: [Virtualized eCS] [Virtualized eCS][eCS-Technical] VBOX question
MIME-Version: 1.0

** Reply to message from "Ed Durrant" <virtualized_ecs_users@2rosenthals.com>
on Tue, 15 Sep 2009 06:47:08 +1000

> Cliff Scott wrote:
> > ** Reply to message from "Ed Durrant" <virtualized_ecs_users@2rosenthals.com>
> > on Mon, 14 Sep 2009 14:38:03 +1000
> >
> >   
> >> That should work but only IF you can ping the eCS machines IP address 
> >> from within VBOX. If not (and I presume you can get to your Internet 
> >> router), you will need to add a route command in the router to send the 
> >> traffic from W2k-vbox that is addressed to the eCS machine's IP address  
> >> back to the internal network, where it will find the eCS machine and its 
> >> LPD server.
> >>     
> >
> > Ed,
> >
> > I can't ping the eCS machine or the one with the printer. I'm on dial-up
> > using InJoy on a separate machine for Internet access so don't have any
> > router as such, just a peer network.
> >
> >   
> Oh - then you're only option is sort out local communication from VBox 
> to the eCS host PC.

Seems as if that is the issue. If I can get the TAP driver to work without
destroying the peer network connection there is hope. So far no go.

-- 

Cliff
eCS 2.0RC7