asked on

Server with two nics reporting to different clients under different NICs. DC, HyperV, RDP roles.

Dear All,

Come across a server with the following setup.

Server has 2x NICs.

It is a DC for a site and runs VM's.
One of the those VM's is an rdp box etc...

The deal is that one of the IP's has been used as a Virtual Network Switch for the VM(s).

The other NIC is meant for the network as its a DC, fileshare etc...

This is a small site.

Some clients when pinged are getting back IP 192.168.1.15 instead of lets say 192.168.1.20.

As one NIC is for HyperV and the other is Usual Network stuff.

This is causing some issues with FQDN of servers etc... for example the mail server cannot be located under the fqdn of mailserver.dom.lan only its netbios name of mailserver.

Please advise where I should start. Network has had a 2003 box demoted, Other servers are 2008r2 and 2012r2. 2003 DC has just been demoted so the domain functional level is still 2003 at present.

Many thanks in advance.

R

giltjr

Did somebody create a A record on the DNS server for the host name mailserver.dom.lan?

Is "dom.lan" your AD integrated domain name? If so, is the host "mailserver" setup to register it host name with the DNS server?

ROM

ASKER

To add some more..

if I ping mailserver ... i get back mailserver.dom.lan... but if I ping mailserver.dom.lan I get no reply!!!

R

ROM

ASKER

There is an a record for mailserver on the dns server to point to its IP.

The other servers have the same issues. i.e. msdynamics.dom.lan ... replies when msdynamics is pinged with fqdn... but you cannot ping the fqdn.

R

SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ROM

ASKER

In DNS the DC has got both IP addresses listed under dahv01, so there are two A records.

R

ROM

ASKER

Thanks Cliff.... What do you suggest as a way forward to straighten this server out?

Thanks

R

ROM

ASKER

Short Term and Long Term please.

i.e. Short Term .. Do X with NIC config and DNS maybe.
Long Term, create a VM for DC, demote the physical server once all roles have been transferred across etc...

Thanks

R

ASKER CERTIFIED SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ROM

ASKER

Fair enough.... I thought that would be the road I would need to go down from what was being said.
No immediate MUCH shorter solution though???

I can get all of that going as a I have another server that I can turn into a DC and dedicate that as physical DC.
Dont have anything else that I could utilise as another host though, this is the best box in the gaff.
So I would need to do the following:

Create a new DC on spare server and transfer all roles over and create as DNS server and make DNS for site etc...
Demote DC on Original Server. Ensure HyperV is working by fixing it if its knackered.
Create secondary DC and DNS as VM on original box which is not a hyperv host only and file store for site. Cannot avoid that as its the box with the most space. Longer term project will organise this Im sure.

Dont have any other options.

Was hoping to have a sticky plaster solution while I organise all of this though. Its doable.. just not instant....:)

Many thanks in advance.

R

ROM

ASKER

OK.

Got a 2nd DC and DNS server as VM.
Will create a second DC on another VM on the other box and demote the original 2x NIC server.
Thanks for your help.
Will report back

R

ROM

ASKER

Thanks to all.

Looks like a straighten out is needed.
R