Author Topic: Can not connect to TCP/IP - DHCP Client  (Read 775 times)

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 5586
  • Karma: +50/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Can not connect to TCP/IP - DHCP Client
« on: December 25, 2025, 06:57:37 pm »
Hello

I have a x64 tablet that only has wifi, so I installed ArcaOS 5.1.1 without network. I added "Null" when it asked me for network devices.

Now I finally got my hands on an USB to Ethernet device with an ASIX chipset.  (ASIX AX88772).
On Network Adapters I added the USBASIX.OS2 driver, added IBM TCP/IP and rebooted.

The USBASIX.OS2 loads at boot, the lights of the USB Ethernet device blinks. But I get no IP on ArcaOS.
TCP/IP Settings are on LAN 0 Enabled and Automatic, using DHCP.
No IP to the router. (192.168.10.1)

DDNS Configuration tells me: MSG07. Configuration Failed: DHCP Client has not been initialized by a DHCP Server.

Any ideas what else can I test to find my issue?

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

RTAN

  • Jr. Member
  • **
  • Posts: 80
  • Karma: +11/-0
    • View Profile
Re: Can not connect to TCP/IP - DHCP Client
« Reply #1 on: December 26, 2025, 12:58:43 am »
Hi Martin,

First test: assign your device a static IP address rather than DHCP. Then, from an OS/2 Command Prompt, trying pinging that IP address - that will tell you whether the TCP/IP stack is fully functional.

If you can't even ping your own IP address then you have a TCP/IP stack problem and we can investigate further. If you *can* ping your own IP address then try pinging your router next. That will then tell you whether you simply have a DHCP issue.

Good luck, and let us know the results of that!

Richard.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 5586
  • Karma: +50/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Can not connect to TCP/IP - DHCP Client
« Reply #2 on: December 26, 2025, 02:12:58 am »
Hello Richard

I set a local IP.  It pings to the local IP that I had assigned (192.168.10.109), but If I disconnect the USB-Ethernet it keep pinging right.

There is not access to the router 192.168.10.1.

Regards
« Last Edit: December 26, 2025, 02:19:59 am by Martin Iturbide »
Martin Iturbide
OS2World NewsMaster
... just share the dream.

RTAN

  • Jr. Member
  • **
  • Posts: 80
  • Karma: +11/-0
    • View Profile
Re: Can not connect to TCP/IP - DHCP Client
« Reply #3 on: December 26, 2025, 01:43:37 pm »
Hi Martin,

That's odd, I would honestly have expected it to *stop* being able to ping its own address when you disconnected the device. I'm afraid I don't have one of those USB-to-Ethernet devices so I can't do any further testing with you, hopefully someone else can help further!

Richard.

David McKenna

  • Hero Member
  • *****
  • Posts: 921
  • Karma: +37/-0
    • View Profile
Re: Can not connect to TCP/IP - DHCP Client
« Reply #4 on: December 26, 2025, 02:55:37 pm »
Martin,

  With the USB ethernet attached and driver loaded and IP set to static, open a command prompt and type 'netstat -r'. What do you get?

Regards,

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 5586
  • Karma: +50/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Can not connect to TCP/IP - DHCP Client
« Reply #5 on: December 27, 2025, 04:33:04 pm »
Hello

I got this:

Quote
[C:\]netstat -r
  destination             router                netmask     metric flags intrf

127.0.0.1              127.0.0.1              255.255.255.255   0    UH     lo
192.168.10             192.168.10.109         255.255.255.0     0    UC   lan0

If I disconnect the USB-Ethernet device I get the same netstat -r reply.

Do I miss to put the router IP somewhere?

Just in case I tested the USB-Ethernet device and cable on a Win11 machine and it is working. Just to rule out any hardware problem.


Regards
« Last Edit: December 27, 2025, 04:37:41 pm by Martin Iturbide »
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 5586
  • Karma: +50/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Can not connect to TCP/IP - DHCP Client
« Reply #6 on: December 27, 2025, 04:53:48 pm »
Hello

The problem got solved with magic  ;D

I installed LCSS because I wanted to see the config.sys organized to compare it to my VM. I rebooted and now the network works, even with DHCP.

I will check what did the trick here. Thanks for the help.

Regards
« Last Edit: December 27, 2025, 05:02:35 pm by Martin Iturbide »
Martin Iturbide
OS2World NewsMaster
... just share the dream.

David McKenna

  • Hero Member
  • *****
  • Posts: 921
  • Karma: +37/-0
    • View Profile
Re: Can not connect to TCP/IP - DHCP Client
« Reply #7 on: December 28, 2025, 02:45:20 pm »
Martin,

  Glad you got it working. Normally the first line when you type 'netstat -r' would be 'default   192.168.10.1  0.0.0.0  0  UGP  lan0' which is your default route to your router. That seems to be missing, so you would need to add a default route on the 'Routing' tab of the TCP/IP notebook app. DCHP will get this automatically.

Regards,

Mathias

  • Full Member
  • ***
  • Posts: 200
  • Karma: +3/-0
  • using ArcaOS
    • View Profile
    • IRC
Re: Can not connect to TCP/IP - DHCP Client
« Reply #8 on: January 07, 2026, 11:55:09 pm »
Just a side note;

Pinging the own ip address, even if there is no cable connected or similar, is normal.

Reason is, the driver is local and the target is still there, since it is local. The ICMP packet never leaves the machine, in this case. Where would it even go to? : ) - The target is local, so the cheapest route is to icmp to the local TCP/IP driver's IP 10.x.x.x .

To reach the local 10.x.x.x IP the packet does not need to use the transfer medium "network cable", since you are already there.

If you release the DHCPed IP (or assign another local IP manually), then this previous IP will no longer work, as the target is no longer there. You could then ping the new locally assigned IP, but no longer the old one. (since it is no longer locally available, the stack would try to use the transfer medium in order to try and access the old IP "over the network cable".

Anyway: Happy it works now. ^^

Mathias