charles_gilley
asked on
Dropping a device into an unknown Windows network - discovery?
My network savvy comes from Unix-land, and I am lost in Windows acronym land. I have a custom WinCE device that will be deployed in a "customer environment" - meaning, I will have no idea what it will look like. What I do know is:
- it is a DHCP client;
- I can set the network name of my device;
I need the device to be discoverable on the network. Rather than have someone go out to query the DHCP assigned IP address, I need the user to be able to find the device by name. From this week's reading, I have learned some about dynamic DNS, then WINS, and I'm trailing off into active directory (at which point I headed to EE).
Broadly, what existing techniques are now employed in a Windows network to support device discovery, and what must my device do to cooperate with the discovery process? Is WINS the main service? Active Directory? dynamic DNS? A mix?
- it is a DHCP client;
- I can set the network name of my device;
I need the device to be discoverable on the network. Rather than have someone go out to query the DHCP assigned IP address, I need the user to be able to find the device by name. From this week's reading, I have learned some about dynamic DNS, then WINS, and I'm trailing off into active directory (at which point I headed to EE).
Broadly, what existing techniques are now employed in a Windows network to support device discovery, and what must my device do to cooperate with the discovery process? Is WINS the main service? Active Directory? dynamic DNS? A mix?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.