Problems with DMS relating to changing network settings.

Oct 14, 2018
4
0
10
So everyone, just want to say first, thanks for helping.

Okay, so a client uses a DMS system which runs off one PC (like a server) which the other PC connects to (kind of like a network share method through the DMS apps).

The problem comes when any PC shuts down (always cause by update auto-restart). When it boots up the second PC can't reach the original PCs DMS. After some checking I almost always detect that the issue is network settings changed such as sharing settings and network changed from private to public. Anyone able to tell me how to change this?/fix this?
 

COLGeek

Cybernaut
Moderator
Do you mean DMZ? If so, what make/model router are you using? Keep in mind that a DMZ establishes a separate network, so Windows, when connecting to those "different" networks will act accordingly (the public/private thing you mentioned earlier).
 
Oct 14, 2018
4
0
10
No I mean a Document Management Server but in reality it is just an app using a network share. Everything is connect in a wired network. It is an issue directly related to the PCs not the other network devices. Im going there in an hour what information is needed? Also there are 4 PCs total but only one is using the App to access the other.
 

Ralston18

Titan
Moderator
I would be interested in the IP addresses being used within the network: router and all four PCs.

DHCP or static? If static, are the assigned IP addresses outside the Router's allowed DHCP address range and reserved by the respective PC's MAC?

Also is the DMS a new installation or an existing installation that just starting having problems?

 
generally the client side would be responsable for the reconnection to the server.
does stopping and restarting the client app allow reconnection?



 
Oct 14, 2018
4
0
10
Stopping and starting does not allow connections, the network uses dhcp and not static, does not seem to be outside the address range as normal network connectivity is all working fine, its just connections to local pcs that becomes effected. Like I said it all works fine when I change the settings back to a private network, I just don't understand why it gets changed when it auto restarts from updates. I am on call and am not around to change the settings back for them when this happens so I need a way to stop it from happening.
 
so a firewall rule blocks the connection when the system is restarted as a public network? (higher restrctions)
the “make this PC discoverable.” set to on sets the system private (less restrictions)

see this for when the option is not in the ui and see the last example where they used a command prompt and .exe to set the setting. Maybe you can set it by script and put it in the task manager to run so it gets run on startup. it does not prevent the problem but will apply a crude fix after a update.
better (longer) version
https://www.tenforums.com/tutorials/6815-set-network-location-private-public-windows-10-a.html

here is a better method: see the powershell script:
https://superuser.com/questions/1160421/how-do-i-force-windows-10-to-see-a-network-as-private