https://community.hpe.com/t5/server-management-systems/hpsim-5-1-resolve-windows-server-name/m-p/3948976#M25784 We just reinstalled HP SIM 5.1 on Red Hat 4U3. We have a bunch of Windows blades and they were all discovered with their IP addresses listed not their name.<BR /><BR />Do I need to config winbind on my CMS in order to get Windows blade discovered by the blade?<BR /><BR />Anything I missed and should do?<BR /><BR />Thank you. Wed, 21 Feb 2007 13:37:46 GMT Arthur Kao 2007-02-21T13:37:46Z https://community.hpe.com/t5/server-management-systems/hpsim-5-1-resolve-windows-server-name/m-p/3948976#M25784 We just reinstalled HP SIM 5.1 on Red Hat 4U3. We have a bunch of Windows blades and they were all discovered with their IP addresses listed not their name.<BR /><BR />Do I need to config winbind on my CMS in order to get Windows blade discovered by the blade?<BR /><BR />Anything I missed and should do?<BR /><BR />Thank you. Wed, 21 Feb 2007 13:37:46 GMT https://community.hpe.com/t5/server-management-systems/hpsim-5-1-resolve-windows-server-name/m-p/3948976#M25784 Arthur Kao 2007-02-21T13:37:46Z https://community.hpe.com/t5/server-management-systems/hpsim-5-1-resolve-windows-server-name/m-p/3948977#M25785 HP SIM uses DNS exclusively for name resolution. Ensure your CMS can get both forward and reverse DNS for the Windows blades in question... Wed, 21 Feb 2007 16:52:33 GMT https://community.hpe.com/t5/server-management-systems/hpsim-5-1-resolve-windows-server-name/m-p/3948977#M25785 David Claypool 2007-02-21T16:52:33Z