R
RonCampbell8
OK, here goes. I Have never posted a question to this, or any, forum regarding windows before, but I'm stumped. I'll try and be as clear as possible.
The scenario: A newly installed windows Server 2019 standard running a Client/Server software called Dentrix. The server is AD/DC/DHCP/DNS.
The secondary adapter is disabled. IPV6 is disabled on the working NIC.
IPV6 is disabled on all client workstations as well.
The client software relies on two parts. an SQL client that will cause all kinds of errors if it looses connection to the server for even a brief second, and access to a shared folder on the server.
The clients are configured with only one DNS, the Server's IP address, I can Ping the server, by name or IP, for hours on end with no dropped packets. DNS queries run on the server all pass. I can browse to the server from any workstation by name or IP without error. I can open the shared folder without error, again from any workstation.
Permissions on the share are: Domain Users\Domain Admins\Everyone - Full
The share is on the root of "C" and inheritance has been disabled, made sure to pass permissions to all sub folders
Guest and Anonymous users have been removed from share
Now the problem:
The client software is comprised of multiple modules, each serves a different purpose, and each one can be launched from within any of the other modules. Since I put in the new Server 2019 I've encountered a problem I can not resolve, and support from the software provider say they have no ideas.
The problem in a nutshell is this, when launching a module from within another module, sometimes, and not all the time, it will tell me it can't access the server share, while showing the absolute correct path to the share. Attempts to browse to and open the share at this point are successful. In normal scenarios this error would indicate a disconnect from the server in some way shape or form. But in this scenario, the client pc is not being disconnected, and hitting "close' on the error still allows the launched module to start. For clarification, this problem occurs maybe a dozen random times a day, out of 100's of launches. Its not tied to a particular workstation. I can not duplicate the error on purpose. I have tried a few things, will wait and see if anyone responds.
Thank you for your time
Continue reading...
The scenario: A newly installed windows Server 2019 standard running a Client/Server software called Dentrix. The server is AD/DC/DHCP/DNS.
The secondary adapter is disabled. IPV6 is disabled on the working NIC.
IPV6 is disabled on all client workstations as well.
The client software relies on two parts. an SQL client that will cause all kinds of errors if it looses connection to the server for even a brief second, and access to a shared folder on the server.
The clients are configured with only one DNS, the Server's IP address, I can Ping the server, by name or IP, for hours on end with no dropped packets. DNS queries run on the server all pass. I can browse to the server from any workstation by name or IP without error. I can open the shared folder without error, again from any workstation.
Permissions on the share are: Domain Users\Domain Admins\Everyone - Full
The share is on the root of "C" and inheritance has been disabled, made sure to pass permissions to all sub folders
Guest and Anonymous users have been removed from share
Now the problem:
The client software is comprised of multiple modules, each serves a different purpose, and each one can be launched from within any of the other modules. Since I put in the new Server 2019 I've encountered a problem I can not resolve, and support from the software provider say they have no ideas.
The problem in a nutshell is this, when launching a module from within another module, sometimes, and not all the time, it will tell me it can't access the server share, while showing the absolute correct path to the share. Attempts to browse to and open the share at this point are successful. In normal scenarios this error would indicate a disconnect from the server in some way shape or form. But in this scenario, the client pc is not being disconnected, and hitting "close' on the error still allows the launched module to start. For clarification, this problem occurs maybe a dozen random times a day, out of 100's of launches. Its not tied to a particular workstation. I can not duplicate the error on purpose. I have tried a few things, will wait and see if anyone responds.
Thank you for your time
Continue reading...