If you can guaruntee DNS will be running on your software's destination network, you could create a "host" A-record in DNS (ex: PHSERVER, and client software can use that, or be configured on what hostname to attempt to connect with.
It a bit of hack, and adds an additional dependency/requirement (DNS) to your product, but it is a possible solution. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of Peter Osucha Sent: Friday, May 23, 2008 7:57 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Network Search Thanks Peter (and others who've responded). This gives me some good info to work with. Peter -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Peter Ritchie Sent: Thursday, May 22, 2008 2:53 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Network Search Yes, if PHost isn't running or isn't listening continuously, the you'll have to pick an arbitrary length of time to listen. You might want to have a look at the DHCP protocol [1]. Parts of it's protocol sound much the same as you've described. [1] http://support.microsoft.com/kb/169289 On Thu, 22 May 2008 14:28:52 -0400, Peter Osucha <[EMAIL PROTECTED]> wrote: >Then I guess I need to choose some length of time to 'listen' for >replies? PHost should send a specific reply to the originating node >providing, for example, the name of its machine? > >Peter =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
