- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Muticast problem
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
Forums
Discussions
Discussions
Discussions
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
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
12-16-2004 08:38 PM
12-16-2004 08:38 PM
Muticast problem
/usr/lib/demos/networking/socket/serv.mcast.c
If I try to start the server twice the following message occurs:
Adress allready is use
unable to bind address
Is there a configuration necessary to allow multicasting at a given address (e.g. 224.168.0.255)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2004 12:22 AM
12-17-2004 12:22 AM
Re: Muticast problem
netstat -an|grep "port_that_you_use_in_program"
This will give which process is using it. Unless it is free you will not be able to bind to it.
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2004 12:28 AM
12-17-2004 12:28 AM
Re: Muticast problem
Usually it takes a time until a formerly bound to port is released.
I know that in the Perl IO::Socket module the contructor takes this parameter to accelerate reavailability
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2004 12:28 AM
12-17-2004 12:28 AM
Re: Muticast problem
Usually it takes a time until a formerly bound to port is released.
I know that in the Perl IO::Socket module the constructor takes this parameter to accelerate reavailability
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2004 12:29 AM
12-17-2004 12:29 AM
Re: Muticast problem
Must have hit the submit button twice.