HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Networking problem related to getpeername
Operating System - HP-UX
1833310
Members
2781
Online
110051
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-25-2002 11:22 PM
06-25-2002 11:22 PM
Networking problem related to getpeername
Hi
We are facing following problems while establishing TCP connection between HP-UX 11.0 ( server) and HP-UX 11.0 ( client). Following things are done
(1) Server binds to a local address eg X by calling system call 'bind'
(2) Client connects to Server by specifying server address X. When client tries to find Server address from connected socket by calling 'getpeername' , it gets different address than X.
Is this a bug in HP-UX? we tried to search HP site but could not find any bug related to this problem.
Did any one face similar situation?
Thank in advance
Regard
We are facing following problems while establishing TCP connection between HP-UX 11.0 ( server) and HP-UX 11.0 ( client). Following things are done
(1) Server binds to a local address eg X by calling system call 'bind'
(2) Client connects to Server by specifying server address X. When client tries to find Server address from connected socket by calling 'getpeername' , it gets different address than X.
Is this a bug in HP-UX? we tried to search HP site but could not find any bug related to this problem.
Did any one face similar situation?
Thank in advance
Regard
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2002 12:57 AM
06-26-2002 12:57 AM
Re: Networking problem related to getpeername
Hi,
Are the Normal networking services like ftp , telnet functions well in the server ?.
Are you binding the server with a IP address and also a port ?.
regards,
U.SivaKumar
Are the Normal networking services like ftp , telnet functions well in the server ?.
Are you binding the server with a IP address and also a port ?.
regards,
U.SivaKumar
Innovations are made when conventions are broken
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2002 03:38 AM
06-26-2002 03:38 AM
Re: Networking problem related to getpeername
Thanks for the reply.
Yes, we are binding with IP and port.
Yes, we are binding with IP and port.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2002 10:49 AM
06-26-2002 10:49 AM
Re: Networking problem related to getpeername
Hi,
This was a problem in sockets
code (xport) and it has been
resolved.
Try linking your binary with
"-lxnet" at compilation time
and you should see it through.
-Lokesh.
This was a problem in sockets
code (xport) and it has been
resolved.
Try linking your binary with
"-lxnet" at compilation time
and you should see it through.
-Lokesh.
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