Score:-1

Need help configuring a second network adapter on Windows Server 2012 R2

td flag

We have a server running Windows Server 2012 R2. It currently has one network adapter configured with a static IP on our internal network (10.x.x.x). We need to add a second network adapter to provide an edge-facing interface (146.x.x.x) for vendors to upload data via FTP.

What is the correct way to configure the network settings on the second adapter? I've read that you shouldn't have default gateways configured on both network adapters.

Thanks

joeqwerty avatar
cv flag
Why aren't you using your network firewall to forward the FTP traffic to the server?
cn flag
`I've read that you shouldn't have default gateways configured on both network adapters.` That is correct, Windows only uses one default gateway. There is not a reason to configure another gateway on any other adapters. This question is missing basic information such as what is the second network adapter physically connected to, and what is the IP address of the adjacent peer on that physical network segment and on the logical network segment, on your premises, that you intend this server to communicate with.
Tom Yan avatar
in flag
So the goal is that this network adapter assigned with `10.x.x.x` should be used for all other *external* traffics?
user1046450 avatar
td flag
@GregAskew, This is a virtual machine in a datacenter. The second adapter is only to provide an external interface to allow a vendor in through the enterprise firewall. The way I understand it from our network team, it has to be an external IP on the server. They don't do NAT from the outside. All other traffic should go through the internal network adapter. What I wasn't sure of is will the vendor be able to make a connection to the 146.x.x.x interface if there isn't a gateway configured on the external adapter?
user1046450 avatar
td flag
@TomYan, Yes, that's correct. All of the internal traffic should use the 10.x.x.x adapter. We only need to allow one static external IP address in to upload data.
cn flag
@user1046450: if your firewall/network is capable of routing an external packet for that network to your host, there is an adjacent peer for the return path that can be used for the routing table of your host. You are ahead of yourself as it sounds like that network component, which is external to your host, and internal to your organization, hasn't been identified yet. Tell us about that network infrastructure between the firewall and your host.
user1046450 avatar
td flag
@GregAskew, I don't have access to the network infrastructure of our organization. We use a VM hosting service in a datacenter managed by another group. We only have access to our VMs. A firewall rule was created to allow the vendor's static IP through to get to our server.
cn flag
The question as it exists is invalid. There isn't a way to get the packets to your host, period.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.