Like many workgroup users, I've had all sorts of problems since 1803.
For starters, I downloaded netbscanner.
https://www.nirsoft.net/utils/netbios_scanner.html It's a small utility program that gathers info about the current network and workstation configurations.
I ran it on my office workstation. It provides all the IP addresses for every workstation on the network, AND what workstation is the "master browser".
The server must be the master browser (YES). To force this setting across your network, you have to do the following.
Set Master browser Fix -- Run RegEdit (right click start menu, select Run (command line) and run regedit.
go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
MaintainServerList REG_SZ Set to "False" on every machine but the workgroup server.
On Server, set IsDomainMaster to "YES", MaintainServerList to "YES"
If left as Auto on the Server, it would probably work out. Best as "YES"
Also, every workstation must be part of the same workgroup, or it may be assigned the master browser for that workgroup. Control Panel/System provides access to changing the workgroup name. A restart is required after changing workgroups.
Configure every computer so it's IP address in manually set.
To set the IP address, right click on the network icon in the task bar and select "Open Network and Internet Settings"
Then select "Change Adapter Properties", click on the network in the screen that pops up,
then Properties, then Internet protocol version 4.
When setting IP addresses use the IP addresses that netscanner comes up with for each workstation and server.
Don't use autoconfig -- click "Use the following IP address and enter the IP address from netbscanner for that computer.
IP 192.169.0.1xx. each computer has it's own IP. FYI, this is for wired networks. Wifi might be different.
Mask 255.255.255.0
Gateway 192.168.0.1
DNS 192.168.0.1
After configuring a workstation or server close out of that stuff.
Open the file manager and Right click on the PC icon. Select "Manage"
Select "Services and Applications" then services
Scroll down to FunctionalDiscovery (two services) and set them to 'Auto delayed start'
Repeat with DNS Client, SSDP Discovery, and UPnP device host.
Then click out and restart the computers. I have found that running netbscanner on the server when all the workstations are started seems to speed this discovery process up.
Also, apparently it can take up to twenty minutes for any computer, including the server, to properly recognize other computers on the network. During this waiting period, you might try to open OpenDental and it won't connect to the server. You can close out and start it up again, and eventually it will connect. It may help to just run around and turn on all the workstations and log in. Then run NetBscanner on the server. Then start up OpenDental, but don't log in. Just proceed to the next workstation. Then come back to the first and log in... Most of the time it logs right in.
At least that was how it worked the last couple days... Fine print -- if it doesn't work, the router probably needs to be turned off for 10 seconds and turned back on. This doesn't seem to effect the existing connections with my router and system, so far. But it did allow workstations that were having trouble connecting to connect to the server.
Also, one other thing that sometimes pops up is some workstations that don't connect may require disconnecting and reconnecting the mapped drives on the workstations. Go to PC and right click and disconnect the mapped drives. Then go open the Server. And map the drives. Each drive must have the same mapped letter for Opendental to connect to it across the network.
-------------
Apparently, MS has rationalized that workgroups is too old and too open for attack. So it's abandoning the system... Presumably, it expects every small business that has been running workgroups will have to buy a server, get an IT manager, etc, etc... Or, this is a way for MS to make a lot more money... Take your pick. There may be a domain server in everyone's future...
Also, I saved all these in the Opendental wiki that is in the tools menu in case I need to refer to it later.
Some references
https://pattersonsupport.custhelp.com/a ... er-browser
https://social.technet.microsoft.com/Fo ... networking
