Results 1 to 5 of 5

Thread: Comm Server Problem with NR

  1. #1
    Join Date
    Jun 2005
    Posts
    760

    Default Comm Server Problem with NR

    Here's my setup. I have G4.0.15 (build 371) and NR2 (build 2.0.0.90) on PC-1 called "emma" which is also the default host to NR. PC-2 is called "home-auto" and also runs G4 (same ver). This is the machine I'm having a problem with. It can't seem to stay connected to NR and very few commands like NetRemote.SetVariable(...) get through. Below is what I see in the Girder Log dDisplay:
    Code:
    Time    Date    Source    Details    Payloads
    21:12:02:391    8/21/2007    NetRemote    Synchronising client EMMA {b489fb44-241c-4475-8d23-fa045aaa4e0f}
    21:12:02:381    8/21/2007    NetRemote    Connected
    21:12:02:371    8/21/2007    NetRemote    Starting feedback thread for EMMA
    21:12:02:361    8/21/2007    NetRemote    Registering NR client
    21:12:02:350    8/21/2007    NetRemote    Adding client 192.168.1.79
    21:12:02:340    8/21/2007    NetRemote    Connection from 192.168.1.79:1367
    21:12:02:300    8/21/2007    Communication Server    New Client Connection    192.168.1.79    1367
    21:12:02:320    8/21/2007    NetRemote    Exiting feedback thread for EMMA
    21:12:02:310    8/21/2007    NetRemote    Closing client for EMMA
    21:12:02:300    8/21/2007    NetRemote    Unregistering NetRemote client 192.168.1.79:1318
    21:12:02:290    8/21/2007    Communication Server    Connection Authenticated 192.168.1.79 NetRemote
    21:12:02:280    8/21/2007    NetRemote    Connection closing 192.168.1.79:1318
    21:12:02:280    8/21/2007    Communication Server    Close Connection    192.168.1.79    1318
    21:12:02:270    8/21/2007    Communication Server    Close Connection
    21:11:56:252    8/21/2007    NetRemote    Synchronising client EMMA {b489fb44-241c-4475-8d23-fa045aaa4e0f}
    21:11:56:232    8/21/2007    NetRemote    Connected
    21:11:56:212    8/21/2007    NetRemote    Starting feedback thread for EMMA
    21:11:36:183    8/21/2007    NetRemote    Registering NR client
    21:11:36:183    8/21/2007    NetRemote    Adding client 192.168.1.79
    21:11:36:173    8/21/2007    NetRemote    Connection from 192.168.1.79:1318
    21:11:36:153    8/21/2007    Communication Server    New Client Connection    192.168.1.79    1318
    21:11:36:153    8/21/2007    Communication Server    Connection Authenticated 192.168.1.79 NetRemote
    21:11:31:486    8/21/2007    NetRemote    Exiting feedback thread for EMMA
    21:11:31:486    8/21/2007    NetRemote    Closing client for EMMA
    21:11:31:466    8/21/2007    NetRemote    Unregistering NetRemote client 192.168.1.79:1111
    21:11:31:456    8/21/2007    NetRemote    Connection closing 192.168.1.79:1111
    21:11:31:436    8/21/2007    Communication Server    Close Connection    192.168.1.79    1111
    21:11:31:376    8/21/2007    Communication Server    Close Connection
    21:09:56:630    8/21/2007    NetRemote    Synchronising client EMMA {b489fb44-241c-4475-8d23-fa045aaa4e0f}
    21:09:56:620    8/21/2007    NetRemote    Connected
    21:09:56:610    8/21/2007    NetRemote    Starting feedback thread for EMMA
    21:09:56:600    8/21/2007    NetRemote    Registering NR client
    21:09:56:580    8/21/2007    NetRemote    Adding client 192.168.1.79
    21:09:56:570    8/21/2007    NetRemote    Connection from 192.168.1.79:1111
    21:09:56:560    8/21/2007    Communication Server    New Client Connection    192.168.1.79    1111
    21:09:56:540    8/21/2007    NetRemote    Exiting feedback thread for EMMA
    21:09:56:530    8/21/2007    NetRemote    Closing client for EMMA
    21:09:56:520    8/21/2007    NetRemote    Unregistering NetRemote client 192.168.1.79:1061
    21:09:56:510    8/21/2007    Communication Server    Connection Authenticated 192.168.1.79 NetRemote
    21:09:56:510    8/21/2007    NetRemote    Connection closing 192.168.1.79:1061
    21:09:56:490    8/21/2007    Communication Server    Close Connection    192.168.1.79    1061
    21:09:56:490    8/21/2007    Communication Server    Close Connection
    21:09:50:461    8/21/2007    NetRemote    Synchronising client EMMA {b489fb44-241c-4475-8d23-fa045aaa4e0f}
    21:09:50:451    8/21/2007    NetRemote    Connected
    21:09:50:441    8/21/2007    NetRemote    Starting feedback thread for EMMA
    21:09:30:432    8/21/2007    NetRemote    Registering NR client
    21:09:30:402    8/21/2007    NetRemote    Adding client 192.168.1.79
    21:09:30:402    8/21/2007    NetRemote    Connection from 192.168.1.79:1061
    21:09:30:392    8/21/2007    Communication Server    New Client Connection    192.168.1.79    1061
    21:09:30:392    8/21/2007    Communication Server    Connection Authenticated 192.168.1.79 NetRemote
    21:09:29:150    8/21/2007    NetRemote    Exiting feedback thread for EMMA
    21:09:29:140    8/21/2007    NetRemote    Closing client for EMMA
    21:09:29:130    8/21/2007    NetRemote    Unregistering NetRemote client 192.168.1.79:4806
    21:09:29:120    8/21/2007    NetRemote    Connection closing 192.168.1.79:4806
    21:09:29:090    8/21/2007    Communication Server    Close Connection    192.168.1.79    4806
    21:09:29:090    8/21/2007    Communication Server    Close Connection
    Why is the Communication Server issuing a command to "Communication Server ... Close Connection"? I'm only guessing this is the problem. What initiates this command? Any suggestions on how to debug? Help most appreciated!

  2. #2
    Join Date
    May 2004
    Location
    Cardigan, UK
    Posts
    9,278

    Default

    First of all I'd suggest using the latest version of NR2 (2.0.0.99) - if that doesn't fix the problem, then go to File|Properties|Plugins and delete the Girder plugin instance - and let auto discovery find that Girder instance (make sure that File|Properties|General|Disable Auto Discovery is not checked).
    --Rob

  3. #3
    Join Date
    Jun 2005
    Posts
    760

    Default

    Thanks Rob. Did the upgrade and let NR rediscover the other G4 instance. It shows the host name now instead of the IP address so we'll see if that helps. So far it doesn't, but I'll try and restart everything later today and see if that helps.

    I did notice the following in DebugView on the home-auto PC. Is this a clue?
    Code:
    [1592] CSConnection::Send Error: : Connection reset by peer (10054) - Closing socket. (2020)

  4. #4
    Join Date
    May 2004
    Location
    Cardigan, UK
    Posts
    9,278

    Default

    How are these PCs connected? WiFi? It certainly sounds as though the connection is breaking which I wouldn't expect with a wired connection (unless there's a dodgy switch/hub in the way).
    --Rob

  5. #5
    Join Date
    Jun 2005
    Posts
    760

    Default

    You nailed it Rob! While Gigabit network adapter cards may be 10x faster, they appear to have 10x the problems. I went back to a 100 Base-t card and all is now working... except for NR. The state logic for hidden windows appears to have changed polarity between v.90 and v.99 but this is the wrong forum to gripe about that. Thanks again!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •