Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. NXCsession timeout error -- is there any way to get more information?

NXCsession timeout error -- is there any way to get more information?

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 16.0k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Z
    Z
    zshnet
    wrote on last edited by
    #1

    Hi all,

    I'm having an issue with accessing my main NetXMS server from a separate private network. I have a computer with  a public address through 1 to 1 NAT, which tries to use nxshell to run a script. This computer talks to the NetXMS server's public IP address (which I can use to access the NetXMS console, so it does work). Any time I try to do this, the process hangs for many minutes (>10) and then eventually ends with an NXCsession timeout error.

    Is there anywhere I can find more information? I didn't see anything in the logs, but is there a keyword I should be looking for? It seems to be specific to this private network (others can access the NetXMS server fine). When I run packet capture on one of the intervening routers, I can see that the two talk and send acknowledgement packets, but no data is ever exchanged.

    Thanks,
    Zach

    P.S.
    For clarification, I have the following topology when trying to access NetXMS

    |----------------Private Network 1----------------- ------------------------------------------------| ------------Public Internet-----------| --------------------Private Network 2-----------------------------------------------------------------|

    Server with NAT-ed public IP address, ==> Router with public internet access====>        Fiber head-end      ====>  Router with public internet access====> NetXMS server with public IP address
    so it can reach public internet                                                                                        to public internet

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      it's definitely a network issue. One possible cause could be MTU mismatch and/or disabled fragmentation somewhere along the route. This could explain why small packets (connection setup and ack) pass through while larger packets with data cannot.

      Best regards,
      Victor

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups