Package Library - Problem importing packages
PDQ 12 (Release 1 Build 4)
Trying to import new packages from the package library.
I see it downloading, but errors out with "The user name or password is incorrect".
No changes other than doing some updates to Server 2012 R2 OS yesterday. Couple of weeks ago I was able to import some packages without issue.
I've retyped the password, restarted the background service, rebooted, used the same account to access the file repository share....
I can deploy existing packages without issue with the same account.
Help...
Comments
Okay.....
So just for the hell of it, I went into preferences and looked at the repository.
Original setting > \\ip of file server\Deploy\Admin Arsenal\PDQ Deploy\Repository
Used the little browse button and pointed to same area and it changed it to > \\name of file server\Deploy\Admin Arsenal\PDQ Deploy\Repository
Working now, but anyone tell me why I can now import packages?
Seems to me that you've found a bug. What happens when you change the host name back to the IP?
I'll try switching to see if the problem occurs again and report back.
Results.....
Switched back to \\ip of file server >>> downloads but errors out "The username or password is incorrect".
Switched to \\name of file server >> working properly
Does the name/dns point to the same IP? Can you dio a nslookup/ping on the name? (just to be sure)
Legend with example names - hope it doesn't confuse you and hope I got this information right.....
So, file server "ZEUS" sits on Network B with a static IP but we do not control Network B. Zeus has DNS settings pointing back to our DC/DNS server called ALPHA (alpha.domA.com)
-------------------------------------------------
PINGING file server named ZEUS using name
ping -a zeus
pinging zeus.domA.com [180.205.115.110] ....
reply from 180.205.115.110 ..... etc
PING WORKS
-------------------------------------------------
PINGING file server named ZEUS using IP
ping -a 180.205.115.110
pinging zeus.domB.com [180.205.115.110] ....
reply from 180.205.115.110 .....etc
PING WORKS
-------------------------------------------------
NSLOOKUP file server named ZEUS using name
nslookup zeus
Server: alpha.domA.com
Address : 180.205.75.50
Name : zeus.domA.com
Address : 180.205.115.110
-------------------------------------------------
NSLOOKUP file server named ZEUS using IP
nslookup 180.205.115.110
Server: alpha.domA.com
Address : 180.205.75.50
Name : zeus.domB.com
Address : 180.205.115.110
OK, so far I understand that the name points to the correct IP. So there should be no issue here regarding this. One thing I can imagine is that there is a firewall which intercepts the communication and blocks it if doesnt match the filters..
BTW I am not sure what encryption is used by PDQ deploy/inventory to communicate between the client/server, but. why dont you connect the networks over a VPN? Its not a good practive to open SAMBA to the Internet as seen recently with the WannaCry malware.
Thanks SelfMan for the help.
Network A and B are both internal. Would I just google up some documentation "networks over a VPN" to look at your suggestion?
I thought that both IP's are external. If they are internal, ignore my note.
In you case it should not matter if you are using DNS/name or IP address to connect to the computer. According your information, the machine is reachable both ways. You might try ipconfig /flushdns just to be sure, but this issue really looks like a bug.
Though there might be one more possible thing. You already have a connection to that server with diffrerent credentials. Like a mapped drive. If possible, logon to the remote server via RDP and check existing sessions in computer management.