I'm trying to emulate in Warp4 what I can do without trouble in win98. (Theres a challenge!) After configuring mpts to attach tcpip to an intel pro10 ethernet card, I have configured TCPIP on that interface to look for a DHCP server (and also a DDNS server). I have left all other options open. This is all the instruction I need to give win98. When OS2 boots it finds the Intel card at 300h and begins to talk to the cable modem. (I can see the activity light flashing on the modem). Then, after 45 seconds or so, everything stops and OS2 reports "Can't get DHCP parameters." Has anyone got a solution for me? I can't think what parameters it can be looking for. (None required with win98). I'm running Warp4 FP15 and connecting with ustp to a motorola surfboard 4101 cable modem. Thanks Chris

There are various bits of info on cable modem and OS/2 on the web. Sometimes, you will need PPOe (Injoy Firewall) firewall/protocols to communicate with broadband providers. I know I do need to if I went with local DSL service here.

I've had similar problems before. At first, it was with a service that required a username/password combo. I thought the software downloaded was bad. The reality is that for some reason, MPTS can be finicky about how you do things. I haven't verified this, but I suspect that it doesn't like to be reconfigured in certain situations. I uninstalled networking, then reinstalled and that would usually get me up n running (I'm on Time Warner's RoadRunner, which does NOT use a login program, so after installing, and setting tcp/ip correctly, you should be online). I've fooled around with a number of different machines, and setups, and usually MPTS/TCPIP would work right away. Then there were times I uninstalled and manually deleted anything that may have been left over, then reinstalled a few times. I have ALWAYS gotten my cable modem working with, usually with less trouble than Winblows. Hope this helps

Lose the DDNS request. If you are changing machines between tries, the SB4100 series remembers the MAC ID of the last NIC. It won't connect to a second one, unplug the cable modem (standby will not work) count to 15 and plug it back in to reset the memory. Some ISP's require that they KNOW the MAC id of the nic connecting, so if it's a different machine, you may have to call them and give them the MAC. you can put a default route of 192.168.100.1 in. That's the IP of the modem. If you are using the orignal version of the TCPIP that came with Warp 4, it needs to be updated, the DHCP was flaky when it was released.

try unplugging the modem for at least 2 full minutes. this will "erase" the memory and the DHCP server should be albe to release a new IP address.