- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Bind in Client Process
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО07-28-2003 05:59 AM
тАО07-28-2003 05:59 AM
Bind in Client Process
Usually, in Socket (Stream Connection) the instruction BIND is used for assign the Listening Port for a Server Process. Can I use Bind also for the Client Process: I means, The client process always uses the same port for connect to the server?
Thanks in advance for the guide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2003 06:04 AM
тАО07-28-2003 06:04 AM
Re: Bind in Client Process
As with anything else this can be changed.
If you have a firewall blocking port 53 between your server and your client, it won't be able to connect.
You can check the /etc/service table for possible conflicts or problems.
SEP
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
тАО07-28-2003 07:32 AM
тАО07-28-2003 07:32 AM
Re: Bind in Client Process
i dont think it is about BIND (named) :)
Alfonso,
If the server is listening on the some port, client should connect to this port. Client side port number depends on system, it is always >1024.
Example:
serwer is listening on port 80. Client is connecting to this port from the other machine - and the client's port is - for example - 23456 (it it first free port on clients system, i think).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2003 08:32 AM
тАО07-28-2003 08:32 AM
Re: Bind in Client Process
Thanks again for any guide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2003 01:59 AM
тАО07-29-2003 01:59 AM
Re: Bind in Client Process
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2003 04:05 AM
тАО07-29-2003 04:05 AM
Re: Bind in Client Process
However, if you always use the same port you'll only be able to have one client connection from each host. If you attempt a second connection while the first is still established, you'll receive an EADDRINUSE error from the connect() system call. If you need more than one connection you will need to make a range of ports available, and continue calling bind() for each port in the range until one succeeds.
Also be careful of TIME_WAIT sockets - these can also prevent the connection from succeeding. Make sure you set the SO_REUSEADDR socket option with setsockopt() before issuing the bind() call.
Regards,
Steve