OS2 World.Com Forum
2012.05.24, 07:07:40 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: TCP/IP in eCS 2.1?  (Read 2444 times)
Lumo
Newbie
*
Posts: 22


View Profile
« on: 2011.06.29, 16:34:57 »

It's been a long time since I last used OS/2 but now I tried my hand at installing eCS 2.1 on a Thinkpad T41 (2373-tg5). The install works fine, when done and telling it to strat networking automatically I can't ping anything. I get a sendto: No route to host.

This is with a wired connection, it says during startup that it can't load drivers for the wifi so thats a later problem. I have a green light on the wired etehernet port so I have physical connectivity.

Checking TCP/IP configuration it tells med LAN Interface 0 is enabled and should get an address via DHCP.
The DHCP client monitor tells me: DDNS hostanme not registered (normal) and IP address Not Configured (not quite normal). Status: Discovering DHCP servers. Linux/Windows/OS X hosts get addresses just fine via DHCP.
Looking at the Details view in the DHCP Client Monitor tells me:
Sending DISCOVER message.
Number of options requested=6
And it does this with three minute intervals (appx).

I'm probably doing something wrong at a basic level here but need some hints as to what's wrong.

 Huh
Logged
Lumo
Newbie
*
Posts: 22


View Profile
« Reply #1 on: 2011.06.29, 16:50:28 »

Also: ifconfig lan0 brings me:
lan0: flags=8843<UP,BROADCAST,RUNNING,MULTICAST,LOOPBRD>
inet 169.254.240.190  netmask 0xffffffff  broadcast 169.254.240.190

lantran.log tells me:
WRND32$ bound to "TCPIP_NIF"
                WRAPPER for bus: 2 slot: 1 vendor: 0x8086  Device: 0x101E
                load SYS: "E1000NT5.SYS" length: 157184 CRC: 0x6ca6 / 0x6ca6
                load INF: "E1000NT5.INF" length: 747
                WRAPPER ErrorLog 0x6004001f
                WRAPPER hardware init successfull MAC: 000D60:C567E1
Logged
warpcafe
Global Moderator
Hero Member
*****
Posts: 746


Failure is not an option.


View Profile
« Reply #2 on: 2011.06.29, 17:13:52 »

Hi Lumo,

I might be mistaken but what I understand from your description is that apparently something is wrong with your setup.
An IP address of 169... to means that it's an "internal" dummy IP assigned to a WiFi adapter in case it has no connection to any WiFi access point.

When you installed eCS, did you make it load drivers for all NICs (the wired AND the wireless)?
If so, could you perhaps try to reconfigure it (using mptn.exe) to only activate/use the wired NIC instead?
I have to admit that I don't know if something changed for eCS 2.1 regarding NIC configuration...

Other than that, are you having any kind of MAC-adress-based filter enabled on your router which possibly prevents the Thinkpad from being served a DHCP address?

Cheers, HTH,
Thomas
Logged

"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy
Lumo
Newbie
*
Posts: 22


View Profile
« Reply #3 on: 2011.06.29, 18:16:10 »

I did run mpts and removed the wireless adapter.
I also moved tcp/ip up so tcpbeui became second on the wired adapter.

The wireless is now not involved at all, no driver.
There is no mac-filtering going on on the network.

It is puzzling. Smiley
Logged
warpcafe
Global Moderator
Hero Member
*****
Posts: 746


Failure is not an option.


View Profile
« Reply #4 on: 2011.06.29, 19:06:16 »

Hi,
that's strange indeed.
Try this in a command window please:
dhcpstrt -i lan0 -d 10
...which should request a new ip for interface zero and wait ten seconds for a response.
(I hope to have memorized the syntax correctly...)
Maybe the dhcp server takes  (too) long to respond?
HTH
Thomas
Logged

"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy
Lumo
Newbie
*
Posts: 22


View Profile
« Reply #5 on: 2011.06.30, 07:58:16 »

Your syntax was close enough to correct:
dhcpstart -d 10 -i lan0
This gives me: DHCP client did not get parameters and Continuing to try in background.

Intiguing. I'm thinking now that although I have a light that I'm connected maybe there is something wrong with the driver for the card?

I get DHCP addresses for all flavors of Windows I've ever tried, Mac OS X 10.4 and up (I haven't tried any olde rversion) and any and all Linux, OpenBSD, FreeBSD etc. that I have plugged into the network.

In short, I don't think the DHCP server is the problem.

I had this exact same problem with a Thinkpad T60 when eCS 2.1GA was released but thought I'd start over on another Thinkpad because the T60 has a bad rep when it comes to OS/2 support.
Logged
Lumo
Newbie
*
Posts: 22


View Profile
« Reply #6 on: 2011.06.30, 08:25:09 »

On second thought, cancel those orders. Smiley

I just set a hard IP on the interface and that works.

I'm going to take the machine home tonight and try it on my home network to see if I get a dhcp-address there.
Logged
Lumo
Newbie
*
Posts: 22


View Profile
« Reply #7 on: 2011.07.12, 15:26:34 »

..nd to follow up - I do get a dhcp-address at home.

I'm not gonna waste more time on resolving whatever was wrong at work, I'm using eCS at home so I'm perfectly happy.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.14 | SMF © 2006-2011, Simple Machines LLC
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!