locked
What happens on port 2179 ? RRS feed

  • Question

  • Hi !

    I am working in C#, trying to build hyper-v manager.

    Is there any way to code my own remote desktop client for guest machines ?

    working with RDP is a later thing. What I've found so far is (correct me if I am wrong):

    Windows's client connects to the server on port 2179. Then some handshaking, metadata exchange happens on port 2179 and client gets data on some 49xxx port.

    What I don't understand is what happens on port 2179 ? Is there any protocol specification I should look for ?

    Thanks


    Thanks

    Living on Earth may be expensive, but did you know that it includes a free trip around the sun? Isn't that worth it?


    • Edited by Omie Friday, June 15, 2012 10:49 AM
    Friday, June 15, 2012 9:41 AM

Answers

All replies

  • Hiya,
    default, RDP uses 3389.

    Remote Desktop Protocol
    http://en.wikipedia.org/wiki/Remote_Desktop_Protocol


    That can however be changed if required.
    Friday, June 15, 2012 10:01 AM
  • Hi Jesper,

    Thanks for the response but no, I am not looking for that part.



    Thanks

    Social lounge for MSDN forum users :-)
    Living on Earth may be expensive, but did you know that it includes a free trip around the sun? Isn't that worth it?

    Friday, June 15, 2012 10:06 AM
  • Hiya,

    Then if you want to know which application is using that port or any other port on your server you can open a cmd and write

    netstat -ab

    Besides that, here is the complete registrered port list:

    http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml

    It takes a little while to load.


    Friday, June 15, 2012 10:08 AM
  • Thanks again but I don't think you've understood my question. If you have hyper-v configured and have a guest machine added, connect to it and then use command 'netstat -a'. Should help you to understand.

    Apparently, hyper-v host listens on port 2179 for console requests, when it gets one, it starts feeding on decided port for console of guest machine.

    What I want to know is what should I say on port 2179 to get the console of guest on my specified port ?


    Thanks

    Living on Earth may be expensive, but did you know that it includes a free trip around the sun? Isn't that worth it?


    • Edited by Omie Friday, June 15, 2012 10:49 AM
    Friday, June 15, 2012 10:12 AM
  • Hiya,

    Thats actually quite interesting.

    Almost like opening Pandoras box of HyperV - "So what hides behind port number 2179"

    vmms.exe or VMConnect.exe

    VMConnect to Hyper-V hosts, Port: 2179; Protocol: RDP—VMConnect is an application that's part of Hyper-V Manager and VMM; it lets you connect to a console session of a Hyper-V VM. By default VMConnect uses port 2179.

    http://www.virtuatopia.com/index.php/The_Hyper-V_Virtual_Machine_Connection_Tool

    http://www.windowsitpro.com/article/microsoft-system-center-virtual-machine-manager/tcp-ip-ports-used-by-vmm-2008

    Sorry for the misunderstanding on the question :)

    Friday, June 15, 2012 10:40 AM
  • Right ! But my question is still unanswered.

    I have tried connecting to host on port 2179 [crap! I typed it 2197 by mistake]. Doesn't quite work..


    Thanks

    Living on Earth may be expensive, but did you know that it includes a free trip around the sun? Isn't that worth it?

    Friday, June 15, 2012 10:46 AM
  • Hi,

    According to the description, it seems that what you want is a developing issue, it is recommended that you perform the further research in development community so that you can get the most qualified pool of response. Thanks for your understanding.

    Wednesday, June 20, 2012 10:11 AM
  • Hi!

    Sorry for the late reply. I figured its VMRDP protocol. documentation is available here:

    http://msdn.microsoft.com/en-us/library/cc242359(v=prot.10).aspx


    Thanks

    Living on Earth may be expensive, but did you know that it includes a free trip around the sun? Isn't that worth it?

    • Marked as answer by Vincent Hu Monday, July 9, 2012 3:30 AM
    Friday, June 29, 2012 8:52 AM