Share via

Trying to fix a NIC configuration

Anonymous
2023-08-22T16:56:03+00:00

New to this forum, but not Microsoft

I have a domain controller that I recently upgraded from 2012r2 to 2019. Can't go to 2022 on this box as the processor generation is too far back.

System is an i3, running 2 NICs. One for external traffic, the other for LAN.

Turns out that the company who made the NIC didn't bother updating their INF to allow for Windows 10/Server 2019, so either had to modify the INF myself (time waster), or get a new NIC. I opted for a new 2.5Gb NIC.

The problem is that I'm having various issues.

Here's the NIC setup...

IP = 192.168.16.2

Gateway = 192.168.16.1

DNS = 192.168.16.2

Alternate DNS = 8.8.4.4 (Google DNS)

DHCP appears to be working, but while everything seems to be getting it's reserved address, mapped drives work, sometimes, but not always. Sometimes though they seem to be getting their IP addresses from the firewall on the incoming side (192.168.0.x). Teaming is not set up. I have NAT turned on (yes, I know, not good practice, but was working on 2003, 2008 and 2012.

No internet access from anything on the LAN through the server, but works directly connected to the firewall.

Nothing was done to the settings of the server itself. Verified NAT was still working, DHCP and DNS as well, yet there's these issues.

Has anyone run across this issue before? I can't seem to find any related issues using Google.

Andy

Windows for business | Windows Server | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-08-24T03:04:49+00:00

    Hello,

    Are the devices on the LAN able to communicate with each other and ping the server on the local network successfully?

    Are there any other roles or services on the DC?

    Use tools like "tracert" from a LAN device to trace the path of network traffic towards an external IP address. This can help identify where the traffic might be getting stuck.

    Can you check the DHCP settings on both the domain controller (server) and the firewall? Ensure that there are no conflicting DHCP servers active on the network, and that the DHCP configuration is consistent across both devices.

    Thanks,

    Karlie

    0 comments