ok... we've got to get you upgraded to TCP/IP 4.3x
Not much you can do about the DC NIC. I have run some previously without problems - hopefully that's the case for you as well (there were other cards, where other drivers were more suitable to those that came with OS/2 and eCS, such as the BC57 series).
Somewhere I have a link to a post on how to update the entire OS. Perhaps it's author will see this and provide the link. If not, I will dig. In the meantime, check this out:
http://www.os2world.com/forum/index.php/topic,3128.msg19210.html#msg19210 Update 1: I don't know if it completely got rid of the TRAP 000e error, but now I'm receiving this message before Warp 4 boots up:
ROUTE: command failed: Network is unreachable
Press Enter to continue...
How can I get rid of that non-annoying error message? The network connection in the guest OS works without any problems regardless of this error.
Update 2: Well...I managed to upgrade the TCP/IP stack to version 4.3 and I'm still either getting the "ROUTE: command failed: Network is unreachable" or a TRAP 000e (up to two times) referencing to SOCKETS.
Should I look in the CONFIG.SYS or the TCP/IP configuration to see what could be causing this?
(I had to go offline, because a technician was trying to fix my computer.)
Update 3: I solved the error by using the correct destination IP address within the 192.168.254.* range. Since I'm using DHCP, it's assigned to 192.168.254.5 so I had to add this line to the C:\MPTN\BIN\SETUP.CMD file:
route add -net 192.168.254.5 192.168.254.254 -netmask 255.255.255.0 -hopcount 1
I truly hope that this will also eliminate the TRAP 000E errors referencing to SOCKETS.
Update 4: Apparently, that still didn't solve the "ROUTE: Command failed" warning. But what I did to solve this was to extract the IBM Peer diskettes from the OS/2 Warp 4 ISO, install IBM Peer and use a static IP address rather than DHCP. I hoping that there won't be anymore updates to this situation.

Now, it's time to hopefully move on to other things.