| Subject | : | TCP not connected to my NIC |
| Author | : | kif kim@foder.dk |
| Date | : | 13 Sep, 2004 on 22:10 |
| Hi For almost a year now, I have been trying to get my OS2 to connect to my linux, and it is becomming rather embaresing, as I have no problem configuring W****** and linux for network, but my prefered os I cannot configure ! My NIC has been tested on Linux & W****** without any problems, and the cable too. The NIC is detected by the driver while booting, and the driver detects my lan speed (100 mbs). But when the MPTSTART.CMD calls INETWAIT, it just times out, and afterwards I cannot ping my linux. When I execute mptn\setup.cmd, I get my loopback and the routings, but nothing happens on the network (no led flashes) and ping reports all packets lost ! I'm using w4, latest fixpack,, latest tcp/ip stack, and Realtec 10/100 NIC. Any ideas ? Thanks Kim Foder |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | dljone9 dljone9@os2world.com |
| Date | : | 13 Sep, 2004 on 23:27 |
|
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | warpcafe warpcafe@yahoo.de |
| Date | : | 14 Sep, 2004 on 16:00 |
...and your x:\ibmcom\protocol.ini just to make sure that no "stupid" error went into it from somewhere... Greetings |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | kif kim@foder.dk |
| Date | : | 14 Sep, 2004 on 19:53 |
| setup.cmd : ------------ protocol.ini : ----------- DRIVERNAME = PROTMAN$ [IBMLXCFG] tcpip_nif = tcpip.nif [tcpip_nif] DriverName = TCPIP$ [NONETADP_nif] DriverName = NULLNDS$ [RTL8139_nif] DriverName = RTSND$ Hope you can see any problems ! Kim Foder |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | dljone9 dljone9@os2world.com |
| Date | : | 14 Sep, 2004 on 20:41 |
| Is your router really at 192.168.0.0?? If it was a DSL/Cable router, I would think it might be 192.168.0.1. Perhaps then your setup.cmd might look like this: route -fh |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | kif kim@foder.dk |
| Date | : | 14 Sep, 2004 on 21:20 |
| Thanks for the input. >Is your router really at 192.168.0.0?? OK, I may have been a bit unbclear on that point ! I have no router, I'm trying to connect my os2 and my linux directly via an crossover-cable (tested and functioning). The Linux is 192.168.0.1, the OS/2 is 192.168.0.2. When I ping 192.168.0.2 from my linux, the led flashes on the nic. when I ping 192.168.0.1 from my OS/2, nothing happens ! >If it was a DSL/Cable router I'm not investing in DSL before I am shure I can get my OS/2 to use the nic ! >route add default 192.168.0.0 192.168.0.1 -hopcount 1 Doesn't do any difference ! Kim Foder |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | dljone9 dljone9@os2world.com |
| Date | : | 14 Sep, 2004 on 22:05 |
| Oh yes, a crossover cable would make the changes I suggest quite useless ![]() Perhaps in this situation - OS/2 needs to act as it's own router. Also, your protocol.ini indicates you have TCP/IP bound to the |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | kif kim@foder.dk |
| Date | : | 14 Sep, 2004 on 23:54 |
| HI >plugging in the system's IP in the route statement...or even Same result in both situations ! I have tried "ifconfig lan0 down" and then "ping 192.168.0.1" then ping tells me that the network is down. After "ifconfig lan0 up" when I ping, it just hangs until I stop it. Under no curcumstances do the activity ledon the nic flash ! >do you also have a null modem cable configured All I have is my internet dial up, and local loop back (127.0.0.1). |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | dljone9 dljone9@os2world.com |
| Date | : | 15 Sep, 2004 on 03:13 |
For myself, I would go back into MPTS.EXE and remove TCP/IP |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | warpcafe warpcafe@yahoo.de |
| Date | : | 15 Sep, 2004 on 10:34 |
| Folks, "route add default 192.168.0.0 ....." Linux uses 192.168.0.1 If there is no device/machine using that adress, so why should that "route default" work at all? Where do you expect the packets to arrive? As TCP/IP is bound to both the nullmodem and the NIC, run tcpcfg2 to see if your NIC is the "lan0" device (or: check if the NIC was assigned the 192.168.0.2 adress) maybe somthing messed up here. Good luck. |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | kif kim@foder.dk |
| Date | : | 15 Sep, 2004 on 21:07 |
| Hi >As TCP/IP is bound to both the nullmodem and the Ok, I have now removed the nullmodem, and that made a differance ! Now I cannot do anything with lan0, no ifconfig and no route ! But, while looking around I may have found something : In c:\ibmcom\lantran.log I found the following : ------------ Loading Realtek Fast Ethernet Network Adapter driver (3.23vk) [2003-01-27] Any ideas what this means (I understand TCPIP is not connected to RTL8139.nif, but why not) ? For some reason "help PRO0022" cannot find the pro.msg file, even though the path are in dpath ! Kim Foder |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | dljone9 dljone9@os2world.com |
| Date | : | 15 Sep, 2004 on 23:54 |
My OS/2 box says, when posed with the "help PRO0022" Perhaps someone else here has a short-cut here for you... |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | kif kim@foder.dk |
| Date | : | 16 Sep, 2004 on 10:59 |
| Hi >My OS/2 box says, when posed with the "help PRO0022" Ok, should I uninstall anything first, or just re-install MPTN ? KimFoder |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | warpcafe warpcafe@yahoo.de |
| Date | : | 16 Sep, 2004 on 11:16 |
Hi fellow investigators, ![]() yeah - that networking subsystem sometimes gets screwed up on configuartion changes. That's sad but true. One question of mine regarding the lantran.log output: If i'm wrong on the NIC - forgive me. I suppose the problem to be related to MPTS. If so, your protocol.ini entries might be messed up. In this case, there's 2 ways of getting it to work: But first we need to check what you actually need: Greetings |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | kif kim@foder.dk |
| Date | : | 16 Sep, 2004 on 21:37 |
| HI again The probelm has been solved ! A long time ago, I was trying to get the on board intel nic to work (maybe its time to try again ?), the driver complained of some undefined resource conflicts. Assuming the conflict was in the IRQ I changed it from 11 to 13. It didn't solve my problem, but for some reason i kept it ! The other day Thomas commented on the wierd IRQ, and today I tried to change it back to the original IRQ 11,. Now everything is functioning as expected (and hoped ;o) Now I have some interesting time ahead of me as I explore Linux servers and NETBUI on OS/2 ;o) Thanks for the great work ! Kim Foder |
| Subject | : | Re:TCP not connected to my NIC |
| Author | : | warpcafe warpcafe@yahoo.de |
| Date | : | 17 Sep, 2004 on 09:38 |
Kim, you'll be pleased: From my own experience, OS/2 is far better suited to connect with Linux (workstations, servers) and samba shares than Windoze which sometimes has troubles with access policies on user base in samba. Nice to see a problem could be solved! Thomas |