Sponsored Content
Top Forums Programming Debugging IO::Socket Not Connecting Post 302428740 by pseudocoder on Thursday 10th of June 2010 07:50:33 PM
Old 06-10-2010
Can you ping the remote Windows machine?
Is the port you have defined open? (nmap)
If it's open, maybe it's firewalled or something?

Try:
Code:
   print "Could not connect! Reason: $!\n";

 

10 More Discussions You Might Find Interesting

1. Programming

Socket Programming socket

Hello, I actually try to make client-server program. I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error : I'm just using this simple code : and I get the same error if I use : If someone can help me, Thanks (2 Replies)
Discussion started by: soshell
2 Replies

2. Shell Programming and Scripting

Regarding Debugging

Hi, If we want to debug a shell script, then set -vx has to be included in the begining of the script. Just i want to know what purpose -vx is used. Thanks in advace Sarwan (2 Replies)
Discussion started by: sarwan
2 Replies

3. Programming

Problem Connecting to Socket

Can anyone help? I'm trying to write a program which will write to a socket. I can get the server to run, but always get an error when I try to connect. It gives me an error at the "connect" command. It's probably a simple error, but I can't seem to find it. #include <sys/socket.h>... (6 Replies)
Discussion started by: Stevhp
6 Replies

4. Solaris

debugging

when I tried to debug my application i got the following. gdb -v GNU gdb 6.6 file is in C and Xmotiff Languages (gdb) attach 25499 Attaching to process 25499 Retry #1: Retry #2: Retry #3: Retry #4: 0xfea40b68 in ?? () (gdb) where #0 0xfea40b68 in ?? () (0 Replies)
Discussion started by: satish@123
0 Replies

5. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime. To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies

6. Programming

which socket should socket option on be set

Hi all, On the server side, one socket is used for listening, the others are used for communicating with the client. My question is: if i want to set option for socket, which socket should be set on? If either can be set, what's the different? Again, what's the different if set option... (1 Reply)
Discussion started by: blademan100
1 Replies

7. Programming

socket function to read a webpage (socket.h)

Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct... #include <stdio.h> #include <stdlib.h> #include <sys/types.h> #include <sys/stat.h> #include <string.h> #include... (3 Replies)
Discussion started by: cyler
3 Replies

8. Programming

Error with socket operation on non-socket

Dear Experts, i am compiling my code in suse 4.1 which is compiling fine, but at runtime it is showing me for socket programming error no 88 as i searched in errno.h it is telling me socket operation on non socket, what is the meaning of this , how to deal with this error , please... (1 Reply)
Discussion started by: vin_pll
1 Replies

9. IP Networking

Clarification - Setting socket options at the same time when socket is listening

I need clarification on whether it is okay to set socket options on a listening socket simultaneously when it is being used in an accept() call? Following is the scenario:- -- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies

10. Programming

c++ debugging

hey i have a problem with a switch case in program and the debugger is messy has hell ( we use normal VI and gdb in our schoool to make it more diffiacult) any way i have a problom where for some unknown reason the debugger just skips a switch statment as if it wasent even there the rest... (2 Replies)
Discussion started by: gotenxds
2 Replies
roar_socket_listen(3)					System Manager's Manual: RoarAudio				     roar_socket_listen(3)

NAME
roar_socket_listen - Opens a new listen socket SYNOPSIS
#include <roaraudio.h> int roar_socket_listen(int type, char * host, int port); DESCRIPTION
Opens a new listening socket for network clients to connect to. You may accept new connections via accept(2). PARAMETERS
type The type of the Socket. See the list below. host The host or path name to listen on. This depends on the type argument. For TCP/IP to listen on any interface use a value of "0.0.0.0". port The port number to listen on. This may be ignored by types not supporting port numbers. SOCKET TYPES
ROAR_SOCKET_TYPE_UNKNOWN The type will be auto detected. Don't use this if you know the type. Only use this to support user given addresses and enable auto detection. ROAR_SOCKET_TYPE_TCP Use a TCP/IP connection. This is standard mode for networking. host is the hostname or IP to listen on and port is the port number to use. ROAR_SOCKET_TYPE_INET Same as above but deprecated. Use ROAR_SOCKET_TYPE_TCP. ROAR_SOCKET_TYPE_UNIX UNIX Domain Socket. This should be default for local connections. host is the filename of the socket. ROAR_SOCKET_TYPE_DECNET DECnet socket. ROAR_SOCKET_TYPE_FORK This is to fork a roard to communicate with. Can't be use to listen on, just to connect to. host and port is ignored at the moment. ROAR_SOCKET_TYPE_FILE This is used to open a plain file. Can't be use to listen on, just to connect to. host is the filename to connect to. RETURN VALUE
On success these calls return filehandle. On error, -1 is returned. BUGS
Listening on UDP sockets is not supported at the moment. EXAMPLES
FIXME SEE ALSO
accept(2), libroar(7), RoarAudio(7). RoarAudio May 2011 roar_socket_listen(3)
All times are GMT -4. The time now is 05:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy