My guess is the database upgrade from 1.2.0 didn’t go as smoothly as I had thought. I probably should have checked some of the tables just to see. Setting the pConfig to “Local” in the database filled in “TCP/IP” in the Printer Type column when clicking on List all printers.

I just fixed my “second” printer issue. There was an & sign in the path to the inf file and the fog gui was showing & for some reason. I removed that from the gui and removed the & from the server path and the printer installed correctly. Strange how there was no error in the fog log but I’m guessing that’s not something you can query?

@Sebastian-Roth I was actually able to compile that dll myself. Looks like it’s throwing on the GetComputerDomain() line in both cases. Trying to join the domain and after I manually join the domain. So I don’t think that’s the problem. It’s failing on the NetJoinDomain() function. I think I need to print out the variables to see if they’re the same for a good image and a bad one.

@Sebastian-Roth All the net use and net session commands return “There are no entries in the list”. So there’s nothing to delete. I’m connected using RDP on all these machines (good and bad images) so I can’t stop the lanmanworkstation service. If I run net use or net session on a good image I get the same message. I think network packets and debug logging on the samba server makes sense to try next. I’ll have to look into that.

@Sebastian-Roth Thanks for that info. Took me a while to realize where the button was. Not like it’s not big enough.

Here’s what I’ve found so far. On a good image or bad image whether I’m joined to the domain or not IsJoindToDomain() always throws on the using (var domain = Domain.GetComputerDomain()) line. Not sure what the purpose of that is but I’m running an NT4 domain, not an AD domain so it could be for that. Because this function fails the client is always calling NetJoinDomain() on every loop.

On a good image that’s disconnected from the domain the first call to DomainWrapper() always fails. I think it’s because my ADOU is always empty. Again something with an NT4 domain? The return value is 50 so then DomainWrapper() is called again with false set. And then it connects.

On a bad image that’s disconnected from the domain the first call to DomainWrapper() fails with a 1219 and then doesn’t try again. I tried adding 1219 to the switch to call again with false set but it fails with a 1219 as well. Not sure what to try next.

Thanks

@Sebastian-Roth I decided to remove the client and re-install it on this machine and now I get a different error in the fog log. It keeps looping on this.

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 13/09/2019 3:06 PM Client-Info Version: 0.11.16
 13/09/2019 3:06 PM Client-Info OS:      Windows
 13/09/2019 3:06 PM Middleware::Authentication Waiting for authentication timeout to pass
 13/09/2019 3:08 PM Middleware::Communication Download: http://xxx.xxx.xxx.xxx/fog/management/other/ssl/srvpublic.crt
 13/09/2019 3:08 PM Data::RSA FOG Server CA cert found
 13/09/2019 3:08 PM Middleware::Authentication Cert OK
 13/09/2019 3:08 PM Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
 13/09/2019 3:08 PM Middleware::Authentication ERROR: Could not get security token
 13/09/2019 3:08 PM Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'.
 13/09/2019 3:08 PM Middleware::Communication POST URL: http://xxx.xxx.xxx.xxx/fog/management/index.php?sub=requestClientInfo&authorize&newService
 13/09/2019 3:08 PM Middleware::Response Invalid security token

I’m wondering if maybe this is the real problem. Do you know what this means?

Thanks

@Sebastian-Roth I was actually able to compile that dll myself. Looks like it’s throwing on the GetComputerDomain() line in both cases. Trying to join the domain and after I manually join the domain. So I don’t think that’s the problem. It’s failing on the NetJoinDomain() function. I think I need to print out the variables to see if they’re the same for a good image and a bad one.

@Sebastian-Roth Would it be possible to get a dll with logging showing which of the following is failing? And maybe the return value of the ones that aren’t?

                using (var domain = Domain.GetComputerDomain())
                {
                    var currentIP = Dns.GetHostAddresses(domain.Name);
                    var targetIP = Dns.GetHostAddresses(idealDomain);

                    return (currentIP.Intersect(targetIP).Any());
                }

@Sebastian-Roth Do you know what function produces that log message? Just wondering if I can do some googling on the error message.

@Sebastian-Roth I tried re-installing last night but ran out of time. I had an old version of Windows 7 that needed a bunch of updates before the fog client would install and run. I’ll have to try again another time.

I did try your debug Module.dll from the other thread and got the following in the log.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 12/09/2019 4:14 PM Client-Info Client Version: 0.11.16
 12/09/2019 4:14 PM Client-Info Client OS:      Windows
 12/09/2019 4:14 PM Client-Info Server Version: 1.5.6
 12/09/2019 4:14 PM Middleware::Response Success
 12/09/2019 4:14 PM HostnameChanger Checking Hostname
 12/09/2019 4:14 PM HostnameChanger Hostname is correct
 12/09/2019 4:14 PM HostnameChanger RenameComputer returned properly, trying register/join next.
 12/09/2019 4:14 PM HostnameChanger Checking AD params before join.
 12/09/2019 4:14 PM HostnameChanger Attempting to join domain
 12/09/2019 4:14 PM HostnameChanger Unable to resolve domain DNS name: The local computer is not joined to a domain or the domain cannot be contacted.
 12/09/2019 4:14 PM HostnameChanger Unknown Return Code:  1219
------------------------------------------------------------------------------

Does that extra log message help at all? When I ran out if time I just re-imaged back to the image that has the join problem.

Thanks

@Sebastian-Roth I just tried disconnecting from the domain on a computer with a different image and the fog client reconnected correctly. Here’s the log.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 10/09/2019 4:46 AM Client-Info Client Version: 0.11.16
 10/09/2019 4:46 AM Client-Info Client OS:      Windows
 10/09/2019 4:46 AM Client-Info Server Version: 1.5.6
 10/09/2019 4:46 AM Middleware::Response Success
 10/09/2019 4:46 AM HostnameChanger Checking Hostname
 10/09/2019 4:46 AM HostnameChanger Hostname is correct
 10/09/2019 4:46 AM HostnameChanger Attempting to join domain
 10/09/2019 4:46 AM HostnameChanger Success, code =  0
 10/09/2019 4:46 AM Power Creating shutdown command in 60 seconds
 10/09/2019 4:46 AM Bus Emmiting message on channel: Power
------------------------------------------------------------------------------

And then this.

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 10/09/2019 4:50 AM Client-Info Client Version: 0.11.16
 10/09/2019 4:50 AM Client-Info Client OS:      Windows
 10/09/2019 4:50 AM Client-Info Server Version: 1.5.6
 10/09/2019 4:50 AM Middleware::Response Success
 10/09/2019 4:50 AM HostnameChanger Checking Hostname
 10/09/2019 4:50 AM HostnameChanger Hostname is correct
 10/09/2019 4:50 AM HostnameChanger Attempting to join domain
 10/09/2019 4:51 AM HostnameChanger The machine is already joined to the domain, code =  2691
------------------------------------------------------------------------------

I really think it’s just something specific with this image but I can’t seem to figure out what’s different. It doesn’t make sense that I can join the domain manually either. I’m almost at the point of just re-installing Windows 7 from scratch to see if that cleans it up.

@Sebastian-Roth I just tried your suggestion. The net session command says There are no entries in the list. Starting the FOG service again produces the same error message as my first post. Strange how there’s no sessions. I figured there’s be something. If I manually join the domain and reboot I then get the following in the fog log.

 09/09/2019 7:36 PM HostnameChanger Checking Hostname
 09/09/2019 7:36 PM HostnameChanger Hostname is correct
 09/09/2019 7:36 PM HostnameChanger Attempting to join domain
 09/09/2019 7:36 PM HostnameChanger The machine is already joined to the domain, code =  2691

@Sebastian-Roth I’m still running an NT4 domain not an AD domain so I’m pretty sure I don’t have any GPO’s? I’m not sure where I’d look for any other tools or scripts on my server. Or are you thinking in the Windows 7 images itself? I’ve been putting off figuring out how to migrate a Samba NT4 domain to a Samba AD domain although I know I need to do that soon.

Thanks