Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Unable to Connect PDQ client to PDQ Server

Spire Networkteam

April 07, 2022 16:56

I recently changed AD password and since then my PDQ Deploy and Inventory are not connecting to the PDQ Server. The server is up, I can login fine, open PDQ on it and it works fine but I cannot connect to it from my laptop as I have always been able to.

I can ping the server from workstation, telnet to both port 6336 (Deploy) and 7337 (Inventory) works fine but I still can connect through PDQ console. Any ideas folks ? I don't get any error, it tries to connect when I hit enter and returns back to the same screen to enter server name and port number. I tried both hostname and IP address of the server, still no luck.

Comments

2 comments

Colby Bouma
April 07, 2022 17:10
- If you check the Event Log, there are probably error messages in there.
- Try rebooting both the server and your laptop.
- Did you change the password of the Background Service user too? If so, make sure to update it: https://link.pdq.com/docs-PDQDeploy?backgroundservice.htm
0
Spire Networkteam
April 07, 2022 19:14

Thanks Colby for your prompt response. I have done everything you mentioned but still unable to connect to the server. Apparently the background service is only used when you connecting to local or server mode which is not applicable to my case because I'm connecting to Client mode. I checked with a colleague and it work fine for them.

Question: What credential does PDQ uses to connect to the server and where in my client can I find that ?

Below is the out of the event viewer:

The server disconnected, it may have gone offline or the network dropped.
AppDomain : PDQDeployConsole.exe
CLR Version : 4.0.30319.42000
Current AppDomain : PDQDeployConsole.exe
Database : C:\ProgramData\Admin Arsenal\PDQ Deploy\Database.db
Date : 2022-04-07T18:56:17.8906432Z
Entry : C:\Program Files (x86)\Admin Arsenal\PDQ Deploy\PDQDeployConsole.exe
Error : The server disconnected, it may have gone offline or the network dropped.
Error Type : AdminArsenal.Protocol.ServerDisconnectedException
License Mode : Enterprise Mode
Manufacturer : Dell Inc. (XPS 15 9500)
Memory : 15.8 GB (7.9 GB free)
PID : 1592
Process : PDQDeployConsole
Product : PDQ Deploy
SentryEnabled : True
Service Mode : Client
Version : 19.3.254.0
Windows : Microsoft Windows 10 Pro (10.0.19044)

The server disconnected, it may have gone offline or the network dropped.
AdminArsenal.Protocol.ServerDisconnectedException
------- INNER EXCEPTIONS -------
An existing connection was forcibly closed by the remote host
System.Net.Sockets.SocketException
NativeErrorCode: 10054
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
------- OUTER EXCEPTION -------
The server disconnected, it may have gone offline or the network dropped.
AdminArsenal.Protocol.ServerDisconnectedException
at AdminArsenal.Protocol.ServerConnectionException.ThrowIfDown(Exception ex)
at AdminArsenal.Protocol.ClientConnection..ctor(ProtocolClient client, Binding binding, EndpointAddress endpoint, Action`1 addCustomHeaders)
at AdminArsenal.Protocol.ClientConnectionPool.Checkout(Action`1 addCustomHeaders)
at AdminArsenal.Protocol.ProtocolClient..ctor(String name, String address, String identity, NetworkCredential credentials, Action`1 addCustomHeaders)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at AdminArsenal.Protocol.ProtocolClient..ctor(String name, String address, String identity, NetworkCredential credentials, Action`1 addCustomHeaders)
at AdminArsenal.ProductProtocolClient..ctor(String name, Boolean requireTcp, AALicense newLicense)
at AdminArsenal.PDQDeploy.DeployProtocolClient.Initialize(Boolean requireTcp, AALicense newLicense)
at AdminArsenal.Application.ProductApplication.InitializeProtocolClientInternal()

0