From: "Cliff Scott" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.16) with ESMTP id 2877212 for virtualized_ecs_users@2rosenthals.com; Mon, 14 Sep 2009 14:34:36 -0400 Received: from secmgr-va.2rosenthals.com ([162.83.95.194] helo=mail2.2rosenthals.com) by secmgr-ny.randr with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1MnGNh-00039z-Om for virtualized_ecs_users@2rosenthals.com; Mon, 14 Sep 2009 14:34:32 -0400 Received: from smtp9.trip.net ([216.139.64.9]:53557) by mail2.2rosenthals.com with esmtp (Exim 4.69) (envelope-from ) id 1MnGNZ-000764-25 for virtualized_ecs_users@2rosenthals.com; Mon, 14 Sep 2009 14:34:22 -0400 Received: from RC7A (dialup-4.225.173.197.Dial1.Dallas1.Level3.net [4.225.173.197]) (authenticated bits=0) by smtp9.trip.net (8.14.1/8.14.1) with ESMTP id n8EIYIZw083078 for ; Mon, 14 Sep 2009 13:34:19 -0500 (CDT) X-CTCH-RefID: str=0001.0A010205.4AAE8CAD.0121,ss=1,fgs=0 Message-Id: <200909141834.n8EIYIZw083078@smtp9.trip.net> Date: Mon, 14 Sep 2009 13:34:16 -0500 To: "Virtualized eCS Users Mailing List" Reply-To: "Cliff Scott" In-Reply-To: References: Subject: Re: [Virtualized eCS]Accessing network shares from guest MIME-Version: 1.0 X-Mailer: The Polarbar Mailer; version=1.25d; build=2006 X-Spam-Score: 0.0 (/) X-Spam-Report: _SUMMARY_ ** Reply to message from "Lewis G Rosenthal" on Mon, 14 Sep 2009 00:39:07 -0400 > Hmmm... Well, none of the above will work without the TAP driver, as > that's what's doing the bridging. > > My TAP driver is: > > 1-07-08 6:21p 104,557 0 ---- prot.os2 > > I also have the NetBIOS loaded to get the peer network working between two > > eCS computers. NetBIOS over TCPIP is loaded by default during install. Lewis, Before I ask more questions I want to thank you and Ed for all your time and effort to help me get this problem solved. It is much appreciated! That is the same one I have except mine says 5:21pm. Before I try installing it again let me clarify the process. I had installed it via MPTS as instructed in the readme which was basically copying the nif and os2 files to \IBMLAN\MAC and then installing the driver via MPTS including attaching the TCPIP protocol. That way it looks like another network card which would give the routing function. Your way of installing the driver manually in Config.sys, adding info to Protocol.ini sounds like the end result would be the same as using MPTS other than the fact that IBMLAN.INI isn't updated. Maybe it isn't necessary in this instance, but I know that if they get out of sync there are serious problems. Is there a problem with using the MPTS method? It seems like a safer method, but maybe that is why it isn't working here. -- Cliff eCS 2.0RC7