- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- TFTPd not bind to second lan
Operating System - HP-UX
1748002
Members
4427
Online
108757
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
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
тАО04-03-2003 10:34 AM
тАО04-03-2003 10:34 AM
TFTPd not bind to second lan
I have a HP/UX 11i system running latest version of Ignite. The problem I am having is that TFTPd is working on lan1 but not lan2. I can tftp to the lan1 interface and pass the get test, "get /var/opt/ignite/INDEX". However, if I tftp to lan2 interface and try the same command, it times out.
I can ping, telnet and ssh to lan2 and I can route out the lan2 interface.
Here is the TFTP line from inetd.conf:
tftp dgram udp wait root /usr/lbin/tftpd tftpd /opt/ignite /var/opt/ignite
and here is "netstat -an | grep 69"
netstat -an | grep 69
tcp 0 0 15.80.40.7
I can ping, telnet and ssh to lan2 and I can route out the lan2 interface.
Here is the TFTP line from inetd.conf:
tftp dgram udp wait root /usr/lbin/tftpd tftpd /opt/ignite /var/opt/ignite
and here is "netstat -an | grep 69"
netstat -an | grep 69
tcp 0 0 15.80.40.7
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-03-2003 12:18 PM
тАО04-03-2003 12:18 PM
Re: TFTPd not bind to second lan
Is your default gateway on lan1? I am not very positive but have nagging doubt that may be the issue. If you can, try changing the default gateway to lan2 and see if that works (and lan1 fails).
...Manjeet
...Manjeet
work is fun ! (my manager is standing behind me!!)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-03-2003 12:27 PM
тАО04-03-2003 12:27 PM
Re: TFTPd not bind to second lan
You what, it just started working. It must have been a networking issue that I did know about.
I am at such a huge company that I could have missed the notice. I'm upset about this since I worked on this problem for a number of hours.
The life of System Admin
Thanks for you help though.
I am at such a huge company that I could have missed the notice. I'm upset about this since I worked on this problem for a number of hours.
The life of System Admin
Thanks for you help though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-03-2003 11:56 PM
тАО04-03-2003 11:56 PM
Re: TFTPd not bind to second lan
Hi,
1] small detail tftpd is UDP protokol, that your output from netstat is incorrect.
2] entry in your inetd.conf seems be good
3] How looks your route table on this machine?
4] where is reside your client station ( net. segment ) ?
1] small detail tftpd is UDP protokol, that your output from netstat is incorrect.
2] entry in your inetd.conf seems be good
3] How looks your route table on this machine?
4] where is reside your client station ( net. segment ) ?
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