I just upgraded to 6.2 (yay me).

I installed the remote agent onto a laptop (outside the network) and I want the info reported back to the server. I do not have a remote collector (don’t want one, just report directly to the server is fine).

I used the remote agent install from the server.

In the log (c:\program files\spiceworks\agent\log\log) on the remote machine, I get a “connectivity test to :9676 failed” error.

I’ve tried 80, 443, and 9676 with the same results.

Do I need that port opened on network’s FW? If so, which type, TCP, UDP?

Thanks

Scott

3 Spice ups

Do you have port 443 NAT’ed through your firewall? That’s all you need to get external communication to/from your agent to work.

Can you summarize your settings (exactly how you typed them) during setup, of course “anonymizing” where necessary?

1 Spice up

More correctly you need the SSL port you setup during the Spiceworks install port forwarded. By default it is 443 unless the install found it in use, then it automatically suggests 9676. You will port forward that port selecting TCP as it is standard HTTPS traffic.

1 Spice up

Jared is correct, I’m assuming a default install of 443. Thanks for clarifying!

1 Spice up

okay! opening 443 on the FW to the server got that part working.

now the error is:

okay! opening 443 on the FW to the server got that part working.

now the error is:

2013-03-19 11:40:10,749 [6] DEBUG Spiceworks.Agent.Service.Message.Post - posting to https:///dataloader/loaddata_agent_respond

2013-03-19 11:40:11,374 [6] DEBUG Spiceworks.Agent.Service.Agent - connectivity test to succeeded

2013-03-19 11:40:11,374 [6] DEBUG Spiceworks.Agent.Service.Agent - connectivity established to app server https:///; sending system data

2013-03-19 11:40:11,390 [6] DEBUG Spiceworks.Agent.Service.Agent - initiating authorization request to central server at https:///

2013-03-19 11:40:11,452 [6] DEBUG Spiceworks.Agent.Common.Security.Util - Current user NT AUTHORITY\SYSTEM has admin role

2013-03-19 11:40:11,624 [6] DEBUG Spiceworks.Agent.Service.Message.Post - registering with the central server before proceeding…

2013-03-19 11:40:11,671 [6] DEBUG Spiceworks.Agent.Service.Message.CryptoHelper - generating keypair

2013-03-19 11:40:12,609 [6] DEBUG Spiceworks.Agent.Service.Message.Post - posting to https:///dataloader/loaddata_central_register

2013-03-19 11:40:12,640 [4] INFO Spiceworks.Agent.Service.Agent - stopped Spiceworks Agent

2013-03-19 11:40:14,624 [1] DEBUG Spiceworks.Agent.Common.Project - No other instances of Spiceworks Agent detected as running

2013-03-19 11:40:14,640 [1] DEBUG Spiceworks.Agent.Service.Agent - Instantiating agent service

2013-03-19 11:40:14,640 [4] INFO Spiceworks.Agent.Service.Agent - started Spiceworks Agent version 6.2.873

2013-03-19 11:40:14,640 [4] INFO Spiceworks.Agent.Service.Agent - setting scan interval to every 600 minutes

2013-03-19 11:40:14,640 [6] DEBUG Spiceworks.Agent.Service.Agent - scan is now due

2013-03-19 11:40:14,640 [4] INFO Spiceworks.Agent.Service.Agent - setting connectivity interval to every 2 minutes

2013-03-19 11:40:28,796 [6] DEBUG Spiceworks.Agent.Service.Message.Post - posting to https:///dataloader/loaddata_agent_respond

2013-03-19 11:40:29,030 [6] DEBUG Spiceworks.Agent.Service.Agent - connectivity test to :443 succeeded

2013-03-19 11:40:29,030 [6] DEBUG Spiceworks.Agent.Service.Agent - connectivity established to app server https:///; sending system data

2013-03-19 11:40:29,030 [6] DEBUG Spiceworks.Agent.Service.Agent - initiating authorization request to central server at https:///

2013-03-19 11:40:29,046 [6] DEBUG Spiceworks.Agent.Common.Security.Util - Current user NT AUTHORITY\SYSTEM has admin role

2013-03-19 11:40:29,062 [6] DEBUG Spiceworks.Agent.Service.Message.Post - registering with the central server before proceeding…

2013-03-19 11:40:29,390 [6] DEBUG Spiceworks.Agent.Service.Message.Post - posting to https:///dataloader/loaddata_central_register

2013-03-19 11:40:29,452 [6] ERROR Spiceworks.Agent.Service.Message.Post - central server reports authentication failure: Fail: bad registration parameters

2013-03-19 11:40:29,452 [6] ERROR Spiceworks.Agent.Service.Agent - failed to perform initial identification with server

2013-03-19 11:40:29,452 [6] WARN Spiceworks.Agent.Service.Agent - Server handshake failed.

Bad password. This is the only remote agent right? Go back in to the remote sites and agents and retype the password there and then redo it on the client.

1 Spice up

no dice on that one, Jared.

I’ve retyped the pswd on the agent page and recreated the .msi. Copied the MSI over to the remote machine and ran it (after uninstalling the agent).

Same error. …message.post - “central server reports authentication falure: Fail: bad registration parameters”

…service.agent - failed to perform initial identification with server

…service.agent - server handshake failed.

And, yes, this is the only machine with a remote agent right now. I’m using it as my crash test dummy

hmm not really anything else to it. At this point i’d email support and open a ticket then.

roger that, thanks for your advice.

Scott