ESX (VMWare VSphere)

Discussion in 'ESET NOD32 Antivirus' started by Temmu, Oct 19, 2010.

Thread Status:
Not open for further replies.
  1. Temmu

    Temmu Registered Member

    Joined:
    Jan 25, 2008
    Posts:
    24
    Greetings!

    I moved my physical ESET NOD32 server so that it became a virtual machine running on ESX v4.1
    I used the VShpere client, import machine tool to accomplish that.

    My virtual machine sees the network and the internet just fine and has no meaningful errors in its server log. It's running Win serv 2003.

    My ESET NOD32 client machines (pcs, servers) now state, cannot contact server.

    We'll use the default port, 2223 for admin server for example.
    Windows firewall is OFF on the ESET NOD32 server.
    Is there anything in ESX / VSphere that prevents certain ports from being used? A place to "open the port"?

    RSVP

    Thanks in advance... :)
     
  2. Temmu

    Temmu Registered Member

    Joined:
    Jan 25, 2008
    Posts:
    24
    ... It resolved itself overnight.

    Apparently, the ESET server simply caught up with itself.

    Thanks for looking.
     
Thread Status:
Not open for further replies.