Windows Server 2012 Unidentified Network

Hi all,

There is a similar topic already solver but since the solution doesn't work for me, I create a new thread. I have a similar set up: WinSrv2012 (VM), two NIC cards (one to with access to LAN one with access to internet). But the LAN network still unidentified though as advised, I put the DNS suffix to the LAN connection and IPv6 is disabled. My configuration is:

Internet
Address: 10.4.101.23/24
Def.GW: 10.4.101.1

LAN
Address: 10.4.100.23/24
No default gateway but a permanent route for 10.0.0.0/8 to 10.4.100.1 which is the gateway of this network
DNS Suffix added to advanced properties

Not sure if it's the best practice. But like this the network doesn't get identified.

If I put a gateway to the LAN connection, (despite the error message for dual gateway) my two network are identified to the same network...

Thanks ahead for the help.
Kind regards
Yohan CourbeIT ManagerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Well, for starters, your static route make the LAN NIC useless, as all traffic, even local, would go through the gateway thus go through the "internet" NIC. That includes the various network discovery protocols. You have a broken topology.
0
Yohan CourbeIT ManagerAuthor Commented:
Hello Cliff,

I'm not sure to understand your comment, the static route 10.0.0.0/8 10.4.100.1 routes all my lan traffic to the LAN (and it works - verified with traceroute). But anyway, what would you recommend for this kind of setup ?

Cheers
0
Cliff GaliherCommented:
That static route shouldn't exist and in a properly designed network is totally unnecessary. Just declaring the IP address of your LAN NIC as 10.4.100.x/24 will auto-generate routes where all LAN traffic goes over that NIC. Your static route breaks that.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Yohan CourbeIT ManagerAuthor Commented:
Ok I got you point. I will try to find a workaround like changing policies or stuff like that (because at the end it's the problem, I got public profile. Thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.