System and methods for robust discovery of servers and services in a heterogeneous environment

• US 20050086340A1
• Filed: 10/06/2003
• Published: 04/21/2005
• Est. Priority Date: 10/06/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kang, Nina, Van Hyning, Kenneth, Allor, Jason
• Granted Patent: US 7,467,203 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The present invention is contained in a system for facilitating the identification, discovery, and monitoring of servers and services within a distributed network. The present invention is a system for dynamically discovering all of the servers and services on a network. The dynamic discovery of servers includes first enumerating all of the domains within a network and second enumerating all of the known servers in each of the discovered domains. Next, the system acquires and stores additional server contact information necessary to robustly connect to the server. Finally, the system determines the role of a server in a specified domain within a network. The system will continually monitor the connections to the servers and may use the server contact information to connect to a server or service when a network failure occurs.

Claims

1. A system for discovering and identifying a server, the system comprising:

a network comprising at least one domain, wherein at least one domain comprises at least one server; and

a communication device comprising;

a server monitoring unit operable for;

dynamically discovering at least one server on the network;

monitoring at least one server on the network; and

determining information associated with the monitored server, wherein the information is used to connect to the monitored server after a network failure situation; and

a potential server storage unit operable for;

storing the information associated with the monitored server.

2. The system of claim 1, wherein the communication device further comprises:

a role inquiry storage unit adapted to store role inquiry data used to determine the role of the server, wherein the role inquiry data comprises information inquiries pertaining to identification of a plurality of server types.

3. The system of claim 2, wherein the potential server storage unit is further operable for receiving and storing potential server data used to identify potential servers, wherein the potential server data is received from a networking directory or from the server'"'"'s response to the role inquiry data.

4. The system of claim 3, wherein the server monitoring unit is further operable for:

communicating with the network, the role inquiry storage unit, and the potential server storage unit,

wherein the server monitoring unit is operable for receiving the potential server data from the potential server storage unit;

determining whether the potential server data requires additional information from a potential server,

wherein the additional information comprises information to robustly connect to the potential server or to identify the server type of the potential server;

receiving role inquiry data from the role inquiry storage unit;

providing role inquiry data to the potential server;

receiving additional information from the potential server;

determining the potential server'"'"'s role from the additional information; and

providing the additional information from the potential server to the potential server storage unit.

5. The system of claim 4, the server monitoring unit further adapted to receive networking data from the networking directory and provide the networking data to the potential server storage unit as potential server data, wherein networking data comprises information necessary to robustly connect to the potential server or information necessary to identify the potential server'"'"'s role.

6. The system of claim 1, the system further comprising:

a network operating system unit adapted to communicate with the network and the server monitoring unit,

wherein the network operating system unit is adapted for;

receiving the potential server data and the role inquiry data from the server monitoring unit;

providing the potential server data and the role inquiry data to the potential server;

receiving the additional information from the potential server; and

providing the additional information to the server monitoring unit.

7. A method for discovering a server in a network, the method comprising:

dynamically discovering at least one server on a network;

receiving a name of the at least one server on the network;

filling in contact information associated with the at least one server;

storing the contact information necessary for connecting to the at least one server;

determining whether the network is functioning properly; and

connecting to the at least one server, if the network is not functioning properly.

8. The method of claim 7, wherein determining whether the network is functioning properly comprises:

determining whether a domain name service (DNS) server is available by attempting to resolve a fully qualified domain name (FQDN) associated with the at least one server; and

determining whether network basic input/output system (NetBIOS) traffic exists by attempting to resolve a NetBIOS name associated with the at least one server,

wherein the network is functioning properly if the FQDN and the NetBIOS name resolve.

9. The method of claim 7, wherein dynamically discovering at least one server comprises:

generating a first list of enumerated domains through domain trust discovery;

generating a second list of enumerated domains through directory partitions discovery;

determining whether at least one domain was found in the first list of enumerated domains or the second list of enumerated domains; and

generating a third list of enumerated domains through networking discovery, if no domain was found in the first list of enumerated domains or the second list of enumerated domains.

10. The method of claim 9, wherein dynamically discovering at least one server further comprises:

generating a first list of enumerated servers through directory object discovery for each enumerated domain;

determining whether an error occurred during the directory object discovery;

performing a first sequence if an error did not occur during the directory object discovery, the first sequence comprising;

determining whether a server was found in the first list of servers; and

generating a second list of enumerated servers through networking discovery, if no server was found in the first list of servers; and

performing a second sequence if an error occurred during the directory object discovery, the second sequence comprising;

generating a second list of enumerated servers through networking discovery.

11. The method of claim 7, wherein filling in contact information associated with the at least one server further comprises:

receiving a server name from a user;

receiving a first domain name from the user, if the user provides the first domain name;

querying a server associated with the server name for a second domain name, wherein the server belongs to a domain identified by the second domain name;

determining whether the user provided the first domain name;

verifying the first domain name, if it is determined that the first domain name was provided by the user;

determining whether the user provided a server identifier name; and

processing the server identifier name, if the server identifier name was provided by the user.

12. The method of claim 11, wherein the method further comprises:

determining whether an error occurred when querying the server identified by the server name for a second domain name; and

terminating operation of the method if the determination is made that an error occurred.

13. The method of claim 11, wherein the server identifier name is selected from a list comprising a NetBIOS name and a FQDN.

14. The method of claim 13, wherein verifying the first domain name comprises:

determining whether the first domain name is the same as the second domain name;

using the second domain name as a designated domain name if it is determined that the first domain name and the second domain name are not the same;

using the first domain name as a designated domain name if it is determined that the first domain name and the second domain name are the same; and

marking a flag that identifies the designated domain name as not validated.

15. The method of claim 14, wherein processing the NetBIOS name or FQDN comprises:

using a network directory to search for a server identified by the NetBIOS name or the FQDN within a predetermined domain;

determining whether the server identified by the NetBIOS name or FQDN was found in the predetermined domain;

performing a first sequence if the server identified by the NetBIOS name or FQDN was not found in the predetermined domain, the first sequence comprising;

determining whether the designated domain name is validated; and

validating the designated domain name, if it is determined that the designated domain name was not validated; and

performing a second sequence if the server identified by the NetBIOS name or FQDN was found in the predetermined domain, the second sequence comprising;

storing the NetBIOS name as contact information, if the server was identified by the NetBIOS name; and

storing the FQDN as contact information, if the server was identified by the FQDN.

16. The method of claim 15, wherein validating the designated domain name comprises:

using DNS reverse lookup to find a correct name type;

determining whether DNS reverse lookup found the correct name type;

performing a third sequence if DNS reverse lookup did not find the correct name type, the third sequence comprising;

designating the NetBIOS name as contact information, if the user provided the NetBIOS name; and

designating a first label of the FQDN as contact information, if the user did not provide the NetBIOS name.

17. The method of claim 7, wherein storing the contact information necessary for connecting to the at least one server comprises:

determining a valid internet protocol (IP) address for connecting to the server;

sending an administrative network call to the server using the valid IP address;

determining whether an error occurred when sending the administrative network call to the server;

performing a first sequence if an error did not occur when sending the administrative network call to the server, the first sequence comprising;

storing the valid IP address as contact information; and

performing a second sequence if an error did occur when sending the administrative network call to the server, the second sequence comprising;

determining whether a FQDN associated with the server is valid;

storing a NetBIOS name associated with the server, if the FQDN is not valid; and

storing the FQDN associated with the server, if the FQDN is valid.

18. The method of claim 17, wherein determining whether a FQDN associated with the server is valid comprises determining whether the FQDN is non-null FQDN.

19. The method of claim 17, wherein determining a valid IP address comprises:

determining whether the server has a non-null FQDN;

determining whether the FQDN resolves properly, if the server has a non-null FQDN; and

designating an IP address retrieved from resolving the FQDN as the valid IP address, if the FQDN resolves properly.

20. The method of claim 19, wherein determining a valid IP address further comprises:

determining whether the server has a non-null NetBIOS name;

determining whether the NetBIOS name resolves properly, if the server has a non-null NetBIOS name; and

designating an IP address retrieved from resolving the NetBIOS name as the valid IP address, if the NetBIOS name resolves properly.

21. The method of claim 20, wherein determining a valid IP address further comprises:

determining if there is a cached IP address associated with the server; and

designating the cached IP address as the valid IP address, if there the cached IP address associated with the server exists.

22. A method for identifying a server in a network, the method comprising:

designating a remote computer for determining a server role for the remote computer;

selecting a role inquiry from a set of role inquiries;

querying the remote computer with the role inquiry;

receiving a response to the role inquiry from the remote computer; and

attempting to determine a server role of the remote computer from the response.

23. The method of claim 22, wherein the method further comprises:

selecting a second role inquiry from a set of role inquiries, if the server role of the remote computer cannot be determined;

querying the remote computer with the second role inquiry;

receiving a second response to the second role inquiry from the remote computer; and

determining server role of the remote computer from the second response.

24. The method of claim 22, wherein the attempt to determine a server role of the remote computer from the response is successful.

25. A computer-readable medium having computer-executable instructions for discovering a server in a network, the computer-executable instructions performing steps comprising:

dynamically discovering at least one server on a network;

receiving a name of the at least one server on the network;

filling in contact information associated with the at least one server;

storing the contact information necessary for connecting to the at least one server;

determining whether the network is functioning properly; and

connecting to the at least one server, if the network is not functioning properly.

26. The computer-readable medium of claim 25, wherein determining whether the network is functioning properly comprises:

determining whether a DNS server is available by attempting to resolve a FQDN associated with the at least one server; and

determining whether NetBIOS traffic exists by attempting to resolve a NetBIOS name associated with the at least one server,

wherein the network is functioning properly if the FQDN and the NetBIOS name resolve.

27. The computer-readable medium of claim 25, wherein dynamically discovering at least one server comprises:

generating a first list of enumerated domains through domain trust discovery;

generating a second list of enumerated domains through directory partitions discovery;

determining whether at least one domain was found in the first list of enumerated domains or the second list of enumerated domains; and

generating a third list of enumerated domains through networking discovery, if no domain was found in the first list of enumerated domains or the second list of enumerated domains.

28. The computer-readable medium of claim 27, wherein dynamically discovering at least one server further comprises:

generating a first list of enumerated servers through directory object discovery for each enumerated domain;

determining whether an error occurred during the directory object discovery;

performing a first sequence if an error did not occur during the directory object discovery, the first sequence comprising;

determining whether a server was found in the first list of servers; and

generating a second list of enumerated servers through networking discovery, if no server was found in the first list of servers; and

performing a second sequence if an error occurred during the directory object discovery, the second sequence comprising;

generating a second list of enumerated servers through networking discovery.

29. The computer-readable medium of claim 25, wherein filling in contact information associated with the at least one server comprises:

receiving a server name from a user;

receiving a first domain name from the user, if the user provides the first domain name;

querying a server associated with the server name for a second domain name, wherein the server belongs to a domain identified by the second domain name;

determining whether the user provided the first domain name;

verifying the first domain name, if it is determined that the first domain name was provided by the user;

determining whether the user provided a server identifier name; and

processing the server identifier name, if the server identifier name was provided by the user.

30. The computer-readable medium of claim 29, having further computer-executable instructions for performing the steps of:

determining whether an error occurred when querying the server identified by the server name for a second domain name; and

terminating operation of the method if the determination is made that an error occurred.

31. The computer-readable medium of claim 29, wherein the server identifier name is selected from a list comprising a NetBIOS name and a FQDN.

32. The computer-readable medium of claim 31, wherein verifying the first domain name comprises:

determining whether the first domain name is the same as the second domain name;

using the second domain name as a designated domain name if it is determined that the first domain name and the second domain name are not the same;

using the first domain name as a designated domain name if it is determined that the first domain name and the second domain name are the same; and

marking a flag that identifies the designated domain name as not validated.

33. The computer-readable medium of claim 32, wherein processing the NetBIOS name or FQDN comprises:

using a network directory to search for a server identified by the NetBIOS name or the FQDN within a predetermined domain;

determining whether the server identified by the NetBIOS name or FQDN was found in the predetermined domain;

performing a first sequence if the server identified by the NetBIOS name or FQDN was not found in the predetermined domain, the first sequence comprising;

determining whether the designated domain name is validated; and

validating the designated domain name, if it is determined that the designated domain name was not validated; and

performing a second sequence if the server identified by the NetBIOS name or FQDN was found in the predetermined domain, the second sequence comprising;

storing the NetBIOS name as contact information, if the server was identified by the NetBIOS name; and

storing the FQDN as contact information, if the server was identified by the FQDN.

34. The computer-readable medium of claim 33, wherein validating the designated domain name comprises:

using DNS reverse lookup to find a correct name type;

determining whether DNS reverse lookup found the correct name type;

performing a third sequence if DNS reverse lookup did not find the correct name type, the third sequence comprising;

designating the NetBIOS name as contact information, if the user provided the NetBIOS name; and

designating a first label of the FQDN as contact information, if the user did not provide the NetBIOS name.

35. The computer-readable medium of claim 25, wherein storing the contact information necessary for connecting to the at least one server comprises:

determining a valid internet protocol (IP) address for connecting to the server;

sending an administrative network call to the server using the valid IP address;

determining whether an error occurred when sending the administrative network call to the server;

performing a first sequence if an error did not occur when sending the administrative network call to the server, the first sequence comprising;

storing the valid IP address as contact information; and

performing a second sequence if an error did occur when sending the administrative network call to the server, the second sequence comprising;

determining whether a FQDN associated with the server is valid;

storing a NetBIOS name associated with the server, if the FQDN is not valid; and

storing the FQDN associated with the server, if the FQDN is valid.

36. The computer-readable medium of claim 35, wherein determining whether a FQDN associated with the server is valid comprises determining whether the FQDN is non-null FQDN.

37. The computer-readable medium of claim 35, wherein determining a valid IP address comprises:

determining whether the server has a non-null FQDN;

determining whether the FQDN resolves properly, if the server has a non-null FQDN; and

designating an IP address retrieved from resolving the FQDN as the valid IP address, if the FQDN resolves properly.

38. The computer-readable medium of claim 37, wherein determining a valid IP address further comprises:

determining whether the server has a non-null NetBIOS name;

determining whether the NetBIOS name resolves properly, if the server has a non-null NetBIOS name; and

designating an IP address retrieved from resolving the NetBIOS name as the valid IP address, if the NetBIOS name resolves properly.

39. The computer-readable medium of claim 38, wherein determining a valid IP address further comprises:

determining if there is a cached IP address associated with the server; and

designating the cached IP address as the valid IP address, if there the cached IP address associated with the server exists.

40. A computer-readable medium having computer-executable instructions for identifying a server in a network, the computer-executable instructions performing steps comprising:

designating a remote computer for determining a server role for the remote computer;

selecting a role inquiry from a set of role inquiries;

querying the remote computer with the role inquiry;

receiving a response to the role inquiry from the remote computer; and

attempting to determine a server role of the remote computer from the response.

41. The computer-readable medium of claim 40, wherein the method further comprises:

selecting a second role inquiry from a set of role inquiries, if the server role of the remote computer cannot be determined;

querying the remote computer with the second role inquiry;

receiving a second response to the second role inquiry from the remote computer; and

determining server role of the remote computer from the second response.

42. The computer-readable medium of claim 40, wherein the attempt to determine a server role of the remote computer from the response is successful.