Using DHCP with FTP Software's OnNet for Windows

ID: Q151399

The information in this article applies to:

Microsoft Windows NT Workstation versions 3.5, 3.51
Microsoft Windows NT Server versions 3.5, 3.51
Microsoft Windows for Workgroups version 3.11
Microsoft Windows 3.1

SUMMARY

When you use DHCP server to assign reserved addresses to FTP Software's DHCP-enabled client OnNet for Windows or PCTCP for DOS, if you type the client[ASCII 146]s media access control address as the "Unique Identifier" in DHCPADMIN, the client will not get the reserved address, but rather, it will be assigned the next available address in the scope.

MORE INFORMATION

FTP Software's DHCP client does not, by default pass its media access control address to the DHCP server when it request an address. Instead, it passes what FTP Software calls a Client ID. Under their Advance Configuration Options, you can assign a unique Client ID. You can then change network interface cards (NICs) without updating your reservation. If you do not assign a Client ID, one with be generated. It will look similar to the following:

69642d303041413030333745303238

To find out the Client ID, let the Client register without a DHCP reservation, and then check the properties of the active least. You can then cut and paste that value into the Unique Identifier field under Add Reservation.

The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words: TCP/IP

Keywords : kb3rdparty kbnetwork ntprotocol nttcp
Version : WINDOWS:3.1,3.11; winnt:3.5,3.51
Platform : WINDOWS winnt
Issue type :