Post reply

ports used by EM

  • March 19, 2004 at 8:39 am

    #82472

    Does anybody know why EM would try to use TCP ports 445 and 139? Using ethereal, I've seen this when trying to view server properties. Firewall blocks these ports, which leads EM to try other ports, which leads to long response times on the client (specifically, after right clicking the server name, it takes a long time for the context menu to be displayed).

  • March 19, 2004 at 2:15 pm

    #499584

    It is NOT EM who does that it just happens indirectly.

    Those ports are used by NBT or netbios over tcp/ip it is all because of the NAME resolution mechanism. To minimize that you may try to create either an alias of your server name with the client network utility pointing to the right ip address or create an entry on the hosts file on your workstation. That will prevent name resolution outside of your box.

    HTH


    * Noel

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply