Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • 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 (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Ways to re-establish connection between client and server on remoting?

Ways to re-establish connection between client and server on remoting?

Scheduled Pinned Locked Moved C#
sysadminhelpquestionworkspace
2 Posts 2 Posters 0 Views 1 Watching
  • 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.
  • K Offline
    K Offline
    kumar bs
    wrote on last edited by
    #1

    My scenario is: Based on Remoting concept, Server is listening to client on particular port using TCPChannel. Suddenly Server (Listner) went off, which client does not have information. When client sends a message, error is thrown saying "No connection could be made because the target machine actively refused it". Is there any way to re-establish client - server connection? Here Server is using randomly selected ports, so we can't hardcode port at client. Client is getting information of port from configuration file created at user's local directory. Thanks

    M 1 Reply Last reply
    0
    • K kumar bs

      My scenario is: Based on Remoting concept, Server is listening to client on particular port using TCPChannel. Suddenly Server (Listner) went off, which client does not have information. When client sends a message, error is thrown saying "No connection could be made because the target machine actively refused it". Is there any way to re-establish client - server connection? Here Server is using randomly selected ports, so we can't hardcode port at client. Client is getting information of port from configuration file created at user's local directory. Thanks

      M Offline
      M Offline
      mav northwind
      wrote on last edited by
      #2

      From my experience, you only get the exception if you try to call a remote method while the server is down. As soon as the remoting server is running again, all remoting method calls work as if the server was there all the time. If you say that the server is using randomly selected ports, how do your clients connect to the remoting server? You have to give a URI for the remoting server object and part of it is the port, so how can this be "randomly selected"?

      Regards, mav -- Black holes are the places where God divided by 0...

      1 Reply Last reply
      0
      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.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups