Iphone 5 connection reset by peer problem

Hi all,
I encounter "Connection reset by peer problem" when i try to login facebook using Iphone 5. I've even reset network setting but it doesn't help.
Any solution? Please advise.
Thanks.

That sounds like a problem with the Facebook servers.

Similar Messages

  • Connection reset by peer problem

    I have the following code, and every time I run it i get a "java.net.SocketException: Connection reset by peer: socket write error" exception. Why is that? This is the first time I'm writing a network client application, so please help :)
    Socket s = new Socket("127.0.0.1",8080);
    OutputStream out = new BufferedOutputStream(s.getOutputStream());
    InputStream in = new BufferedInputStream(s.getInputStream());
    out.write("server status\r\n".getBytes());
    //out.flush();
    StringBuffer responseLine = new StringBuffer();
    int c;
    while(in.available() > 0) {
      c = in.read();
      responseLine.append((char)c);
    //out.close();
    //in.close();
    //s.close();
    System.out.println(responseLine.toString());P.S. It's the same problem with or wothout the out.flush(), and with or wothout closing my streams and socket.

    InputStream = new BufferedReader
    Um..just look at that code, oh boy.
    InputStream is a class and so is
    BufferedReader
    Two different classes (event if they are subclasses)
    cant be directly assigned to each other.The human eye sometimes sees what it wants to see and not what it is... :-)
    I think the problem is with the protocol and the timing. The while loop may never execute due to timing:
    1. Client's "server status" request takes a few ms to arrive in the server.
    2. In the meanwhile, in.available is zero and the client does not enter the loop and does not append any characters to the string buffer.
    3. Server writes its status on the socket which arrives at the client which is no longer reading it a few ms later.
    Which brings us to the protocol:
    If the server status is a fixed length block of data, try reading it into a single byte buffer.
    If it is variable length or text, use a BufferedReader on the socket, read the response a line at a time and make the server end the report with a token (like a last line of "END_OF_SERVER_STATUS_REPORT" or "01234567890123456789012345678901234567890123456789", whatever).
    Don't check if data is available on a socket if you know it should be, sooner or later, and you don't want to multiplex your flow on data availability.

  • Always suffer "connection reset by peer" while performing software update

    Hi all,
    I just bought a brand new macbook air. The first thing I do for this laptop is to perform the software update. It suffered me for a long time that I always encounter the error message
    "Connection reset by peer The Installer package has been moved to the Trash. To try again, open the package from the Finder"
    For some update that the file larger than 10Mbytes, the error is very easy to occur. I will be ever lucky that I could download the update package for larger update file.
    I can make sure that my network to wireless route is well as I could download 500Mbytes file manually from internet without any problem. Actually, I had downloaded the mac X OS 10.5.4 package manually and upgrade the system from 10.5.2 to 10.5.4 as it is almost impossible for me use "software update" to download about 500Mbytes without "connection reset by peer" problem.
    Any input is appreciate.
    Thanks.

    I have the exact same problem , can any one please help with this
    Thanks

  • Connection reset py peer

    When I try to connect to Itunes Store on my iphone, I get a message back saying "Cannot connect to Itunes Store.  Connection reset by peer.  How can I resolve this?

    Hi Roen,
    Maybe I'm pointing you into the wrong direction, on forehand my apologies for that.
    What I need you should check: Ironport has a limit on the number of concurrent TLS session. Your problem might occur when this limit is reached and an additional host tries to setup a TLS connection.
    (Not sure, just a shot in the dark)
    Good luck with this problem,
    Best Regards,
    Steven

  • Socket read error: connection reset by peer

    Hi.
    Has anybody experienced the error message �Socket read error: connection reset by peer�
    Please see below for detailed information.
    Appreciate your help
    Regards
    RT
    Enviroment specification
    Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
    2 firewalls between client and db.
    Client:
    Win 2000,
    SP3,
    Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
    JDK 1.3
    JRUN3.0
    The TCP protocol is being used in the communication
    Error messages
    Web Users receive:           Socket read error: connection reset by peer
    Trace files on the sever:      Read unexpected EOF ERROR on 18.
    Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
    The problem
    The users of the java web application, experiencing an exception almost once or twice a day.
    The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
    At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
    This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
    The application
    The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
    The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
    Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
    Issues considered
    Connection pooling
    It is a customized connection pooling, developed by Lindorff developers.
    I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
    The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
    Firewall
    One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
    Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
    Number of processes the DB can handle
    Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
    Port redirection through a firewall:
    Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
    The network group
    The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
    It seems like the firewall are dropping packages bacause of "Unknown
    established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involved

    Presumably something is working.
    Thus the problem is not with your code. At least not the database part that you have control over.
    That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it.

  • XI 2.0 Inbound file adapter : Connection reset by peer

    I am using XI 2.0 and have an inbound file adapter. It polls every 5 minutes. But at least 1 or twice a day the file adapter stops with the following error message.
    "java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read" occurred \par
    There have been times when this runs for days or weeks without any problems.
    Has anyone else seen this issue and how do your correct it?
    Currently I have to go into the file adpaters and restart them manually. It would be nice if there was some way to automate this function. Any ideas?
    Regards,
    Jim

    With JDK 5.0 use ojdbc5.jar instead of ojdbc14.jar.

  • Connection reset by peer.

    I recently started getting following exception. I use Windows 2000
              with weblogic 5.1 service pack 12. This problem does not effect the
              functionality, and happens randomly.
              Thank you,
              berker(at)optonline.net
              java.net.SocketException: Connection reset by peer: socket write error
                   at java.net.SocketOutputStream.socketWrite(Native Method)
                   at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
                   at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
                   at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
                   at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
                   at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
                   at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
                   at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
                   at weblogic.servlet.FileServlet.service(FileServlet.java:56)
                   at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
                   at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
                   at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
                   at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
                   at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

    Looks like the browser user is closing the browser or moving on to a new url before the response comes back.
              Search the newsgroup, as there are a number of posts concerning this.
              Bill
              berker wrote:
              > I recently started getting following exception. I use Windows 2000
              > with weblogic 5.1 service pack 12. This problem does not effect the
              > functionality, and happens randomly.
              >
              > Thank you,
              > berker(at)optonline.net
              >
              > java.net.SocketException: Connection reset by peer: socket write error
              > at java.net.SocketOutputStream.socketWrite(Native Method)
              > at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
              > at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
              > at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
              > at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
              > at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
              > at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
              > at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
              > at weblogic.servlet.FileServlet.service(FileServlet.java:56)
              > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
              > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
              > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
              > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
              > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
              > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
              > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

  • IOException: Connection reset by peer: JVM_recv in socket input stream read

    hi
    I encountered a problem : a program throw out an exception:java.io.IOException: Io exception:
    Connection reset by peer: JVM_recv in socket input stream read.
    I tried my best to resolve it ,but unfortunately,i didn't know what caused the exception.
    the following is my application environment:
    I have two PC(Win2000os),one is a server which installed oracle9.2.0.2 and jdeveloper9.0.3,the another is a
    client which only intalled jdeveloper9.0.3.Two days ago,i performed a web application on my client with
    jdeveloper,and it includes some JSP and a javabean files.JSP Page finished uploading client xml file to a
    folder on server and the javabean finished loading the xml file into a xmltype column.I can make sure the
    connection is established and the javabean is OK,beacause my some jsp page can successfully use
    <jsp:usebean> tag and use the javabean's some other public interfaces,except the interface that finishs
    loading the xml file into a xmltype(clob) column.
    Then i do many tests!I changed the javabean to a java class incluse a main method beacause it is easy to
    debug.Finally i found the following code caused the exception:
    public CLOB writetoClob( CLOB clob, InputStream is )throws SQLException, IOException {
    InputStreamReader reader = new InputStreamReader( is );
    Writer writer = clob.getCharacterOutputStream( );
    char[] buffer = new char[clob.getChunkSize(  )];
    int charsRead;
    for ( charsRead = reader.read( buffer ); charsRead > -1;charsRead = reader.read( buffer ) ) {
    writer.write( buffer, 0, charsRead );
    writer.close();
    return clob;
    when it runs to writer.close(),the exception is caused!
    Then i copy the java class to the server,it runs ok!
    That is to say ,the same code,the different result!
    But when i run my web application on server with jdeveloper Embedded OC4J Server and a jsp page loaded javabean
    and run to mentioned code ,the same exception occured!
    I checked the application log in event viewer,the descriptions was:
    The data buffer created for the "AppleTalk" service in the "C:\WINNT\system32\atkctrs.dll" library is not
    aligned on an 8-byte boundary. This may cause problems for applications that are trying to read the
    performance data buffer. Contact the manufacturer of this library or service to have this problem corrected or
    to get a newer version of this library.
    I search some some resolution about this exception with web and someone sayed :
    This basically means that a network error occurred while the client was receiving data from the server. But
    what is really happening is that the server actually accepts the connection, processes the request, and sends a
    reply to the client. However, when the server closes the socket, the client believes that the connection has
    been terminated abnormally because the socket implementation sends a TCP reset segment telling the client to
    throw away the data and report an error.
    Sometimes, this problem is caused by not properly closing the input/output streams and the socket connection.
    Make sure you close the input/output streams and socket connection properly. If everything is closed properly,
    however, and the problem persists, you can work around it by adding Thread.sleep(1000) before closing the
    streams and the socket. This technique, however, is not reliable and may not work on all systems.
    In general,the following information is conclution:
    Web application runs error both on client and on server.
    If it was changed to a client java class,it only run ok on server!
    i have done anything that i can do now,i feel depressed very much!
    how can i resolve the problem!
    Any a little help will be appreciated!
    regards!
    Thanks
    Jiawei ZHAO

    How can i solve the problem.
    Thanks in advance!
    Jiawei Zhao

  • Connection reset by peer: JVM_recv in socket input stream read

    Dear All,
    We are facing a very unusual problem. In our application, there is a functionality to transfer files to a FTP server using java FTPClient.
    Now while transferring set of files, few times it throws the error:
    Connection reset by peer: JVM_recv in socket input stream read
    This error comes irregularly.
    Can you suggest the reason for this.
    Regards,
    Akhil

    which platform are you using? which ip stack , ipv4 or ipv6?
    try to set -Djava.net.preferIPv4Stack="true" when startup,
    it will use ipv4 stack instead of default ipv6 on solaris.

  • Remote Desktop on Mac connecting to 2008 R2 Server produces "Connection Reset by Peer" error when idle 20 mins

    Mac Clients are running 10.9.2 Mavericks. 
    Client is Microsoft Remote Desktop 8.05.
    Clients are mixed in how they connect to the Windows 2008 R2 server, some
    are on Wifi some are on Wired Ethernet.
    If you connect to the Server through the RD Client, and get on you work 
    and if you then say go idle  ( still connected but not doing anything such as 
    printing from the Server or in an Application on the Server) then after 20 mins it
    (the client) throws up a "Connection reset by Peer" error.
    You click OK, and then it breaks connection. You can however reconnect without issue.
    We have currently about six users who are using the RD Connection to access QuickBooks on
    this 2008 R2 server. Four are on Macs and get the errors. Two are on PCs and do not get the errors.
    Here is the log file from one of the Macs that had the error:
    [2014-Apr-07 10:34:07] RDP (0): Server shows cursor
    [2014-Apr-07 10:34:09] RDP (0): Server hides cursor
    [2014-Apr-07 10:34:21] RDP (0): Server shows cursor
    [2014-Apr-07 10:34:22] RDP (0): Server hides cursor
    [2014-Apr-07 10:34:25] RDP (0): Server shows cursor
    [2014-Apr-07 11:00:29] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 11:00:29] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 11:00:29] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 11:02:35] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 11:02:35] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 11:02:35] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 11:02:35] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 11:02:35] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-07 11:02:35] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 11:02:35] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 11:02:35] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 11:02:35] RDP (0): client version: 8.0.24428
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 11:02:35] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 11:02:35] RDP (0): Server supports RAIL
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 11:02:35] RDP (0): Server supports RAIL
    [2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 11:09:38] RDP (0): Server hides cursor
    [2014-Apr-07 11:09:38] RDP (0): Server shows cursor
    [2014-Apr-07 11:09:38] RDP (0): Server hides cursor
    [2014-Apr-07 11:09:38] RDP (0): Server shows cursor
    [2014-Apr-07 11:09:38] RDP (0): Server hides cursor
    [2014-Apr-07 11:09:38] RDP (0): Server shows cursor
    [2014-Apr-07 12:16:31] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 12:16:31] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 12:16:31] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 12:21:42] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 12:21:42] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 12:21:42] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 12:21:42] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 12:21:42] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-07 12:21:42] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 12:21:42] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 12:21:42] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 12:21:42] RDP (0): client version: 8.0.24428
    [2014-Apr-07 12:21:42] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 12:21:42] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 12:21:42] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 12:21:43] RDP (0): Server supports RAIL
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 12:21:43] RDP (0): Server supports RAIL
    [2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 15:30:19] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 15:30:19] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 15:30:19] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 15:30:22] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 15:30:22] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 15:30:22] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 15:30:22] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 15:30:22] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-07 15:30:22] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 15:30:22] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 15:30:22] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 15:30:22] RDP (0): client version: 8.0.24428
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 15:30:22] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 15:30:22] RDP (0): Server supports RAIL
    [2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 15:30:23] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 15:30:23] RDP (0): Server supports RAIL
    [2014-Apr-07 15:30:23] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 16:52:24] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 16:52:24] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 16:52:24] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 16:52:27] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-07 16:52:27] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-07 16:52:27] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 16:52:27] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-07 16:52:27] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-07 16:52:27] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-07 16:52:27] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-07 16:52:27] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-07 16:52:27] RDP (0): client version: 8.0.24428
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-07 16:52:27] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 16:52:28] RDP (0): Server supports RAIL
    [2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 16:52:28] RDP (0): Server supports RAIL
    [2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-07 16:52:40] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-07 16:52:40] RDP (0): Disconnect initiated by server
    [2014-Apr-07 16:52:45] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-07 16:52:45] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-07 16:52:45] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-07 16:58:19] RDP (0): *** Application terminated ***
    [2014-Apr-08 10:00:23] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 10:00:23] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 10:00:23] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:00:23] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:00:23] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 10:00:23] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 10:00:23] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 10:00:23] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 10:00:23] RDP (0): client version: 8.0.24428
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 10:00:23] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 10:00:23] RDP (0): Server supports RAIL
    [2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 10:00:38] RDP (0): Server hides cursor
    [2014-Apr-08 10:00:40] RDP (0): Server shows cursor
    [2014-Apr-08 10:08:35] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 10:08:35] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 10:08:35] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 10:08:39] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 10:08:39] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 10:08:39] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:08:39] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 10:08:39] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-08 10:08:39] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 10:08:39] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 10:08:39] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 10:08:39] RDP (0): client version: 8.0.24428
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 10:08:39] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 10:08:39] RDP (0): Server supports RAIL
    [2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 10:08:40] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 10:08:40] RDP (0): Server supports RAIL
    [2014-Apr-08 10:08:40] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:02:36] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 11:02:36] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 11:02:36] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 11:04:38] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.25
    audiomode:i:0
    username:s:michele.lefebvre
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 11:04:38] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 11:04:38] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:04:38] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:04:38] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 11:04:38] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 11:04:38] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 11:04:38] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 11:04:38] RDP (0): client version: 8.0.24428
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 11:04:38] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:04:38] RDP (0): Server supports RAIL
    [2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:04:39] RDP (0): Server supports RAIL
    [2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:04:49] RDP (0): Server hides cursor
    [2014-Apr-08 11:04:50] RDP (0): Server shows cursor
    [2014-Apr-08 11:04:51] RDP (0): Server hides cursor
    [2014-Apr-08 11:04:55] RDP (0): Server shows cursor
    [2014-Apr-08 11:05:09] RDP (0): Server hides cursor
    [2014-Apr-08 11:05:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:33] RDP (0): Server hides cursor
    [2014-Apr-08 11:06:33] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:06:44] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:49] RDP (0): Server hides cursor
    [2014-Apr-08 11:06:50] RDP (0): Server shows cursor
    [2014-Apr-08 11:06:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:02] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:06] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:14] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:26] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:32] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:33] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:35] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:35] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:35] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:36] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:36] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:36] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:07:38] RDP (0): Server hides cursor
    [2014-Apr-08 11:07:38] RDP (0): Server shows cursor
    [2014-Apr-08 11:17:05] RDP (0): Server hides cursor
    [2014-Apr-08 11:17:08] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:53] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:54] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:54] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:58] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:58] RDP (0): Server shows cursor
    [2014-Apr-08 11:26:58] RDP (0): Server hides cursor
    [2014-Apr-08 11:26:58] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:05] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:06] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:15] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:15] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:15] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:15] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:17] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:17] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:22] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:22] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:23] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:25] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:25] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:25] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:25] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:26] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:29] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:29] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:29] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:29] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:31] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:31] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:32] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:33] RDP (0): Server shows cursor
    [2014-Apr-08 11:27:35] RDP (0): Server hides cursor
    [2014-Apr-08 11:27:36] RDP (0): Server shows cursor
    [2014-Apr-08 11:29:50] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 11:29:50] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 11:29:50] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 11:30:04] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 11:30:04] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 11:30:04] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:30:04] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 11:30:04] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 11:30:04] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 11:30:04] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 11:30:04] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 11:30:04] RDP (0): client version: 8.0.24428
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 11:30:04] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:30:04] RDP (0): Server supports RAIL
    [2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:30:05] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 11:30:05] RDP (0): Server supports RAIL
    [2014-Apr-08 11:30:05] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 11:30:11] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:11] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:11] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:11] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:12] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:12] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:12] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:12] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:30] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:31] RDP (0): Server shows cursor
    [2014-Apr-08 11:30:31] RDP (0): Server hides cursor
    [2014-Apr-08 11:30:31] RDP (0): Server shows cursor
    [2014-Apr-08 14:45:21] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 14:45:21] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 14:45:21] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 15:11:03] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 15:11:03] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 15:11:03] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 15:11:03] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 15:11:03] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-08 15:11:03] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 15:11:03] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 15:11:03] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 15:11:03] RDP (0): client version: 8.0.24428
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 15:11:03] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 15:11:03] RDP (0): Server supports RAIL
    [2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 15:11:04] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 15:11:04] RDP (0): Server supports RAIL
    [2014-Apr-08 15:11:04] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 15:22:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 15:22:36] RDP (0): Disconnect initiated by server
    [2014-Apr-08 15:22:41] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 15:22:41] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 15:22:41] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 16:29:11] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:michele.lefebvre
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-08 16:29:11] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-08 16:29:11] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 16:29:11] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-08 16:29:11] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-08 16:29:11] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-08 16:29:11] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-08 16:29:11] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-08 16:29:11] RDP (0): client version: 8.0.24428
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-08 16:29:11] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 16:29:12] RDP (0): Server supports RAIL
    [2014-Apr-08 16:29:12] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-08 16:29:51] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-08 16:29:51] RDP (0): Disconnect initiated by server
    [2014-Apr-08 16:29:56] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-08 16:29:56] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-08 16:29:56] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-08 16:37:07] RDP (0): *** Application terminated ***
    [2014-Apr-09 09:24:29] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 09:24:29] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 09:24:29] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 09:24:29] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 09:24:29] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-09 09:24:29] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 09:24:29] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 09:24:29] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 09:24:29] RDP (0): client version: 8.0.24428
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 09:24:29] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 09:24:29] RDP (0): Server supports RAIL
    [2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 09:24:45] RDP (0): Server hides cursor
    [2014-Apr-09 09:24:46] RDP (0): Server shows cursor
    [2014-Apr-09 09:24:46] RDP (0): Server hides cursor
    [2014-Apr-09 09:24:49] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:08] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:10] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:15] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:27] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:30] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:31] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:33] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:34] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:38] RDP (0): Server hides cursor
    [2014-Apr-09 09:25:48] RDP (0): Server shows cursor
    [2014-Apr-09 09:25:50] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:40] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:40] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:40] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:40] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:40] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:40] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:41] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:41] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:41] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:41] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:41] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:53] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:53] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:53] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:53] RDP (0): Server shows cursor
    [2014-Apr-09 09:26:58] RDP (0): Server hides cursor
    [2014-Apr-09 09:26:58] RDP (0): Server shows cursor
    [2014-Apr-09 09:27:20] RDP (0): Server hides cursor
    [2014-Apr-09 09:27:22] RDP (0): Server shows cursor
    [2014-Apr-09 09:27:23] RDP (0): Server hides cursor
    [2014-Apr-09 09:27:23] RDP (0): Server shows cursor
    [2014-Apr-09 10:10:53] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 10:10:53] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-09 10:10:53] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-09 10:10:56] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 10:10:56] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 10:10:56] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:10:56] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:10:56] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-09 10:10:56] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 10:10:56] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 10:10:56] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 10:10:56] RDP (0): client version: 8.0.24428
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 10:10:56] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:10:56] RDP (0): Server supports RAIL
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:10:56] RDP (0): Server supports RAIL
    [2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:12:00] RDP (0): Server hides cursor
    [2014-Apr-09 10:12:01] RDP (0): Server shows cursor
    [2014-Apr-09 10:16:50] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 10:16:50] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-09 10:16:50] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-09 10:22:22] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 10:22:22] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 10:22:22] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:22:22] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en1 af=30 (AF_INET6) addr=fe80::ee35:86ff:fe3b:e3d8%en1 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:22:22] RDP (0): en1 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-09 10:22:22] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 10:22:22] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 10:22:22] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 10:22:22] RDP (0): client version: 8.0.24428
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 10:22:22] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:22:22] RDP (0): Server supports RAIL
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:22:22] RDP (0): Server supports RAIL
    [2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:26:40] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
    [2014-Apr-09 10:26:40] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 10:26:40] RDP (0): *** Application terminated ***
    [2014-Apr-09 10:27:28] RDP (0): *** Application terminated ***
    [2014-Apr-09 10:28:36] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:m
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 10:28:36] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 10:28:36] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:28:36] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 10:28:36] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
    [2014-Apr-09 10:28:36] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 10:28:36] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 10:28:36] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 10:28:36] RDP (0): client version: 8.0.24428
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 10:28:36] RDP (0): Resolved '192.168.16.25' to '192.168.16.x' using NameResolveMethod_DNS(1)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:28:36] RDP (0): Server supports RAIL
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 10:28:36] RDP (0): Server supports RAIL
    [2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 11:33:11] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Apr-09 11:33:11] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
    User Message : Failed to read from socket: -1
    [2014-Apr-09 11:33:11] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Apr-09 11:33:18] RDP (0): Final rdp configuration used: screen mode id:i:2
    use multimon:i:1
    session bpp:i:24
    full address:s:192.168.16.x
    audiomode:i:0
    username:s:michele.lefebvre
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:0
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com:1
    bookmarktype:i:3
    use redirection server name:i:0
    [2014-Apr-09 11:33:18] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Apr-09 11:33:18] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 11:33:18] RDP (0): gif0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): stf0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Apr-09 11:33:18] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
    [2014-Apr-09 11:33:18] RDP (0): en1 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en4 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): en3 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Apr-09 11:33:18] RDP (0): --- END INTERFACE LIST ---
    [2014-Apr-09 11:33:18] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Apr-09 11:33:18] RDP (0): client version: 8.0.24428
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Apr-09 11:33:18] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 11:33:19] RDP (0): Server supports RAIL
    [2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2014-Apr-09 11:33:19] RDP (0): Server supports RAIL
    [2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2014-Apr-09 11:33:34] RDP (0): Server hides cursor
    [2014-Apr-09 11:33:38] RDP (0): Server shows cursor
    Any help would be appreciated.

    Hi,
    A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a restart. On a datastream socket, the
    connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent an RST packet). This error is also possible on a datagram
    socket; for instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable.
    Please check the following:
    1. Ping the remote host you were connected to. If it does respond, this problem might have been a transient one (so you can reconnect now), or the server application you were
    connected to might have terminated (so you might not be able to connect again).
    2. Type tracert at the command prompt to determine the path to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end,
    but it might help to identify if the problem is somewhere along the way.
    3. Check if there is any related error log in the server side.
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • How to avoid a SocketException: Connection reset by peer

    Hi,
    My problem sounds very simple at first, but I couldn't figure out how to get out of it. It's tricky.
    A have a JSP page which makes some processing and yields output to the user. Everything runs OK, until the user decide to stop the window (or to close the window) before the results render to the browser. When the next browser tries to load this page, the right page is loaded, but before it, the error garbage (error page, stack trace) from the previous user is showed in the browser...the exception is SocketException: Connection Reset by Peer.
    As I could see in the error log for the web server, the server flushes the page to the client browser, but the browser closed the HTTP connection, then this error is returned. That's OK, but this error output that was not sent appears to be "stored" somewhere in the server, and then is sent to the next client that requests the page. I tried to clear the buffer with out.clearBuffer() in the beginning of the page, but it didn't work.
    The solution would simply be to ignore this error output, i.e., to clean the output before the next user try to load the page. but I don't know how to do that.
    Sorry about the long posting, I hope I was clear in my explanation. I am using Websphere Studio Testing Web Server...and this situation happens on any browser (the problem seems to be in the server).
    Thanks in advance,
    Tiago.

    try using out.flush() in your code, use finalize ??
    out.flush();
    out.close();
    all the best !

  • Javax.servlet.ServletException: Connection reset by peer....Help needed..

    Initially, when I clicked on my JSPs, everything was fine. I was able to retrieve data successfully from all the JSPs. However, after much clicking through the JSPs. I was not able to access the JSPs and the Internal Servlet Error was shown.
    Below is my Tomcat.log:
    Context log: path="/Aedge" Error in jsp service() : Connection reset by peer: socket write error
    javax.servlet.ServletException: Connection reset by peer: socket write error
         at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:375)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
         at org.apache.tomcat.core.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:163)
         at org.apache.tomcat.servlets.DefaultServlet.doGet(DefaultServlet.java:187)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
         at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559)
         at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:160)
         at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
         at java.lang.Thread.run(Unknown Source)
    Context log: path="/Aedge" <b>Internal Servlet Error:</b><br>.....
    What is the problem here? How can I solve this as I had to restart my Tomcat once a while due to this problem.

    ok.. I have db classes where all my sql statements methods are being displayed.. In each db class, there will be a getInstance() method to create the connection. Below is one of my db class.. How to I modified the things you had mentioned in my codes..
    package aedgeSoft.access;
    import aedgeSoft.business.*;
    import java.sql.*;
    import java.util.*;
    import java.util.Date;
    import java.io.*;
    public class DBMemberType
         private Connection con;
         private static DBMemberType instance = null;
         public static DBMemberType getInstance()
              try
                   if(instance==null)
                        instance = new DBMemberType();
              catch(SQLException e)
                   System.out.println("Problems with loading database in DBMemberType");
              catch(ClassNotFoundException e)
                   System.out.println("Problems with loading db driver in DBMemberType");
              finally
                   return instance;
         private DBMemberType() throws SQLException, ClassNotFoundException
              try{
              Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
              con = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;user=username;password=password;DatabaseName=db");
              catch(InstantiationException e)
                   e.printStackTrace();
              catch(IllegalAccessException e)
                   e.printStackTrace();
         //add memberType
         public boolean addMemberType(MemberType mt)
    ..........

  • Re: Connection reset by peer: Connection reset by peer

              >This is not a problem. It is an error message that you can safely ignore (that
              we should not be printing) and have fixed in version 6.0.
              Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem for us.
              Indeed we just ignored this exception in 5.1, but today with 6.1sp2, we get it
              each time we do a RequestDispatcher.forward(). The forward is done, but every
              attributes set on the request are lost !!
              At first I thought it was related with the NT Muxer, or the NT Performance Pack,
              I removed the property NativeIOEnabled but I still get a :
              ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection reset by
              peer: socket write error
                   at java.net.SocketOutputStream.socketWrite(Native Method)
                   at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
                   at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
                   at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
                   at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
                   at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
                   at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
                   at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
                   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
                   at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
                   at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
                   at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
                   at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
                   at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
                   at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

              Yann,
              This is not a J2EE Connector problem. From the stack trace it looks like you might
              have better luck posting this to the Servlet newsgroup.
              Also, just so that you are aware, this newsgroup is not monitored regularly so
              if your issue/question is not getting answered in a timely manner, please send
              a request to BEA Support.
              >
              >>This is not a problem. It is an error message that you can safely ignore
              >(that
              >we should not be printing) and have fixed in version 6.0.
              >
              >--
              >
              >Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem
              >for us.
              >Indeed we just ignored this exception in 5.1, but today with 6.1sp2,
              >we get it
              >each time we do a RequestDispatcher.forward(). The forward is done, but
              >every
              >attributes set on the request are lost !!
              >At first I thought it was related with the NT Muxer, or the NT Performance
              >Pack,
              >I removed the property NativeIOEnabled but I still get a :
              >
              >ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection
              >reset by
              >peer: socket write error
              >     at java.net.SocketOutputStream.socketWrite(Native Method)
              >     at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
              >     at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
              >     at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
              >     at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
              >     at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
              >     at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
              >     at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
              >     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
              >     at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
              >     at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
              >     at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
              >     at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
              >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
              >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
              >     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
              >     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
              >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              >
              

  • (104) Connection reset by peer

    Dears,
    I have a web Application which works fine when accessed from other machines except one. Only in that machine I get an error
    **(104) Connection reset by peer**
    Please help me to solve this problem.

    monoranjang wrote:
    Even I thought that it is a bug in JSP. Good because it is.
    But if it a bug then the issue should occur in all the computers, why is it from a specific computer? I don't know. Some really bad coding?
    We could not reproduce this issue from any other computers except that one.Doesn't really matter does it?
    I mean you are the server and you are aborting the connection for some reason.

  • Broken Pipe/Connection Reset By Peer IO Exceptions

    Can someone explain what causes a connection reset by peer exception vs.
              a Broken Pipe IO exception? I realize they are generally caused by
              someone hitting stop, closing their browser, hitting a different link,
              etc.. but I was trying to understand what might cause a connection
              reset by peer exception vs. a broken pipe exception. I've added code to
              my servlet to suppress the "Connection Reset By Peer" socket exceptions
              but I'm wondering if I should do the same with Broken Pipe. Also, are
              there are other types of similar exceptions that can occur when users
              get impatient.. Thanks
              Kirk
              

    I do not have an idea about your application server but i do know how i solved it in weblogic. Just see whether this is helpful to you.
    Points to be sure of........
    1) Make sure that when ever you request a connection from a pool, after you are done with it return it. If you are not returning it and trying to use that reference again, this problem will occur.
    2) Look at the capabilities of your app server. Set the connection pool such that
    a) All the connections are checked at regular interval with some default select statement from any table in the database.
    b) Connections are check when the connection is checked out and returned to the pool.
    I the connection object is not ready , close it and create a new one. The app server which manages the pool should implement these feature so that when you get the connection - its the tested and working object.
    If your app server does not support - then think of ways you testing it before you using it(Anyway this is not the good solution).

Maybe you are looking for