Kris Steenhaut wrote:

> 
> 
> David Eckard schreef:
> 
> 
>>Double check your MPTS setup.  You should see the nic listed with TCPIP as
>>one of the protocols.  IP is IP.  Software vs Hardware shouldn't matter. 
>>You might have ISDNPM still hanging around and interferring.
>>
>> 
>>
> 
> Indeed! David, you're right on spot!
> 
> 
> The nic still was bound to the ISDNPM protocol PPPEMYWI.OS2.
> 
> So I'd freed the nic from everything, rebooted and bound the nic to IBM 
> tcp/ip. Ran tcpcfg2,
> and, as Sid told us:
> 
> 
>>It was set up to the extent that I had clicked on 'Enable interface' and 
>>'Get an address automatically' on the first page of the TCP/IP 
>>configuration network.
>>
> 
> 
> for lan0, I clicked on "enable interface" and
"Automatically, using 
> DCHP". Save and exit (incidentally, the system reboots automagically 
> when you dare to change anything) ...
> 
> Now, after the reboot: still nothing, meaning no connection.
> 
> I had the lucky punch to open immediately the file setup.cmd. Ugh !? No 
> "dhcpstrt -i lan0" present.
> OK. Ran once more tcpcfg2, "enable interface" +
"automatically, using 
> DHCP" checked on, save and the mandatary reboot.
> After, still no "dhcpstrt -i lan0" present in setup.cmd.
> 
> In the mood of total despair I ran then "dhcpstrt -i lan0"
from command 
> line ... lights on router and nic began flashing .... started mozilla, 
> to http://192.168.2.10, and yes, suddenly I landed in the plain 
> internals of the router.
> 
> To be short: in tcpcfg2 "enable interface" MUST NOT be
checked on, only 
> "automatically, using DHCP" has to be checked on.
> 
> Well, I have to agree, once all the trouble is over, it's easy. All the 
> more as my telecom and provider's (Belgacom and skynet.be) data already 
> are stored in the router. So, further on I had nothing more to to than 
> to enter my user name and type the password twice.
> 
> 
> It is remarkable how much faster my dsl acts now with the router 
> compared to ISDNPM. So, indeed, with the prices of routers dropping 
> down, it's better to spend of few more of euro on a router.
> 
> A big thank you to everyone who cared to suffer along with me.
> 
> .... But the saga hasn't come to his end yet.
> 
> My main computer (setup.cmd main computer):
> 
> ifconfig lan0 192.168.0.1 netmask 255.255.255.0 metric 1 mtu 1500
> 
> was connected to my laptop (setup.cmd laptop)
> 
> ifconfig lan0 192.168.0.2 netmask 255.255.255.0 metric 1 mtu 1500
> 
> By means of a wired connection to a second nic at the main computer (the 
> first nic being bounded to isdnpm & PPPEMYWI.
> 
> Questions:
> 
> 1. How can I establish a wired connection over the router?
> 
> 2. After success with 1., how can I connect the laptop ( TP 41) wireless 
> to the router (I do have a jacaranda blue pcmcia card) and over the 
> router to the main PC.
> 
> 3. What are my best bets to make the whole lot as wireless as possible?
> 


Now, your first step is to Backup your setup.cmd and related files, AND 
DOCUMENT What you did.  So you can fix it Next Time, because there WILL 
be a Next Time!!!

MarkO



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/E8folB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2user/

 To unsubscribe from this group, send an email to:
    os2user-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 




---