Having done some IP programming in the past, I'm gonna say this could be a system or software problem, if that is the exact wording of the message. The attempt to open the socket fails and the next command to use the socket generates that error.
I'm curious what "I researched and did what I thought was how to open the port with correct ip and port #, but it is still closed." means? I'm assuming you can browse the net okay, do email, etc.. Can you ping the site you're trying to connect to with the software?
Thanks for the reply. Mabye I can clarify a little....After installing the fileshare program,I did one of those online diagnostic tests for ports. It said the port I needed was closed. I went to my Network settings and did what I thought would open the port. I went back to the diagnostic test after rebooting and re-installing the program and making sure the firewall was off, and it said the port was still closed. I repeated that procedure about 3 times. I never got an error message from my computer though. I can ping the site, I just checked to see. I have used this program with no problems in the past on different computers, just not with this one. Mabye this will help a little more, sorry for the confusion...
The port is opened by the program in reality, not by the OS. I'd think if it failed to open it should generate a critical error to the program. A firewall blocks the port on transport, it (by itself) doesn't actually close it.
I'm assuming you're looking at the portscan with the software running, also assuming the program has a constant 'listener' on the port you're looking at.
Once you've turned off the internet firewall on XP and any other firewall like norton or zonealarm, I'm not sure there's much else you can do. You might try to telnet to what you are trying to connect to, just change the port on the telnet connect. Probably won't be readable, but the response might be more informative if it fails.
phantomco
15 Posts
0
May 20th, 2004 17:00
Having done some IP programming in the past, I'm gonna say this could be a system or software problem, if that is the exact wording of the message. The attempt to open the socket fails and the next command to use the socket generates that error.
I'm curious what "I researched and did what I thought was how to open the port with correct ip and port #, but it is still closed." means? I'm assuming you can browse the net okay, do email, etc.. Can you ping the site you're trying to connect to with the software?
CBHtn
2 Posts
0
May 20th, 2004 18:00
phantomco
15 Posts
0
May 20th, 2004 22:00
The port is opened by the program in reality, not by the OS. I'd think if it failed to open it should generate a critical error to the program. A firewall blocks the port on transport, it (by itself) doesn't actually close it.
I'm assuming you're looking at the portscan with the software running, also assuming the program has a constant 'listener' on the port you're looking at.
Once you've turned off the internet firewall on XP and any other firewall like norton or zonealarm, I'm not sure there's much else you can do. You might try to telnet to what you are trying to connect to, just change the port on the telnet connect. Probably won't be readable, but the response might be more informative if it fails.