Ports not opening on windows server 2019

Timmy Olsson 20 Reputation points
2023-11-28T18:30:35.1033333+00:00

Hello, i am out of ideas, as the title says i simply cannot seem to get port 25734 opened in local Lan.
This is the setup:

Network: Unifi UDM Pro (All local traffic is allowed and also added the ports to allowed on all devices locally)

Server - Windows server 2019 (This server is also the DNS server for the network)

Client1 - Windows 10

Client2 - Windows 10

So ill try and explain as good as i can:
I have telnet installed and on Client2 the port is opened and i can telnet to it from all clients and the server aswell. I need to open the port on the server though and not on the client.
I have a listener shown in both netstat -a and also shown in the resource monitor where the port says allowed aswell.

On the server i have added exceptions in the firewall, i have added the exceptions in the antivirus (Bitdefender), i have disabled the firewall and antivirus and it still says filtered when checking the port and also telnet does not work to the server (The exact same settings with both firewall and antivirus active works when telnet to Client2 instead of the server).

I have 2 other ports opened the exact same way on the server and i can telnet to those from all the clients, but if i open a new port it will simply not open, even if i try another port.

I have tried to disable all i can think of and it still works like a charm to Client2 but the server refuses to let me in.

i need the port open for the solidworks license manager which we now have to run on a client instead of the server since i cannot get the port to open on the server.

Sorry if i am missing information here but tell me what information you need and ill provide it.

A Summary if i was unclear:
I want to telnet to port 25734 from all clients to the server.

I at the moment can telnet from all the clients and the server to Client2 on port 25734

I have the same listener installed on the server and Client2

I have the same settings in firewalls, antivirus and network on Client2 and the server (The same rules on opening and allowing both the port 25734 and the program that runs the listener)

I can telnet to localhost 25734 on the server without problems so the listener should be ok

In the resource manager it says the ports are allowed for communication and that its listening, netstat -a also shows that the server is listening on the port.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,607 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2023-11-30T13:55:15.3033333+00:00

    Ok, new info, installing other applications on a domain controller isn't recommended. One option may be to install the hyper-v role (as only role) on host, then stand up two virtual machines. One for active directory domain services and another as the application server.

    --please don't forget to close up the thread here by marking answer if the reply is helpful--

    1 person found this answer helpful.

7 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-11-28T18:39:13.5266667+00:00

    i have disabled the firewall and antivirus and it still says filtered when checking the port and also telnet does not work to the server

    Sounds like you'll need to reach out to the solidworks software vendor for support.

    --please don't forget to close up the thread here by marking answer if the reply is helpful--


  2. Anonymous
    2023-11-28T18:47:27.2333333+00:00

    There's no difference in the way the windows firewall works here. Since you have third-party firewall you could ask them for assistance as well, or stand up a new one (2019 fully patched OOB) for testing.

    --please don't forget to close up the thread here by marking answer if the reply is helpful--


  3. Anonymous
    2023-11-28T19:08:10.6266667+00:00

    Ok, well we have no idea here how cleanly that uninstall might be. You could try standing up a new 2019 patched fully for testing.

    --please don't forget to close up the thread here by marking answer if the reply is helpful--


  4. Anonymous
    2023-11-28T19:15:34.9133333+00:00

    Sounds good, the software vendor is going to be your best resource to trouble shoot this problem.

    --please don't forget to close up the thread here by marking answer if the reply is helpful--