- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: netcard problem
Operating System - HP-UX
1759773
Members
3802
Online
108889
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
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
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-25-2002 12:36 AM
06-25-2002 12:36 AM
Re: netcard problem
if I understand the issue correctly this is purely a routing issue , a cleint machine vcna point the .20 inbterface from your machien but not the .26 or .27 network interfaces also attached to it , a HP-UX will surely receive the request but as long as it doesn't see then as being needed to route to other networks will ignore them , they are useless to him , you indeed feel no trouble reaching the 192.168.20.15 address from the remote clients as they are on the same .20 subnet , however a remote client needs to know how to reach the 192.168.26 or 192.168.27 network trough your system of via a default gateway which has acces to that networks , you won't be seeing anything in this systems routing table on that , best way to get to these other nets is to check that client failing to ping the 2 other lan interfaces has a default gateway set tot the 192.168.20 interface of your machine or a direct host route to the .26 or .27 IP of your client
or a specific network route to .26 or .27 trough your .20.15 interface....
or a specific network route to .26 or .27 trough your .20.15 interface....
...knowing one ignores a greath many things is the first step to wisdom...
- « Previous
-
- 1
- 2
- Next »
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP