From: "Ed Durrant" <os2-wireless_users@2rosenthals.com>
Message-ID: <4A89C4F1.50808@durrant.mine.nu>
Date: Tue, 18 Aug 2009 07:00:33 +1000
User-Agent: Thunderbird 2.0.0.21 (OS/2/20090411)
MIME-Version: 1.0
To: OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>
Subject: Re: [OS2Wireless] More networking questions
References: <list-2813512@2rosenthals.com>
In-Reply-To: <list-2813512@2rosenthals.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Mark Henigan wrote:
> Hello Lewis:
>
> On the box with one each of a wireless and a
> wired NIC, I deinstalled the two NICs in MPTS
> but now get the message:
>
> "
> Protocol Managaer Not Installed.
> NET3406 An error occurred while opening network
> device driver NET1=NETBIOS.
>
> SYS1719:  The file C:\IBMLAN\NETPROG\NETWKSTA.200
> specified in the IFS statement on line 36 of the
> config.sys file does not contain a valid device
> driver or file system driver.
> Line 36 is ignored.
> "
>
 This is a bug in eCS (I recently raised a ticket on this) - it's been 
around a while. If you de-install a card in MPTS that uses Netbios over 
IP (or, I am guessing NetBEUI), the little popup program comes up and 
shows no cards supporting TCPBeui and when you click OK it says the 
config has been updated - unfortunately it doed not remove or Rem out 
two lines in Config.sys

DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200
and
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N

(I think if you had Netbios also loaded, it wotld probably miss this one 
as well)
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2

The work around is simple - go into config.sys and put rem space at the 
start of each of these lines.




> I would prefer not to deinstall and reinstall MPTS
> because I've had difficulty with it in the past.
> When I deinstalled the two NICs, I of course had
> to remove each protocol before removing the NIC.
> Is there something in IBMLAN.INI or config.sys
> that I should change that would likely fix this?
>
> On a second box I have the NIC loading fine
> according to the verbose boot information but then
> am stopped by:
>
>     "ioctl(SIOCAIFADDR): Invalid argument"
>
> and have to hit ENTER to continue.  I recall
> searching for SIOCAIFADDR in all of the DLLs and
> SYS and other files I could think of since it was
> likely present in ASCII text.  I found it that way
> and was able to solve a similar problem previously
> as a result.  But, I seem to have saved the
> information in that secret place where I "save" so
> much valuable material for future reference.
>
 This is an error in \MPTN\BIN\SETUP.CMD - post the contents (cut and 
paste) here and we'll sort out what has to be changed. Alternatively, if 
this second system is running Netbios or TCPBEUI, the cleaner way to fix 
up all the files is to run laninst.exe which is in \ibmlan\install, go 
through the tailored route and check everything is set as you want it. I 
also normally also go then into TCPCFG2 and check also that the correct 
TCPIP ports are configured as I want them. A reboot after these two 
steps and "normally" everything is OK.

> Any thoughts?  Or, have I provided far too little
> background information?
>
> TIA,
>
> - Mark
>
> Mark Henigan


-- 
Cheers/2

Ed

Checkout my eComStation Australia Podcasts 

Search on eComStationAustralia in iTunes or set up Thunderbird to look at http://eComStationAustralia.podbean.com/feed or simply go to the webpage http://eComstationAustralia.podbean.com 


Don't miss the tenth Warpstock Europe at Stralsund, Germany 12-15 November 2009 check out - http://www.warpstock.eu for details.
(I will be presenting on Virtualisation and eCS at the conference).