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 / C++ / MFC
  4. Can't open listening socket on Win2k3 Server

Can't open listening socket on Win2k3 Server

Scheduled Pinned Locked Moved C / C++ / MFC
c++questionsysadminwindows-adminjson
2 Posts 1 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.
  • J Offline
    J Offline
    Jon Betzold
    wrote on last edited by
    #1

    I can't seem to open a listening socket on Windows Server 2003. The very same code has run on NT4 and Win2k for years. But when I try to run it on Win2k3, it fails to create a listening socket. The code is a C++ wrapper for the Windows Socket API (MFC Socket classes are mostly useless). I don't believe there is anything unusual about the way the code was implemented. It has never given us any trouble in the past. I guess my question is this: Is there something more that I must know/do in order to run a socket server (i.e. listening socket) on Win2k3. Is this part of MS's Secure Computing Initiative. Or am I just overlooking the obvious? Any help would be greatly appreciated. Thanks, Jon

    J 1 Reply Last reply
    0
    • J Jon Betzold

      I can't seem to open a listening socket on Windows Server 2003. The very same code has run on NT4 and Win2k for years. But when I try to run it on Win2k3, it fails to create a listening socket. The code is a C++ wrapper for the Windows Socket API (MFC Socket classes are mostly useless). I don't believe there is anything unusual about the way the code was implemented. It has never given us any trouble in the past. I guess my question is this: Is there something more that I must know/do in order to run a socket server (i.e. listening socket) on Win2k3. Is this part of MS's Secure Computing Initiative. Or am I just overlooking the obvious? Any help would be greatly appreciated. Thanks, Jon

      J Offline
      J Offline
      Jon Betzold
      wrote on last edited by
      #2

      Win2k3 requires a listening socket to be bound to a specific IP, whereas Win2k and NT4 do not. We were not binding to a specific IP. One small change, and the code works on all 3 operating systems. Jon

      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