B
BrokenConfig
Hello. I have a strange issue I am hoping someone can assist me with.
I use a Shop management software called E2. Its running on an edition of Server 2016 that is configured in not the best practice. It has AD installed, It is a DC, It has DNS running on it, and it has IIS and SQL running on it. I know its not best practice, but everything was working just fine for a long time until a few days ago when some apps stated reporting errors and failing to function.
I am by no means an expert in this stuff but I believe it to be an issue with DNS. The only reason I have for this is because the issues I am having seem to come and go. When things work fine, I seem to be able to ping the server locally and return its ipv4 address. When things seem to stop working is when I ping the server locally and it returns ::1 and not an ipv4 address.
The apps need a signed and trusted ssl cert to function. I believe the certs I have are fine because this problems seems to come and go now for the past few days.
I can ping with "ping -4" and it does give me the correct address, but it seems the default goes to ::1. Now I just recently did some windows updates and this started to happen. Maybe something got jazzed?
I really dont even know where to begin to look other than dns, but even there I dont really have the knowledge to troubleshoot.
Anyone know what might be causing these issues?
Thanks.
Continue reading...
I use a Shop management software called E2. Its running on an edition of Server 2016 that is configured in not the best practice. It has AD installed, It is a DC, It has DNS running on it, and it has IIS and SQL running on it. I know its not best practice, but everything was working just fine for a long time until a few days ago when some apps stated reporting errors and failing to function.
I am by no means an expert in this stuff but I believe it to be an issue with DNS. The only reason I have for this is because the issues I am having seem to come and go. When things work fine, I seem to be able to ping the server locally and return its ipv4 address. When things seem to stop working is when I ping the server locally and it returns ::1 and not an ipv4 address.
The apps need a signed and trusted ssl cert to function. I believe the certs I have are fine because this problems seems to come and go now for the past few days.
I can ping with "ping -4" and it does give me the correct address, but it seems the default goes to ::1. Now I just recently did some windows updates and this started to happen. Maybe something got jazzed?
I really dont even know where to begin to look other than dns, but even there I dont really have the knowledge to troubleshoot.
Anyone know what might be causing these issues?
Thanks.
Continue reading...