Databases
StackOverflow2013
Postsdbo
POJAVA vs Python Socket defaults
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJAVA vs Python Socket defaults
    text
    copied!<p>I'm pretty sure that my root problem is the antivirus app managed by our network, but my a basic socket client I wrote in Python that worked up until a short time ago is now giving me "socket error 10013". I also have the <a href="http://sockettest.sourceforge.net" rel="nofollow">SocketTest </a> app in JAVA. SocketTest works, but I have been unsuccessful in getting Python to connect. The WIN 7 PC has two network cards, not bridged. I have switched the firewall on and off. If I disable the connection to the corporate LAN then the Python client is happy. Just to reiterate, this configuration worked for several months. I cannot find the difference. Here is the sample code:</p> <p>Python</p> <pre><code>MY_IP = '192.168.100.2' MY_PORT = 62828 ROBOT_IP = "192.168.100.10" ROBOT_SOCK = 29999 robotSocket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) robotSocket.bind((MY_IP, MY_PORT)) # Tried without binding robotSocket.connect((ROBOT_IP, ROBOT_SOCK)) </code></pre> <p>Result "socket error 10013"</p> <p>JAVA:</p> <pre><code>socket = new Socket(ROBOT_IP, ROBOT_SOCK); is = socket.getInputStream(); in = new BufferedInputStream(is); while (!desonnected) { try { String got = readInputStream(in); // in.readLine(); </code></pre> <p>This works fine, but I cannot find the difference to adjust my Python code. I'm sure it is the OfficeScan, but....</p> <p><strong>Edit</strong></p> <p>I ran WireShark as suggested. With both network cards enabled the Python connection request is not sent. After disabling the corporate LAN, I compared the Connection requests between the JAVA client and the Python client and they contained the same data except for the local port of course.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload