UTMStack
-
|
The notes on the Integration window say that the Windows agent only works on Windows 2016 R2 and above. Is this correct? I am trying to install it on a Windows 2012 R2 server and keep getting a message saying that port 9000 and 50051 need to be open. They are open everywhere on the server. We have a plan to upgrade that server soon, but I am trying to get some visibility into the network prior to the upgrade. Does this also mean the agent will not work on Windows 10/11 Pro? |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 13 replies
-
|
@jjcoker09 To confirm whether ports 9000 and 50051 are open, you can use the following PowerShell commands: PLEASE: remember to replace "your_ip_or_host" with the actual IP address or hostname of your UTMStack Instance. This indicates that ports 9000 or 50051 on your UTMStack Instance are closed, and you need open them for successful communication. |
Beta Was this translation helpful? Give feedback.
-
|
The ports are not responding from the agent machine.
but...on the UTMStack Server:
sudo ufw status
Status: inactive
For iptables, though the ufw is not enabled:
iptables -L -v
Chain DOCKER-INGRESS
(pkts 39) (bytes 2024) (target ACCEPT) (prot tcp) (opt --) (in any) (out any) (source anywhere) (destination anywhere) (tcp dpt:9000)
(pkts 0) (bytes 0) (target ACCEPT) (prot tcp) (opt --) (in any) (out any) (source anywhere) (destination anywhere) (tcp spt:9000 ctstate RELATED,ESTABLISHED)
...same for 50051
netstat -na | grep "9000"
tcp 6 0 0 :::9000 :::* LISTEN
...same for 50051
We used the ISO install to a VM server for the installation and did what we normally do for these installs...we thought. Not sure what we could have missed.
The DOCKER-INGRESS Forward result is below:
(pkts 281) (bytes 17707) (target DOCKER-INGRESS) (prot all) (opt --) (in any) (out any) (source anywhere) (destination anywhere)
Any ideas?
…________________________________
From: Yorjander Hernandez Vergara ***@***.***>
Sent: Friday, January 26, 2024 6:37 AM
To: utmstack/UTMStack
Cc: JJ Coker; Mention
Subject: Re: [utmstack/UTMStack] Windows Agent for UTMStack 10.1.0 and 10.2.0 (Discussion #370)
@jjcoker09<https://github.com/jjcoker09> To confirm whether ports 9000 and 50051 are open, you can use the following PowerShell commands:
Test-NetConnection your_ip_or_host -Port 9000
Test-NetConnection your_ip_or_host -Port 50051
PLEASE: remember to replace "your_ip_or_host" with the actual IP address or hostname of your UTMStack Instance.
If the output includes a warning similar to the following:
WARNING: TCP connect to (your_ip_or_host : 9000) failed
This indicates that ports 9000 or 50051 on your UTMStack Instance are closed, and you need open them for successful communication.
—
Reply to this email directly, view it on GitHub<#370 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFHZZTUVSGDXX56XP334ZF3YQOPRDAVCNFSM6AAAAABCLP72D2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DENJWGU4DG>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
________________________________
This email has been scanned for spam and viruses by Proofpoint Essentials. Click here<https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5f096d230b0f1564aab7204026fa20dba8edc6ad9aa5fc6ac818c48b3f790ee999c6a8df360155d9a493545d0776f64a80dc15f2337cc2b6210fc272f73f8a19d5102563592d35417d66db80c8b8a2adc15adebae03d379bc079d79a2cd05df0b81decc82306cff1c536d5900eb2680e1ca3895374f16ef7f174b9a6882f35064c524c3e608f8f1f69292d2c034b6aa657d38ba7b8f8308043> to report this email as spam.
|
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem. But I instal on UTMServet agent . And it connected to server. But remote agent on other systems imposible to connect |
Beta Was this translation helpful? Give feedback.
-
|
Is it way to add agents to UTMStack? |
Beta Was this translation helpful? Give feedback.
-
|
You may have issues with network routing or firewall. In certain cases it is because UTMStack is on a different network than the agents, and the servers/workstations cannot find the route to the network where UTMStack is located. It could also be that the IP or FQDN that is appearing in the command is not the one you should use in your environment. We're going to need a little more information about your network configuration. For example CIDR of UTMStack, CIDR of the servers or workstations where the agent is being installed, the command you are running to install the agent, of course removing the connection key that appears in the command, etc. |
Beta Was this translation helpful? Give feedback.
-
|
IP For UTMStack is 10.0.0.27/24 . The windows and linux client have the same network. For my comp 10.0.0.17/24 docker_gwbridge Bridge docker0 Bridge - reloved with>> ping The last command is: For windows in PS what is in integration: Anwear for all system is the same: |
Beta Was this translation helpful? Give feedback.
-
|
I'm only having this problem with one network install, but it affects all machines on that network. I have had to fight with the ISO installs for some of the other networks but I think I have that worked out now. It appears that Ubuntu 22.04 latest versions have some problems installing on VM Esxi servers. It errors out in the beginning of the install saying there are integrity issues with the ISO file. I downloaded them separately for the different networks where the problem was occurring, and each had the same issue. For now, I am using a VMDK/VMK that I can just drop in place with 22.04 installed. At this one location, the computers and the UTMStack server are on the same network/subnet. I can nmap to the ports on the UTMStack server and they come up as open (from the machine that is failing the install). I see the ports open on the UTMStack server via netstat and the iptables rules are all set to allow, though UFW is disabled so that should not matter anyway. I wiped the UTMStack server and set it up again using the new VMDK/VMK. I had to configure the default route as part of the initial setup, but everything after that is normal. Same problem on that same network. One machine that is having the problem is a new Windows 11 machine and the other is an older Windows server. The Active Directory there was created initially as part of a Windows SBS system. I am wondering if something is left from the group policies that is causing the problem. I am going to take a standalone machine over there next to test the agent install from it. |
Beta Was this translation helpful? Give feedback.
-
Hi, did you removed the UTMStack's Server IP/URL? or is it missing in the command you are getting from the guide? |
Beta Was this translation helpful? Give feedback.
-
|
Can you please run the following commands and share the output with us? They are basically checking for system minimum requirements and docker services status. |
Beta Was this translation helpful? Give feedback.
-
|
I just snipped an image of HTOP since it was changing and attached it as a jpg. docker service lsID NAME MODE REPLICAS IMAGE PORTS docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES df -hFilesystem Size Used Avail Use% Mounted on
|
Beta Was this translation helpful? Give feedback.
-
|
docker service ls docker ps df -h htop |
Beta Was this translation helpful? Give feedback.
-
|
I got a little more into docker after trying a million different things on my local network to try and isolate the issue. I ran "docker network list" to get a list of the docker networks. That gave me the NETWORK ID of the utmstack_default network. When I ran "docker network inspect NETWORK ID" on that network ID, I discovered that the IP range on it was the same as the VPN range on my firewall. So, I got into my firewall and changed the VPN network there to something different. That did not fix my problem with the agent installs, but I am convinced that the failure MUST have something to do with this. I don't know docker well enough to mess with it. Anyone have any suggestions on what I should do next? If I do another UTMStack install, will it change something if my network gateway isn't pointing to its own VPN zone when the docker networks are being setup? ...I still have a few strands of hair left, but I can't handle too many more failures on this. |
Beta Was this translation helpful? Give feedback.
-
|
This MUST be because of our 10.0.0.X ranges. @TYrorare, you are using the same range I am using and the UTMStack is picking up 10.0.1.X for its docker range. I just completely reinstalled Ubuntu on my network, then reinstalled the UTMStack software after removing the 10.0.1.X VPN zone on my firewall. Still doesn't fix the problem. I don't think the configured install for UTMStack can run properly on a 10.0.0.X network. All of my working installs are on a different range entirely. None of them have had any problems. I will bet if we change our internal range to something other than 10.0.0.X, it will work. I have it running on a 10.10.1.X range as well as 192.168.0.X and 10.10.5.X. I am going to change the range on this network tomorrow and test it. (I'll probably break a few printers and copiers, but it shouldn't be too big a deal. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I can officially say that moving the local network off the 10.0.0.X range fixes this problem. I can't say how much of the 10.0.0.X subnet would be affected. The docker for UTMStack runs on 10.0.1.X so I imagine that subnet would at least have the same problem. In any case, I switched my internal network to 192.168.2.X and let the UTMStack server just pick up a DHCP address on that new range. I didn't change anything else internally on the install or do a reinstall. The agent installs finished perfectly and everything is up and running. I had to reconfigure some printers and the wifi on the network, but everything else worked well. This should probably be in the instructions somewhere...or at least there should be some mention of how to fix it if this range is in use on the local network. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @jjcoker09 thanks for the feed back |
Beta Was this translation helpful? Give feedback.
-
|
Can you explaine, how to change those network addresses? |
Beta Was this translation helpful? Give feedback.
-
|
I may be able to help you with it, depending on how you are setup. Can you describe how your Internet comes into your network and what equipment you have between you and the Internet? Do you have your own firewall? Do you have a server onsite that is responsible for managing your network?
Thanks,
JJ
From: TYrorare ***@***.***>
Sent: Monday, March 4, 2024 4:50 AM
To: utmstack/UTMStack ***@***.***>
Cc: JJ Coker ***@***.***>; Mention ***@***.***>
Subject: Re: [utmstack/UTMStack] Windows Agent for UTMStack 10.1.0 and 10.2.0 (Discussion #370)
Can you explaine, how to change those network addresses?
—
Reply to this email directly, view it on GitHub<#370 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFHZZTQPVEULHYGPUUPDDNDYWRGULAVCNFSM6AAAAABCLP72D2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DMNRVGEYTA>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
…________________________________
This email has been scanned for spam and viruses by Proofpoint Essentials. Click here<https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5f18a4a5553655bf38cbfd088b819af35272d54895b8474b12d0e5995be3494b56a8c021dbf7b73e80cd9ef245f46e4ac134d2bfaf439de71d5a2062a4d920e0b82e8dc690ab65694e7ad7f05b6264dc55ac9614f7c822b970bac4e728234430c5452cd749a78d22502c8410d6e9d731e8740f9b3ece4974fe79f3692afbec726b02f7b7a1b5fc41745e345b739ee2d67ae03eec5e7fbeef88> to report this email as spam.
|
Beta Was this translation helpful? Give feedback.
-
|
So, I install by ISO. My local network CIDR is 10.0.0.0/24 but i have VPN IPsec with same network 10.1 10.2 10.3 ... 10.10. UMstack server has IP 10.0.0.27/ I gave my own Gateaway/Firewall/VPN with address 10.0.0.1 |
Beta Was this translation helpful? Give feedback.
-
|
I ruan the command docker network inspect utmstack_default |
Beta Was this translation helpful? Give feedback.
Ok, I can officially say that moving the local network off the 10.0.0.X range fixes this problem. I can't say how much of the 10.0.0.X subnet would be affected. The docker for UTMStack runs on 10.0.1.X so I imagine that subnet would at least have the same problem. In any case, I switched my internal network to 192.168.2.X and let the UTMStack server just pick up a DHCP address on that new range.
I didn't change anything else internally on the install or do a reinstall. The agent installs finished perfectly and everything is up and running. I had to reconfigure some printers and the wifi on the network, but everything else worked well.
This should probably be in the instructions somewhere.…