Method of detecting TCP/IP bindings of installed network interface cards present in a computer system
Assignee3Com Corporation
InventorBrant D. Thomsen
Life of this patent
Estimating the term…
Abstract
The present invention provides a method for detecting TCP/IP (Transmission Control Protocol/Internet Protocol) bindings for Network Interface Cards (NICs) installed on Windows 95™ and Windows 98™ operating systems with a VPN (Virtual Private Network) client present. More particularly, the present invention provides a method for parsing the Windows™ system registry to detect TCP/IP bindings for network interface cards installed within a host computer system. In one embodiment, a function for detecting TCP/IP bindings of one network interface card implemented and repeated for all keys of the registry of a computer software for detecting the TCP/IP bindings for network interface cards installed on the host computer system.
Claims17
In a computer system, a method of detecting the TCP/IP binding location for a network interface card, wherein said method is adapted for causing said computer system to perform steps comprising of:
- a) opening a first registry key;
- b) for at least one key in said first registry key, performing a function, wherein said function is adapted for causing said computer system to perform steps of:
- b1) identifying a second registry key represented by the location of a “HardWareKey” string value of said first registry key;
- b2) identifying a third registry key represented by the location of a “Driver” string value for said second registry key;
- b3) identifying the ID value for the parent of the device represented by said first registry key;
- b4) determining a fourth registry key represented by said ID value for the parent of said device;
- and
- b5) determining a fifth registry key represented by the “HardWareKey” string value for said fourth registry key.
- b6) provided there is a “HardwareID” string value for said fifth registry key, said third registry key contains the TCP/IP settings for said network interface card and said fifth registry key is a registry key for said network interface card.
In a computer system running on an operating system, a method of detecting the TCP/IP binding location for a network interface card, wherein said method is adapted for causing said computer system to perform steps comprising of:
- a) opening a first registry key;
- b) for at least one key in said first registry, performing a function, wherein said function adapted for causing said computer system to perform steps of:
- b1) provided the “HardWareKey” string value of said first registry key starts with the string “NETWORK\MSTCP\”, storing said “HardWareKey” string value, said “HardWareKey” string value represented as key1;
- b2) determining a second registry key represented by the “HardWareKey” string value for key1, said second registry key located under the “HKEY_LOCAL_MACHINE\Enum” tree;
- and
- b3) storing said second registry key, said second registry key represented as key1a.
In a computer system running on a Windows™ based operating system, a method of detecting the TCP/IP binding location for a network interface card, wherein said method is adapted for causing said computer system to perform steps comprising of:
- a) opening a first registry key;
- b) for at least one key in said first registry, performing a function, wherein said function is adapted for causing said computer system to perform steps of:
- b1) provided the “HardWareKey” string value of said first registry key starts with the string “NETWORK\MSTCP\”, storing said “HardWareKey” string value, said “HardWareKey” string value represented as key1;
- b2) determining a second registry key represented by the “HardWareKey” string value for key1, said second registry key located under the “HKEY_LOCAL_MACHINE\Enum” tree;
- b3) storing said second registry key, said second registry key represented as key1a;
- b4) determining a third registry key represented by a “Driver” string value for key1a, said third registry key located under the “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class” tree;
- b5) storing said third registry key, said third registry key represented as key1b;
- b6) creating a first variable for storing a location of a registry key, said first variable referred to as key2;
- b7) assigning key2 the same registry key value assigned to key1;
- b8) determining the ID value for the parent of the device represented by key2;
- b9) provided said parent ID value is not “00000000”, finding a fourth registry key represented by said parent ID value for said device;
- b10) storing the location of said fourth registry key, said location of said fourth registry key represented as key2;
- b11) determining a fifth registry key represented by the “HardWareKey” string value for key2, said fifth registry key located under the “HKEY_LOCAL_MACHINE\Enum” tree;
- b12) storing said fifth registry key, said fifth registry key represented as key2a;
- b13) provided there is a “HardwareID” string value for said fifth registry key represented as key2a, storing said third registry key represented as key1b in a list and storing said fifth registry key represented as key2a in said list, wherein said string value represented by key2a is a registry key for said network interface card and wherein said string value represented as key1b are the TCP/IP settings for said network interface card;
- c) producing said list, wherein said list is a listing of said network interface card devices and the registry location where said TCP/IP settings for each network interface card is stored.
Dependencies are inferred from the claim text.