GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Communications and Wireless
- >
- Re: network performance
Communications and Wireless
1846054
Members
2161
Online
110253
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
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
Go to solution
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
09-19-2003 04:25 AM
09-19-2003 04:25 AM
I moved my hp9000 to another lan. I redefined my network parameters with set_parms.
But now I think something is wrong with the network environment on my machine:
- ping with ip-address is ok:
# ping 53.139.184.13
PING 53.139.184.13: 64 byte packets
64 bytes from 53.139.184.13: icmp_seq=0. time=0. m
64 bytes from 53.139.184.13: icmp_seq=1. time=0. m
64 bytes from 53.139.184.13: icmp_seq=2. time=0. m
...
...
- ping with hostname is very strange:
get the first response after about 5 min:
# ping aegon
--> waiting 5 min
PING aegon: 64 byte packets
64 bytes from 53.139.184.13: icmp_seq=0. time=0. ms
64 bytes from 53.139.184.13: icmp_seq=1. time=0. ms
...
- Boottime of the machine is 1 hour!
Long time to start network daemons for
example 'NFS client subsystem' or 'mail daemon'
What's wrong
Thanks for any help
Frank
But now I think something is wrong with the network environment on my machine:
- ping with ip-address is ok:
# ping 53.139.184.13
PING 53.139.184.13: 64 byte packets
64 bytes from 53.139.184.13: icmp_seq=0. time=0. m
64 bytes from 53.139.184.13: icmp_seq=1. time=0. m
64 bytes from 53.139.184.13: icmp_seq=2. time=0. m
...
...
- ping with hostname is very strange:
get the first response after about 5 min:
# ping aegon
--> waiting 5 min
PING aegon: 64 byte packets
64 bytes from 53.139.184.13: icmp_seq=0. time=0. ms
64 bytes from 53.139.184.13: icmp_seq=1. time=0. ms
...
- Boottime of the machine is 1 hour!
Long time to start network daemons for
example 'NFS client subsystem' or 'mail daemon'
What's wrong
Thanks for any help
Frank
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2003 02:13 AM
09-22-2003 02:13 AM
Re: network performance
Check all your network settings again. Look through your logs. It sounds like you missed something when you moved to the new network. Either the system still thinks it is on the old network in one of the config file or your dns is still working with the old network address.
If your network services are taking forever at boot up, then I would assume your system doesn't know itself by name anymore. Which would be dns or your /etc/host file entry.
If your network services are taking forever at boot up, then I would assume your system doesn't know itself by name anymore. Which would be dns or your /etc/host file entry.
"Everyone can be taught to sculpt: Michelangelo would have had to be taught how not to. So it is with the great programmers."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2003 02:13 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2003 02:26 AM
09-23-2003 02:26 AM
Re: network performance
Hi Ron
Bingo!!!
"nslookup aegon"
--> got time out with the wrong ip-address
I changed the DNS server IP address. Now the system works with no problems
Cheers
Frank
Bingo!!!
"nslookup aegon"
--> got time out with the wrong ip-address
I changed the DNS server IP address. Now the system works with no problems
Cheers
Frank
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 2026 Hewlett Packard Enterprise Development LP