On Fri, 01 Sep 2006 10:49:09 -0400 (EDT), Hakan wrote:
>>windows being what it is, it's also possible that some windows dhcp request/parameter
that
>>was not supplied by OS/2's requestor hung or caused a timeout on the server's thread....
>
>Is there a way of finding out what these "windows-specific" settings
>might be? I tried using ipconfig /all on the win machine but was not
>struck by anything that seemed odd.
IN the dhcpcd.cfg file (there's the OS/2 one and an eCS one) you might want to change the
vendor class and user class to something other than "IBMWARP_V4.1" I don't know off the
top of my head what a windows client sends....but seems there's no advantage to telling
them right off that you're not windows...there's other parameters that are not specified
normally but you can pound out the above two classes and see what happens...
back to list