120 reputation
17
bio website flexlabs.org
location Chisinau, Moldova
age 27
visits member for 4 years, 8 months
seen Dec 17 at 11:21
C# ASP.NET developer for a couple of years. Posessed with an active programming spirit and with a never-ending desire to learn more.

Oct
28
asked SCVMM 2012 R2, single logical network both on trunk and access port
Oct
6
comment All networks (public + private + domain) became domain networks
Question.. My other sites also have domain controllers, and they're connected to the main site over a VPN, and that goes over the external gateway... Could that be the reason why the external adapter is marked as a domain adapter (even though the domain controllers are in different sites) ?
Oct
5
comment All networks (public + private + domain) became domain networks
Just added that in
Oct
5
revised All networks (public + private + domain) became domain networks
added ipconfig
Oct
5
asked All networks (public + private + domain) became domain networks
Oct
5
awarded  Commentator
Oct
5
comment External Network Adapter Location Domain instead of Public
Did you ever solve that problem? I just ran into the same situation =/
Aug
1
comment Avoiding a multi-homed Domain Controller in a dual network environment
@BigHomie Could you write that as an answer please so I can mark it as such then? :)
Jul
30
comment Avoiding a multi-homed Domain Controller in a dual network environment
Hmm.. We DO have another DNS in the network (public facing, hosts some public zones), which is obviously sitting on the public IP address... Sounds like I should either multi-home it, i.e. allow requests to come from both public and internal NIC, or have yet another DNS server (non public facing) that will just act as a forwarder for the DC.. Something tells me the second option is right, even if that means I need another VM.. Does that sound about right?
Jul
30
comment Avoiding a multi-homed Domain Controller in a dual network environment
Oh yeah, I definitely get that.. The DNS from DC is not public facing.. But I was under the impression that it should be able to resolve public DNS (not the other way around). So if one of the machines in the network tries to resolve a host name, it asks the DCs DNS (which is the only DNS server(s) in the server's network settings), and the DC will either know the answer, or ask it's forwarders, right?
Jul
30
comment Avoiding a multi-homed Domain Controller in a dual network environment
@BigHomie that's a very good point, and I would have gone for that, except for one thing - if I do this, what will happen with DNS forwarding? All the other servers should use the DC's DNS IP, but if the other servers try to resolve external host names - they will fail, since the DC can't resolve them, right?
Jul
30
comment Avoiding a multi-homed Domain Controller in a dual network environment
As such, a NAT is out of the question
Jul
30
comment Avoiding a multi-homed Domain Controller in a dual network environment
Multiple web servers, different IPs, hostnames etc.. Other servers are dedicated, and need full remote access. We don't have a class C subnet for nothing :-)
Jul
30
comment Avoiding a multi-homed Domain Controller in a dual network environment
The whole thing is already behind a firewall, actually. The issue with your suggestion is that if I do it like that then all the servers will have only internal IP addresses. It's no good for us, since the servers have to be public facing (a lot of them are Web servers).
Jul
30
awarded  Editor
Jul
30
revised Avoiding a multi-homed Domain Controller in a dual network environment
added 381 characters in body
Jul
30
asked Avoiding a multi-homed Domain Controller in a dual network environment
Oct
12
accepted HP ProLiant DL180 G6 SSD upgrade (sata 3)?
Oct
12
comment HP ProLiant DL180 G6 SSD upgrade (sata 3)?
That's pretty much what I expected. I'm not worried much, but I did wonder if I could improve the sequential reads as well. Thanks a lot!
Oct
11
awarded  Student