- The mapping on Windows for the local network is not updated
- After installing a recent windows update we are no longer able to connect to our Sage data via our mapped drive or via the network (windows 10 version 1803)
- Windows 10 Update removed the Homegroup feature
- The real server IP address is different on the local mapping
CAUTION: This solution requires advanced knowledge of Windows security and network settings. Sage isn't responsible for any issues that arise from changes to these settings. Ensure you back up all system and application databases necessary for a complete restoration. It's advisable to contact a certified consultant or your system administrator for assistance. Section I: Verify these first
- Confirm that all antivirus and firewalls on the local computer and on the server (or on the computer where the data is located) are disabled. ( For example "on access" scanner from Windows Defender, McAfee, Norton, etc)
- Verify if all workstations are running the same version of Sage 50
- Verify the issue is resolved. If the issue persists, proceed to Section II
.Section II: Get the real IP address
Note: This process is applicable for a local area network (LAN)
- Get IP address from the server: On the server, select Start, Run, type CMD, then press Enter
- Type ipconfig, then press Enter to get server IP address
- From the local computer: Select Start, Run
- Type in \\IPaddress and press Enter
- From the explorer window, open the company on the server
Note: if you can open it without any error messages, you have to fix the mapping on the local computer or create the new drive with the new address
Section III: Creating or Fixing the mapping on the local computer
- On the Desktop, right-click on My computer and choose Map network drive
- Choose the drive letter
- Type \\IP address in the Folder field and press Finish. If you see the old drive listed already, correct the IP address
- Open the company through the mapped drive from Sage 50 Accounting
Section IV: Goto the IP address and make sure it works and then going back to hostname can make it work
- Goto the \\ipaddress and make sure the file opens
- Go back via \\hostname and make sure the file opens
- Verify that you can reboot and it opens via hostname now
DocLink: Error: "A network error occurred while communicating with the Connection Manager"
- Solution ID
- 220924850011122
- Last Modified Date
- Mon Nov 21 17:54:25 UTC 2022
- Views
- 0