- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- strange outbound network delay on rp3110 hpux11.23
Operating System - HP-UX
1759121
Members
3419
Online
108879
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
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
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
тАО02-08-2007 12:38 AM
тАО02-08-2007 12:38 AM
When I print to a jetdirect printer 10 feet away, I works fine. But I have to stare at the printer for 2 minutes.
When I ssh out of the box, I have to wait 2 minutes before I see ANY response.
When I ssh into the box, I get in right away.
So to recap: network thingy going into box is fine. network thingy going out of box has 2 minute delay.
Any idea where I should look to debug it?
I DID run bastille. I DID set it up in trusted mode. I THINK there might me some type of ip-port filter. But I don't know what it would be called.
I bet that even questions on this issue will be useful.
steve
When I ssh out of the box, I have to wait 2 minutes before I see ANY response.
When I ssh into the box, I get in right away.
So to recap: network thingy going into box is fine. network thingy going out of box has 2 minute delay.
Any idea where I should look to debug it?
I DID run bastille. I DID set it up in trusted mode. I THINK there might me some type of ip-port filter. But I don't know what it would be called.
I bet that even questions on this issue will be useful.
steve
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2007 01:29 AM
тАО02-08-2007 01:29 AM
Re: strange outbound network delay on rp3110 hpux11.23
Steve,
has it always been this way ?
Have you changed any routing info/ default gateways (netstat -r)?
Any errors on the cards (netstat -i) ?
has it always been this way ?
Have you changed any routing info/ default gateways (netstat -r)?
Any errors on the cards (netstat -i) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2007 01:30 AM
тАО02-08-2007 01:30 AM
Solution
Shalom steve,
Nice name.
Yes, IP-Filter can cause this, though normally it would have just stopped the traffic totally.
Trusted system does not do this.
The most likely cause however is:
1) Delay in DNS resolution. If you let bastille touch DNS this could be an issue. It could also be a problem with DNS in your office.
The way around this is normally to make sure /etc/nsswitch.conf has files first.
Have an entry in /etc/hosts that includes the printer and the local system.
Make sure any setup on the print server is sane and responds quickly.
2) You may if you suspect Bastille, wish to run the undo function and do a test. If this fixes the problem then you have to find a way to do the Bastille work that doesn't dirupt printing.
SEP
Nice name.
Yes, IP-Filter can cause this, though normally it would have just stopped the traffic totally.
Trusted system does not do this.
The most likely cause however is:
1) Delay in DNS resolution. If you let bastille touch DNS this could be an issue. It could also be a problem with DNS in your office.
The way around this is normally to make sure /etc/nsswitch.conf has files first.
Have an entry in /etc/hosts that includes the printer and the local system.
Make sure any setup on the print server is sane and responds quickly.
2) You may if you suspect Bastille, wish to run the undo function and do a test. If this fixes the problem then you have to find a way to do the Bastille work that doesn't dirupt printing.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2007 02:28 AM
тАО02-08-2007 02:28 AM
Re: strange outbound network delay on rp3110 hpux11.23
The problem was in resolv.conf.
The ip address of the DNS server I was using was wrong. I fixed the ip. The problem went away.
I wasn't really using DNS for resolving ip addresses. So you would think a bad entry in resolv.conf wouldn't have an effect. Well, I did have it continue on to DNS if it failed to find the hostname in the files. I have that word "DNS" in nsswitch.conf. So the box would spend 2 minutes trying to get DNS stuff out of a ficticious host via an invalid ip address.
Thanks for the help.
steve
The ip address of the DNS server I was using was wrong. I fixed the ip. The problem went away.
I wasn't really using DNS for resolving ip addresses. So you would think a bad entry in resolv.conf wouldn't have an effect. Well, I did have it continue on to DNS if it failed to find the hostname in the files. I have that word "DNS" in nsswitch.conf. So the box would spend 2 minutes trying to get DNS stuff out of a ficticious host via an invalid ip address.
Thanks for the help.
steve
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