Who can show me the reason error TortoiseSVN, when I connect SVN-Repo to update resource
The error detail:
I has already checked the
SVN server is running
Ping to IP server ok
I attached message error:
Error: Unable to connect to a repository at URL 'https://........'
Error running context: A request to send or receive data was
disallowed because the socket is not connected and (when sending on a
datagram socket using a sendto call) no address was supplied.
Hope Everyone help me show the way to fix it.
I have already found the problem, my server svn disabled svn-ports
Error running context: A request to send or receive data was
disallowed because the socket is not connected and (when sending on a
datagram socket using a sendto call) no address was supplied.
Related
I have an IMAP client (Perl, Mail::IMAPClient) connecting to a MS Exchange server which, upon login, receives the error "1 BAD Command received in Invalid state." This same IMAP client works in a number of other environments with no errors, and certainly not errors immediately at login!
I've had trouble determining the source of the error and at this point I'm inclined to think the customer's Exchange server is misconfigured or there's some firewall or packet manipulation shenanigans afoot.
I was able to take a packet capture that really looks normal other than the error. After the TCP handshake this is the whole IMAP conversation, followed by the TCP hangup.
No. Time Source Destination
4 0.010228000 (server) (client)
Internet Message Access Protocol
Line: * OK The Microsoft Exchange IMAP4 service is ready.\r\n
No. Time Source Destination
5 0.012680000 (client) (server)
Internet Message Access Protocol
Line: 1 LOGIN (username) (password)\r\n
Request Tag: 1
Request Command: LOGIN
Request: LOGIN (username) (password)
No. Time Source Destination
6 0.017559000 (server) (client)
Internet Message Access Protocol
Line: 1 BAD Command received in Invalid state.\r\n
Response Tag: 1
Response Status: BAD
Response: BAD Command received in Invalid state.
Am I right in assuming the problem is on the IMAP server's end?
You need to send a CAPABILITY command first, so that you can check if the server has LOGINDISABLED (which it probably does, hence your error).
I have a client-server (Java) application using persistent TCP connections, but sometimes the Server receives java.io.IOException: Connection reset by peer exception when trying to write on the socket, however I don't see any error in the Client log.
This RST is probably caused by an intermediate proxy/router, but if that's the case, should this be seen on the client as well?
If the RST is sent by the client, it can be seen on it using a packet sniffer such as wireshark. However, it won't show up in any user-level sockets since it's sent by the OS as a response to various erroneous inputs (such as connection attempts to a closed port).
If the RST is sent by the network, then it's pretending to be the client to sever the connection. It can do so in one direction, or in both of them. In that case, the client might not see anything, except for a RST sent by the actual server when the client continues to send data to a connection it perceives as open, while the server sees it as closed.
Try capturing the traffic on both the server and the client, see where the resets are coming from.
I have a client - server app that uses NSStream to connect. sometimes when trying to open a connection, one side of the connection gets NSStreamEventEndEncountered when first trying to send a message.
I use the bridge between CFStream and NSStream. My server create a socket with:
_ipv4cfsock = CFSocketCreate(kCFAllocatorDefault,PF_INET, SOCK_STREAM,IPPROTO_TCP, kCFSocketAcceptCallBack, handleConnect, &info);
In the handleConnect callback function, CFStreamCreatePairWithSocketis used to get two CFStream.
My client use CFStreamCreatePairWithSocketToHost to connect to the host.
The client connects (Creates NSStreams) and then sends a ping. When my server receives a connection it opens a NSStream, and when it recieve a ping it sends a pong.
When one of the connection closes the other should get a NSStreanEventEndEncountered as I have set kCFStreamPropertyShouldCloseNativeSocket to true on the streams.
I get several different results: I used NSLog to see what was happening.
-Most of the time the connection opens and works as expected.
Server did recieve new connection
Server recieved ping
Server Sent pong
Client recieved pong
-The connection closes (NSStreamEventEndEncountered) when trying to send the pong. The client doesn't recieve the pong but recieve NSStreamEventEndEncountered
Server did recieve new connection
Server recieved ping
Server recieved pong
Server closed
Client closed
-The connection closes (NSStreamEventEndEncountered) when trying to send the ping. The server doesn't recieve the ping or NSStreamEventEndEncountered
Server did recieve new connection
Client closed
-An error is recieved when trying to send the ping:
Server did recieve new connection;
Error recieved: The operation couldn’t be completed. Connection reset by peer
Both the client and the server are on my computer. Why does the stream get a NSStreamEventEndEncountered when trying to write?
I found the issue, I had a buffer that was sent as soon as my connection opened. If no data was in this buffer, an empty buffer was sent, which is an end signal for the streams.
From Apple Doc:
If the other end of the connection closes the connection:
Your connection delegate’s stream:handleEvent: method is called with
streamEvent set to NSStreamEventHasBytesAvailable. When you read from
that stream, you get a length of zero (0).
Your connection delegate’s stream:handleEvent: method is called with streamEvent set to
NSStreamEventEndEncountered.
When either of these two events occurs,
the delegate method is responsible for detecting the end-of-file
condition and cleaning up.
I have a FIX server and FIX client implementing FIX4.4 running on the same network. I use QuickFIX C++ engine. Altough they are on the same network, sometimes they disconnect. In the FIX server's event logs:
20140612-01:21:30.000 : Sent test request TEST
20140612-04:11:56.000 : Sent test request TEST
20140612-07:05:26.029 : Sent test request TEST
20140612-07:05:26.029 : Socket Error: An established connection was aborted by the software in your host machine.
Means HEARTBIT messages are failed to send/recv.
What can be wrong? I have a regular setup and nothing special..
Thanks
while the client connection was accepted by the server, it doesn't look like you then achieved "logon". First you connect, then you logon. You need to make a logon request after you connect. Look at the initial FIX messages sent between client and server.
I can telnet to a certain host and port no problem and issue commands. However when i try to script a socket connection (using nmap NSE and Lua) to the same host and port, it fails with the following error message:
|_sockettest: Trying to receive through a closed socket
the socket connect part of my code is here:
local msg
local response
msg = "hello\n"
local socket = nmap.new_socket()
socket:set_timeout(150000)
socket:send(msg)
response,data = socket:receive()
return data
I think the data is sending ok. The server should just echo back what i sent. Does anyone know what the problem could be?
You need to call socket:connect before receiving (and before sending). Seriously, read that code you wrote. Where did you specify to whom you're sending ?