- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: NSLOOKUP works, but IP still showing as system...
-
-
Forums
- Products
- Servers and Operating Systems
- Storage
- Software
- Services
- HPE GreenLake
- Company
- Events
- Webinars
- Partner Solutions and Certifications
- Local Language
- China - 简体中文
- Japan - 日本語
- Korea - 한국어
- Taiwan - 繁體中文
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Blog, Poland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2004 02:38 AM
04-06-2004 02:38 AM
NSLOOKUP works, but IP still showing as system name
But about 7 servers are not showing up by their name, but rather their IP address.
Tried removing one and adding again, but no dice.
Any ideas?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2004 08:51 PM
04-06-2004 08:51 PM
Re: NSLOOKUP works, but IP still showing as system name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 12:29 AM
04-07-2004 12:29 AM
Re: NSLOOKUP works, but IP still showing as system name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 12:43 AM
04-07-2004 12:43 AM
Re: NSLOOKUP works, but IP still showing as system name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2004 01:33 AM
04-07-2004 01:33 AM
Re: NSLOOKUP works, but IP still showing as system name
"DCOM got error "Class not registered " from the computer dwnt1.sherwin.com when attempting to activate the server"
and
"DCOM was unable to communicate with the computer using any of the configured protocols."
But I can ping the machines in each error and use NSLOOKUP both ways.
So, now to figure this mess out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2004 08:10 AM
04-08-2004 08:10 AM
Re: NSLOOKUP works, but IP still showing as system name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2004 04:07 PM
04-12-2004 04:07 PM
Re: NSLOOKUP works, but IP still showing as system name
Make sure the DNS is correct, both forward and reverse lookups. Check that you're not having one return a sub-domain, e.g. looking up 10.10.10.10 might return server.ad.mycompany.com but you're just doing a lookup of server.mycompany.com to compare.
Then allow the various discovery / identification processes to go through. I've got all my devices recognised and we have a mixture of AD and Unix based DNS which offers loads of variety for confusion. I've not had to resort to using a local hosts file, I've found that tends to cause more problems later on, e.g. you click on the device link and cannot get to the page.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2022 Hewlett Packard Enterprise Development LP