Windows Server 2016 – Nginx: Are all $ remote_addr always our internal gateway?

I have had Nginx (1.15.8) running for quite some time as a reverse proxy that serves some pages hosted within our organization from separate servers. Today I was trying to add some white list features and I noticed that it didn't work as expected. After checking the records, all traffic shows the $remote_addr as our internal portal (

Here is my nginx.conf, excluding all production sites. The server entry you see is my test for the whitelists.

worker_processes    1;

error_log           logs/error.log;
error_log           logs/error.log  warn;

events {
    worker_connections  1024;

http {
    log_format          main  '($time_iso8601) $remote_addr - $server_name:$server_port > $proxy_host:$proxy_port ($request - $status)';
    access_log          logs/access.log  main;
    server_names_hash_bucket_size  64;
    include             mime.types;
    default_type        application/octet-stream;
    client_max_body_size 2000M;
    client_header_timeout 120s;         
    client_body_timeout 120s;   

    sendfile            on;
    keepalive_timeout   65;

    server {
        listen      80;
        location / {
            #allow; #internal
            deny all;
            root c:/webroot/;
            index index.html;

With the previous configuration, nobody can access the site (403). If I recommend the allow command, EVERYONE can access the site. I am testing this from an AWS server, as well as from a remote user's desktop. If I look at the records, the two requests (internal and external) are identical.

Here are the internal and external records with the allow Commented:

(2019-09-17T12:22:01-07:00) - > -:- (GET / HTTP/1.1 - 403)
(2019-09-17T12:22:02-07:00) - > -:- (GET /favicon.ico HTTP/1.1 - 403)
(2019-09-17T12:22:10-07:00) - > -:- (GET / HTTP/1.1 - 403)
(2019-09-17T12:22:10-07:00) - > -:- (GET /favicon.ico HTTP/1.1 - 403)

And here are the records with the allow NOT commented:

(2019-09-17T12:29:34-07:00) - > -:- (GET / HTTP/1.1 - 200)
(2019-09-17T12:29:34-07:00) - > -:- (GET /favicon.ico HTTP/1.1 - 404)
(2019-09-17T12:29:38-07:00) - > -:- (GET / HTTP/1.1 - 200)
(2019-09-17T12:29:38-07:00) - > -:- (GET /favicon.ico HTTP/1.1 - 404)

Why is this happening? Is this a network configuration problem?

Database migration failed from SQL Server 2012 to 2016

After restoring the SQL Server 2012 backup to 2016 at 100% completion, it has failed and the database has been recovered pending recovery.

Able to do the restoration with the same backup of SQL Server 2012 to 2014 is successful and then tried to make 2104 to 2016 but the same error.

Error: 928, Severity: 20, State: 1.
During upgrade, database raised exception 211, severity 23, state 109, address 00007FFA50AB1225. Use the exception number to determine the cause.
Error: 211, Severity: 23, State: 109.
Corruption in database ID 7, object ID 3 possibly due to schema or catalog inconsistency.

Have performed an integrity check and a catalog check at the source.
I have also tried to make the repair allow data loss after entering emergency mode.
I tried to separate and attach with a single file. I even tried the reconstruction log.
I got the same resources as the source server.

Windows application – Windows 10 Enterprise 2016 LTSB X64 en-ESD ESP 2019 | NulledTeam UnderGround

OS: x64 | Language: English | Size: 3.21 GB


* File: W10.LTSBX64.ENU.SEP2019.iso
* Size: 3.21 GB
* Format: Boot ISO

* SOURCE: dvd-9059483

* CRC32: 91dc3255
* MD5: 6019a38fccb1799f3d4285aae692e855
* SHA-1: 1c5a59a477e7e66ddd17b61fa9a456f4ec2399b9


* Dynamic update (s):
* KB4013419
* KB4039556
* Service stack update:
* KB4512574
* Cumulative update:
* KB4516044
* NET Framework 4.8:
* KB4486129
* Cumulative update for
* .NET Framework 4.8:
* KB4514354
* Flash Player security update:
* KB4516115

SetupComplete / Post-install:

* .NET Framework 3.5
* Defender Updates



* Windows 10 Enterprise 2016 LTSB – STD
* Windows 10 Enterprise 2016 LTSB – DLA

* STD = Standard installation: for those with their own license key
* DLA = Digital license activation (HWID)


* Ready for UEFI
* (Use the attached Rufus USB tool to make UEFI bootable).
* Diagnostic and recovery toolset 10.0 (Microsoft DaRT)
* install.wim compressed to recovery format (install.esd)


* Create bootable USB (highly recommended) with Rufus,
* (attached) or burn to DVD-R at low speed.


* WindowsAddict, author of the Windows activation script

* I hope you enjoy this release!


Download from UploadGig

Download from RapidgatorDownload from Nitroflare

How to save the value of a Yes / No checkbox through Sharepoint 2016 REST API onPrem?

How is marked / unmarked for sharepoint 2016 in-prem saved through the REST API? I have a couple of input text boxes to save text, but I can't save yes / no for cbAttending, I can't seem to get the value when it's checked. We appreciate any pointer.

What version of Node.js can I use if I am stuck in SPFx v.1.1.0 (SP 2016)?

I am stuck in SharePoint 2016 at the moment, and I know that means I am stuck using SPFx v.1.1.0.

However, I am not sure what that means in terms of which version of Node.js to use.

I have some conference notes that claim to use LTS Node v.8, but my notes are not clear if that means it should be exactly v.8, or at a minimum v.8.

I ask because I have a non-SharePoint project that requires Node LTS v.10, and I'm trying to find out if I can upgrade to Node v.10, or if I will have to install NVM for I can change between 8 and 10 depending on what I am working.

Will SPFx v.1.1.0 work with Node LTS v.10?

spfx webparts – Migration of the SP 2010 site collection to SP 2013 On-Prem to SP 2016 On-Prem to SP 2019 On-Prem | Go from the classic pages to the modern ones

I am new to an organization that is moving from SP 2010 to SP 2013 to SP 2016 to SP 2019. All of these are local versions. The site collection has almost 3,500 sites. There are many customizations: web parts that include more content editors that point to jquery and html files.

For testing purposes, a team updated from SP 2010 to SP 2013. Nothing broke, yet. My concern is when they migrate to SP 2016, and modern pages are activated – the content editor web part does not exist in modern pages – SPFx rules. What happens on those pages where content editor web elements have been used to point to files? Is there a document for best practices?

sql server: MAXDOP configuration for SQLserver 2016 and higher

I was reviewing the MS documentation record: configuring MAXDOP starting SQL2016 as that automatic soft NUMA enabled by default and confusing me on how to make changes to the current versions of SQ2014 and SQL2012:

MSDN Link– server-2017 # Guidelines

Current configuration of SQL2012 / 2014:

Logically Processors =80
Numa Node=4
Physical RAM= 512GB

So what is the change after moving them to SQL2016 and higher? MAXDOP of the current configuration can not stand and need to tune? If so, what does MS propose?

Please share your experiences when configuring this.

Best antivirus 2016 |


If you really want first-line protection, go with Norton Security 2016 (paid) and Malwarebytes (Premium). That is what I use.

If you want a still good and free protection, go to Avast Antivirus (free) and Malwarebytes (free edition).

permissions – SP 2016 in local error: Sorry, we are having trouble reaching the server

while I share permission and in all types of people who select I get this error "Sorry, we are having trouble getting to the server"
enter the description of the image here
by clicking Shared with I receive an error "unexpected server response data"
enter the description of the image here

I tried the following,

  • resetting IIS,
  • restarted the server
  • different usernames
  • the memory space is enough

Please help me to solve this error.

The properties of the mssql 2016 server mix replication article continue to change after a while

We have in our configuration the fusion replication between two servers that run the same versions of the MSSQL server. We have some fields of geography data type and fix it by converting filestream to nvarchar (max) for all articles. And it works for a few days (I don't know how many exactly) and again we have the same problem again. Does anyone here know what is the cause of that? Note that we are tracking DDL changes throughout the database and that we do not see any new columns of that type, so there are no changes in the structure of the database (of which we are aware).

Any help with this will be greatly appreciated, thanks.