HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Problems with Tcpip and names
Operating System - OpenVMS
1827514
Members
2812
Online
109965
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-14-2004 10:25 PM
07-14-2004 10:25 PM
Problems with Tcpip and names
Hello,
some strange things happen at the moment in our OpenVMS. First the Versions (OpenVMS 7.3-1, TCP/IP 5.3 Eco2). We use DHCP for our PCs.
We have 3 DNS-Servers, 2 Win2000 Servers and 1 OpenVMS-Server. First I used for VMS the VMS DNS-Server, now I try the Win2000 servers but
nothing changed.
Here are two of our users, user A is from a NT4 PC and user B from a XP PC:
VMS> show user /full
A BDE04 A 2B64DCE9 TNA9622: (Host: mrsstwsn5266 Port: 3431)
B BDE05 _TNA919: 2B4C15DA TNA919: (Host: mrsstwsn00164 Port: 2299)
Now the strange things:
1)
The name of the PC from user A is PC5331 and not MRSSTWSN5266.
The IP-Adress of PC5331 is 10.112.70.19
NSLOOKUP> 10.112.70.19
Name: mrsstwsn0068
Address: 10.112.70.19
NSLOOKUP> MRSSTWSN0068
Name: mrsstwsn0068.STO.MODOPAPER.COM
Address: 10.112.68.115
NSLOOKUP> MRSSTWSN5266
Name: mrsstwsn5266.STO.MODOPAPER.COM
Address: 10.112.68.151
2)
The name of the PC from user B is MRSSTWSN00129 and not MRSSTWSN00164
The IP-Adress of MRSSTWSN00129 ist 10.112.68.29
NSLOOKUP> MRSSTWSN00129
Name: mrsstwsn00129.STO.MODOPAPER.COM
Address: 10.112.68.29
NSLOOKUP> MRSSTWSN00164
*** mrsstser0015.sto.modopaper.com can't find mrsstwsn00164: Server failed
The ping for mrsstwsn00164 fails,too. The PC seems to be not reachable.
We have the same problem with more of our PCs. Sometime you can see names that don't exist, sometimes you see names of other PCs.
We've looked in our DNS but we can't find the error. The PC5331 can only be found in the DHCP database, the PC00129 can be found in the DNS database.
How can I see the right names?
some strange things happen at the moment in our OpenVMS. First the Versions (OpenVMS 7.3-1, TCP/IP 5.3 Eco2). We use DHCP for our PCs.
We have 3 DNS-Servers, 2 Win2000 Servers and 1 OpenVMS-Server. First I used for VMS the VMS DNS-Server, now I try the Win2000 servers but
nothing changed.
Here are two of our users, user A is from a NT4 PC and user B from a XP PC:
VMS> show user /full
A BDE04 A 2B64DCE9 TNA9622: (Host: mrsstwsn5266 Port: 3431)
B BDE05 _TNA919: 2B4C15DA TNA919: (Host: mrsstwsn00164 Port: 2299)
Now the strange things:
1)
The name of the PC from user A is PC5331 and not MRSSTWSN5266.
The IP-Adress of PC5331 is 10.112.70.19
NSLOOKUP> 10.112.70.19
Name: mrsstwsn0068
Address: 10.112.70.19
NSLOOKUP> MRSSTWSN0068
Name: mrsstwsn0068.STO.MODOPAPER.COM
Address: 10.112.68.115
NSLOOKUP> MRSSTWSN5266
Name: mrsstwsn5266.STO.MODOPAPER.COM
Address: 10.112.68.151
2)
The name of the PC from user B is MRSSTWSN00129 and not MRSSTWSN00164
The IP-Adress of MRSSTWSN00129 ist 10.112.68.29
NSLOOKUP> MRSSTWSN00129
Name: mrsstwsn00129.STO.MODOPAPER.COM
Address: 10.112.68.29
NSLOOKUP> MRSSTWSN00164
*** mrsstser0015.sto.modopaper.com can't find mrsstwsn00164: Server failed
The ping for mrsstwsn00164 fails,too. The PC seems to be not reachable.
We have the same problem with more of our PCs. Sometime you can see names that don't exist, sometimes you see names of other PCs.
We've looked in our DNS but we can't find the error. The PC5331 can only be found in the DHCP database, the PC00129 can be found in the DNS database.
How can I see the right names?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2004 03:19 AM
07-15-2004 03:19 AM
Re: Problems with Tcpip and names
it looks like the inverse lookup (ip addr to name) is not inline with the normal lookup (n ame to addr). These are/can be seperate databases. How are the DNS databases updated?
____________________
Purely Personal Opinion
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2004 05:12 AM
07-15-2004 05:12 AM
Re: Problems with Tcpip and names
Hi,
if you have 3 DNS server what order are record in vms name service?
You posted:
Before this you could see the DNS server answer you: in that DNS server may be 10.112.70.19 is mrsstwsn0068.
When you try reverse resolving, as Ian posted you access to a different database and also setting name you cold inquire about virtual host.
Look for this real example (web site of my business):
NSLOOKUP>shs-av.it
Non-authoritative answer:
Name: shs-av.it
Address: 193.207.40.49
> 193.207.40.49
Name: explorer.anstal.it
Address: 193.207.40.49
Antonio Vigliotti
if you have 3 DNS server what order are record in vms name service?
You posted:
NSLOOKUP> 10.112.70.19
Name: mrsstwsn0068
Address: 10.112.70.19
Before this you could see the DNS server answer you: in that DNS server may be 10.112.70.19 is mrsstwsn0068.
When you try reverse resolving, as Ian posted you access to a different database and also setting name you cold inquire about virtual host.
Look for this real example (web site of my business):
NSLOOKUP>shs-av.it
Non-authoritative answer:
Name: shs-av.it
Address: 193.207.40.49
> 193.207.40.49
Name: explorer.anstal.it
Address: 193.207.40.49
Antonio Vigliotti
Antonio Maria Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2004 05:33 PM
07-15-2004 05:33 PM
Re: Problems with Tcpip and names
Hello,
in both directions it is the same name server that answers (both times the openVMS server).
But we've found a solution for our problem (we needed the IP-Adresses of the users who are logged in), I've switched off that the IP-Adresses are translated into names:
TCPIP> set service telnet /log=addr
Now I only see the IP-Adresses and these are the right ones.
So many thanks to all who tried to help me (perhaps we can find the reason for our problems in the future).
Kind regards,
Kirsten
in both directions it is the same name server that answers (both times the openVMS server).
But we've found a solution for our problem (we needed the IP-Adresses of the users who are logged in), I've switched off that the IP-Adresses are translated into names:
TCPIP> set service telnet /log=addr
Now I only see the IP-Adresses and these are the right ones.
So many thanks to all who tried to help me (perhaps we can find the reason for our problems in the future).
Kind regards,
Kirsten
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP