Email and AI : Version 12.52.31

Email Issues:

We have received some calls where ASW’s email system was no longer working with gmail accounts.  We do not use gmail, so we had to do some research.  Google and Microsoft are adopting a new standard to make emails more secure.  It is using oAuth, a protocol that is emerging.  We are working to find the simplest way to have you implement these changes, but both companies have made it very complex, and there are lot of “hoops to jump through”.  The bottom line is that you will end up having to do some complex work on your end to get the proper authorization codes from these companies, and to set your accounts to allow you to send emails through their services.

 

Quickbooks:

Some people are using Quickbooks for their accounting and may have implemented the interface that writes your invoice and customer data directly to QB from ASW when you close a workorder.  This was all included to work with the desktop version of QB.  Now, Intuit is moving to their cloud based system only and fully phasing out the desktop versions.  ( Of course you don’t have to upgrade away from that if you are using an earlier version ).  We decided to look at being able to output directly to the cloud version, and it really should be a simple process.  However, so far we are finding a lot of red tape, new fees, etc. that complicate the process.  We’ll keep working on this.

 

AI:

There is a lot of talk about AI, and MANY companies are providing their own products.  When you use them on their webpage, you can do some things for free, but when interfacing with them in a program, they have fee based models.  Even so, there are two implementations of AI in ASW, and we are working on a rather fascinating option to also implement on your local data.  However, please remember that AI is in it’s infancy, and you should NEVER count on it’s accuracy.  

CoPilot:  ( F3 key ):  This is Microsoft’s initial AI model built into Windows 11.  You can enter a question, it will search for answers and display what it finds.  It may be fairly limited.

Gemini: ( F4 key ):  This is newly implemented in this version, but it’s a bit more complex.  You will need to go to Google’s website and get an ID key for Gemini.  Copy it, then in ASW, under Tools -> Setup you will see AI Key.  Click on that and paste in your gemini key.  Exit ASW and when you come back in, the F4 key will give you the prompt for a question.  Be specific if you want realistic answers.

All AI models are designed for the companies to make profits so they will all be asking for money.  Also, again remember they are in their infancy, and though they may appear to be impressive, they have a whole lot to learn, and they don’t always hit the right target.

 

We’ll keep you updated as these developments take place.

CRITICAL: Networking Issues

UPDATED:  New information added 5/11/2025 @ 4:12 PM PDT

Over the past two weeks some of our clients are reporting that one of their computers can no longer bring up the program.  They have received an error that says either “File cannot be Opened”, or “Server cannot be reached”.  Clearly this is VERY frustrating !

This is not caused by anything within Auto Shop Writer ( MLS 12 ), and we cannot make any update to the program to resolve it.  This is strictly a Windows networking issue.

In November, 2024, Microsoft announced new networking protocols to increase security, and the development of software controlled networking.  I have talked to many IT techs who see the problems at many of their ( non-MasterLink ) clients who all depend on the built in networking found in Windows Pro.

In most cases we have found workarounds that resolve the problems ( at least for now ), but there has been no clear documentation or direction from Microsoft on how to setup the networking for basic interactive data sharing under the new methodology.

Shops are seeing this take place overnight.  One day everything works fine, the next it does not.  Because we have not yet encountered the issue here at our location, we really have no way to aggressively test it, and find a solution.  

We are actively engaged with other professionals to identify the root cause, and fixes, for this problem.  However, it is basically a networking issue that involves the Windows operating system.  If you encounter the problem, we’re happy to talk with your IT person to explain our system ( which is using basic Windows Peer to Peer networking ).  

One does not need to test this with ASW.  On the workstation that is not connecting, go into Windows Explorer ( the little manilla folder on the task bar at the bottom of your screen ), then in the left column, scroll down to Network.  Click on the arrow to the left that would show the visible computers.  Can you see the server ?  Can you click on it’s arrow to show the shared folders ?  If so, can you see, and click on, the MLS12s folder and see the Data ?  If not, then something in your system is blocking it.

This will all be related to “permissions”, set and controlled by Windows.  Not all machines will update at the same time, and thus it may be a problem on only one computer, and then another.

We will continue to research the problem, and provide further guidance as we get answers.  

 

Using AI, here is a list of suggestions you can share with your IT Professional.  This is 100% due to changes in the networking protocols in Windows and has arisen due to recent changes including in the current updates:  

If Windows 11 devices can no longer see shared folders on another computer after a recent Microsoft update, try these troubleshooting steps:

 

### **1. Restart the Devices**

– Restart both the computer sharing the folder and the one trying to access it.

 

### **2. Check Network Discovery and File Sharing**

– Open **Control Panel** > **Network and Sharing Center** > **Change advanced sharing settings**.

– Ensure **Network Discovery** and **File and Printer Sharing** are turned ON.

– If using a Private network, check the settings under the “Private” section.

 

### **3. Ensure SMB1 is Enabled (If Necessary)**

Some updates may disable **SMB 1.0**, which older systems or devices require.

– Open **Control Panel** > **Programs and Features** > **Turn Windows features on or off**.

– Scroll down and check **SMB 1.0/CIFS File Sharing Support**.

– Click **OK**, then restart your PC.

 

### **4. Verify Network Profile is Set to Private**

– Go to **Settings** > **Network & Internet**.

– Under **Wi-Fi** or **Ethernet**, check if your network is set to **Private** (not Public).

 

### **5. Re-enable Guest Access in Group Policy**

Some updates disable guest access to network shares:

– Press `Win + R`, type **gpedit.msc**, and press **Enter**.

– Navigate to **Computer Configuration > Administrative Templates > Network > Lanman Workstation**.

– Double-click **Enable insecure guest logons**, set it to **Enabled**, and click **OK**.

– Restart the computer.

 

### **6. Reset Network Settings**

– Open **Command Prompt (Admin)** and run the following:

  “`

  netsh int ip reset

  netsh winsock reset

  ipconfig /flushdns

  “`

– Restart the computer.

 

### **7. Check Windows Credentials**

– Open **Control Panel** > **Credential Manager**.

– Go to **Windows Credentials** and remove any incorrect saved credentials related to the shared computer.

– Reconnect to the shared folder and re-enter credentials if needed.

 

### **8. Check Windows Firewall and Antivirus**

– Temporarily disable the firewall:  

  Open **Windows Security** > **Firewall & network protection** > **Turn off firewall**.

– If the shared folders become accessible, add an exception for **File and Printer Sharing**.

 

### **9. Verify Sharing Permissions**

– Right-click the shared folder > **Properties** > **Sharing** tab.

– Click **Advanced Sharing** and ensure **Share this folder** is checked.

– Click **Permissions**, ensure the correct users have **Read/Write** access.

 

### **10. Try Accessing via IP Address**

– Press `Win + R`, type `\\[IP-Address]\SharedFolder`, and press **Enter**.

– Example: `\\192.168.1.10\SharedDocs`.

 

If the issue persists, it might be due to a Microsoft update bug. Checking **Windows Update history** and rolling back the latest update could help.