HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DNS HELP!
Operating System - HP-UX
1833056
Members
2424
Online
110049
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
06-04-2001 03:38 PM
06-04-2001 03:38 PM
DNS HELP!
I have a L2000 with an IP address of 192.168.*.*
This goes to a firewall where on the outside the IP address turns into 156.42.*.*
Our Clients all have Win98 on their desks and I am wanting to be able to telnet to the L2000 if I am working
on a clients system. I also want to telnet to my other
Unix boxes from the L2000 when I am on it.
The L2000 is our DNS server. When I try to do a nslookup or telnet from the L2000 to any other unix box (That's already behind the firewall) it sits and hangs.
Do I need to add a route to get from the clients system to the L2000 or must I do something else to get to any cpu from wherever I am.
This goes to a firewall where on the outside the IP address turns into 156.42.*.*
Our Clients all have Win98 on their desks and I am wanting to be able to telnet to the L2000 if I am working
on a clients system. I also want to telnet to my other
Unix boxes from the L2000 when I am on it.
The L2000 is our DNS server. When I try to do a nslookup or telnet from the L2000 to any other unix box (That's already behind the firewall) it sits and hangs.
Do I need to add a route to get from the clients system to the L2000 or must I do something else to get to any cpu from wherever I am.
Ross Hanson
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2001 04:52 PM
06-04-2001 04:52 PM
Re: DNS HELP!
Ross:
If you are trying to access the 192.168 server from outside your firewall, I am afraid you are out of luck because the 192.168 address are not routable on the internet. However, what you can do is to set up a listen address on the firewall which gets translated (or plugged-to) to 192.168 address of the L-class. (your firewall admin folk should know how to publish an address and plug it to the L-class)
within your firewall perimeter (inside your network) you can set up any routing provided that all the clients know how to get to the 192.168 network ( I am assuming that you have your wintel machines also having 192 address.)
in summary, this is what you should check:
1. Are you trying to connect to the 192.168 address from outside your fw? if so, get your fw admins to create a plug-to address and set up the appropriate static routes to the L-class
2. if youa re trying to connect from another 192.168 box inside your network, you should not have any problems, if you do, it is likely that your dns is not properly configured with reverse name entries.
my 2c
If you are trying to access the 192.168 server from outside your firewall, I am afraid you are out of luck because the 192.168 address are not routable on the internet. However, what you can do is to set up a listen address on the firewall which gets translated (or plugged-to) to 192.168 address of the L-class. (your firewall admin folk should know how to publish an address and plug it to the L-class)
within your firewall perimeter (inside your network) you can set up any routing provided that all the clients know how to get to the 192.168 network ( I am assuming that you have your wintel machines also having 192 address.)
in summary, this is what you should check:
1. Are you trying to connect to the 192.168 address from outside your fw? if so, get your fw admins to create a plug-to address and set up the appropriate static routes to the L-class
2. if youa re trying to connect from another 192.168 box inside your network, you should not have any problems, if you do, it is likely that your dns is not properly configured with reverse name entries.
my 2c
nothing wrong with me that a few lines of code cannot fix!
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP