Server 2012 r2 emulated nic's

Hello
I have been told that within 2012 r2, you can have emulated nic's
So, if I only have 1gb nic, and want to run a proper cluster, I can add 'virtual' nic's to preset to the OS.
Is that possible?
best regards
jesper vindum, denmark

I'm not sure where you are going with this. With a single NIC, there is absolutely no way to run a 'proper cluster'. A proper cluster has no single point of failure. A single NIC means there is a single point of failure.
Microsoft Failover Clustering can run just fine with a single NIC - I've done it many times. But it is not a 'proper cluster'. Or, as suggested, you can install Hyper-V and then create multiple virtual switches for use by virtual machines.
Then you can create guest clusters with multiple NICs, but at that point, the host becomes a single point of failure. Again, no 'proper cluster'.
I don't know what Henrik was getting at with his answer.
I think we need to have a better understanding of what you are trying to do before we can confidently agree that you are proceeding correctly.
. : | : . : | : . tim

Similar Messages

Direct Access Server 2012 R2 Single NIC DNS problem with 8.1 Enterprise

Dear helpers,
I am beginning to rip my hair over the following problem and I am asking for some guidance:
I have setup DA on a server 2012 R2 with the simple wizard using one NIC. I have opened up port 443 to my DA Server and operations status is showing green on everything. I have used Djoin to join a remote win 8.1 enterprise client to our domain and
setup DA. I can see that my tunnel is established and the client shows up as an IPHTTPS client on my server:
Role                       : client
URL                        : https://vpn.ourdomain.com:443/IPHTTPS
Last Error Code            : 0x0
Interface Status           : IPHTTPS interface active
Connection status on client is stuck in connecting and the eventlog on client gives me following error:
The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:
           Adapter Name : {424F50B4-BF1A-4D96-81FA-7D7436A99F07}
           Host Name : TEST
           Primary Domain Suffix : ourdomain.com
           DNS server list :
                172.16.8.1
           Sent update to server : <?>
           IP Address(es) :
             172.16.8.110
The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running at
this time.
I understand why this is failing because it seems like it is contacting the local DNS to register and that's wrong.
Get-DaConnectionStatus gives me the following:
Status    : Error
Substatus : CouldNotContactDirectAccessServer
I can ping the name on the DA server and also the IPv6 address, I can also do nslookup if i set the server used to my internal DNS-servers IPv6 address(DNS and DA server = same machine). My DA Client GPO is being applied to the client and i get an NRPT table
looking as follows:
Settings for DirectAccess-NLS.ourdomain.com
DirectAccess (Certification Authority) :
DirectAccess (IPsec)                    : disabled
DirectAccess (DNS Servers)              :
DirectAccess (Proxy Settings)           : Use default browser settings
Settings for vpn.ourdomain.com
DirectAccess (Certification Authority) :
DirectAccess (IPsec)                    : disabled
DirectAccess (DNS Servers)              :
DirectAccess (Proxy Settings)           : Use default browser settings
Settings for .ourdomain.com
DirectAccess (Certification Authority) :
DirectAccess (IPsec)                    : disabled
DirectAccess (DNS Servers)              : fd1f:6801:cc14:3333::1
DirectAccess (Proxy Settings)           : Bypass proxy
I cannot reach any internal resources by name or IPv4 address except the DA server.
I will gladly provide more info if needed
Please help!
//Cris

Hi,
Thanks for your reply.
Firstly, computer certificates are necessary for DirectAccess.
In addition, it is no need to assign an IPv6 address on all the servers. In Windows server 2012/R2, the
Built-in NAT64 and DNS64 support for accessing IPv4-only resources.
If you select Configure DirectAccess Clients with DNS client suffix search list and add additional suffixes to the list,
you can search for short, unqualified computer names in more than one specified DNS domain.
For more detailed information about DNS suffix search list, please refer to the link below:
Step 2: Configure the DirectAccess Server
Best regards,
Susie

Server 2012 w/two nics

I have a Dell Server with 2 NIC cards. One is configured with a static Public IP address for two remote stores to connect thro RDP. The other card is configured for the LAN. This works part of the time. Sometime the entire internet lags terribly. Think it
is possibly how I have the cards configured. I am new to this!! Can someone help?
Thanks

Hi TimCDP,
In general, we configure IP address, subnet mask, Default gateway and DNS server for the Internet faced NIC. We leave the default gateway blank for the intranet faced NIC.
You can try the settings above and see how it works.
If issue persists, please provide us more detailed information and ipconfig /all for further research.
Thanks.
Jeremy Wu
TechNet Community Support

Enable Lan Routing Windows Server 2012

Hi!
I'm trying to setup the RRAS in a Windows server 2012 to route between my two networks. I have a windows server 2012 with two nics and the RRAS installed. I installed "Lan Routing" custom option.
My configuration is:
Server nic1 - 192.168.1.254 255.255.255.0 (no dfgateway)
Server nic2 - 192.168.103.54 255.255.255.0 (no dfgateway)
Clients subnet1 - 192.168.1.x 255.255.255.0 192.168.1.254
Clients subnet2- 192.168.103.x 255.255.255.0 192.168.103.54
The problem is that from a client of subnet1 i can ping 192.168.1.254 and 192.168.103.54 but i can't ping clients of subnet2, and backwards the same problem.
Thanks.

Your client machines need to know how to find the route to the other subnet.
1) So on a client on subnet 1, open a Command Prompt and type:
route add -p 192.168.103.0 mask 255.255.255.0 192.168.1.254
This adds a permanent route which tells the client to go to 192.168.1.254 to find network 192.168.103.0
2) On the clients on subnet2 you would type:
route add -p 192.168.1.0 mask 255.255.255.0 192.168.103.54
Make sure the clients have the appropriate server NIC address as their default gateway and DNS.
For example, for clients on subnet1:
IP: 192.168.1.x
Gateway: 192.168.1.254
DNS: 192.168.1.254
That is misleading at best. The original post is a straight forward example of subnet to subnet routing. No additional routes are required because the default routing is quite adequate. If you look at the addresses of the static routes you provide
you will see that they are the same as the default addresses already set (so they are redundant).
Ping is not a reliable test of connectivity any more. Built-in firewalls will block it by default. You will need to temporarily disable the firewalls of the clients to test with ping (unless you enable ICMP echo in both directions on all clients).
Bill

Server 2012 R2 Crashes with NIC Team

Server 2012 R2 Core configured for Hyper-V. Using 2-port 10Gbe Brocades, we want to use NIC teaming for guest traffic. Create the team... seems fine. Create the virtual switch in Hyper-V, and assign it to the NIC team... seems fine. Create
a VM, assign the network card to the Virtual switch... still doing okay. Power on the VM... POOF! The host BSOD's. If I remove the switch from the VM, I can run the VM from the console, install the OS, etc... but as soon as I reassign the virtual
NIC to the switch, POOF! Bye-bye again. Any ideas here?
Thank you in advance!
EDIT: A little more info... Two 2-port Brocades and two Nexus 5k's. Running one port on NIC1 to one 5k, and one port on NIC2 to the other 5k. NIC team is using Switch Independent Mode, Address Hash load balancing, and all adapters active.

Hi,
Have you updated the NIC driver to latest?
If issue persists after updating the driver, we can use WinDbg to analyze a crash dump.
If the NIC driver cause the BSOD, please consult the NIC manufacture about this issue.
For detailed information about how to analyze a crash dump, please refer to the link below,
http://blogs.technet.com/b/juanand/archive/2011/03/20/analyzing-a-crash-dump-aka-bsod.aspx
Best Regards.
Steven Lee
TechNet Community Support

DirectAccess on Server 2012 R2 with Single NIC behind NAT on IPv4 only Corporate Network Results in "DNS Not Working Properly"

I hit this problem at a customer site and can re-produce it in a simple lab. Lab environment: servers:
1x Server 2012 R2 DC and DNS server - DC1 - 10.0.0.1
1x Server 2012 R2 DirectAccess (DA) server - DA1 - 10.0.0.100
Servers are running "Update" (KB2919355) and following DA hotfixes:
KB2929930
KB2966087
I configured DA (via advanced wizard) as follows:
DA and remote access
AD group
directaccess-webprobehost DNA (A) record pointing to 10.0.0.100
behind an edge device (with a single network adapter)
SSL certificate from enterprise root CA issued to directaccess.contoso.com
NLS on remote server using https://nls.corp.contoso.com
DNS: corp.contoso.com = 10.0.0.1; nls.corp.contoso.com = ""
DNS suffix search list = corp.contoso.com
The DNS server validates successfully in the configuration UI.
With this configuration, I get a static IPv6 address of fd79:7a37:cbd9:3333::1/128 assigned to the NIC
The operations status is all green apart from DNS which displays the following error:
"DNS: Not Working Properly"
Error:
None of the enterprise DNS servers fd79:7a37:cbd9:7777::a00:1 used by DirectAccess clients for name resolution are responding. This might affect DirectAccess client connectivity to corporate resources.
Causes:
Enterprise DNS servers fd79:7a37:cbd9:7777::a00:1 are not responding.
I can, however ping fd79:7a37:cbd9:7777::a00:1 (which is the DNS64 translation of 10.0.0.1)
I would like to know what checks are failing as there are no failures in Event Viewer.
I have come across forums where people have the same issue and fix it by specifying the local IP (in this case 10.0.0.100) as the DNS server, however Richard Hicks has confirmed with me that the DNS server should be set to the DNS server, not the DA server's
IP.

Thanks for the post Matt,
ISATAP has been disabled on my DA server, so the results of a "ROUTE PRINT -6" command yields:
===========================================================================
Interface List
12...00 15 5d 01 03 64 ......Microsoft Hyper-V Network Adapter
1...........................Software Loopback Interface 1
14...00 00 00 00 00 00 00 e0 IPHTTPSInterface
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
12 261 fd79:7a37:cbd9::/48 On-link
14 306 fd79:7a37:cbd9:1000::/64 On-link
14 306 fd79:7a37:cbd9:1000::/128   On-link
14 306 fd79:7a37:cbd9:1000::1/128     On-link
14 306 fd79:7a37:cbd9:1000::2/128    On-link
14 306 fd79:7a37:cbd9:1000:814c:28be:46b5:52c1/128   On-link
12 261 fd79:7a37:cbd9:3333::1/128 On-link
12 261 fd79:7a37:cbd9:7777::/96 On-link
12 261 fe80::/64 On-link
14 306 fe80::/64 On-link
12 261 fe80::20c0:e848:d304:9f01/128   On-link
14 306 fe80::814c:28be:46b5:52c1/128     On-link
1 306 ff00::/8 On-link
12 261 ff00::/8 On-link
14 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
If Metric Network Destination Gateway
0 4294967295 fd79:7a37:cbd9:1000::/64 On-link
0 4294967295 fd79:7a37:cbd9::/48 On-link
0 4294967295 fd79:7a37:cbd9:7777::/96 On-link
===========================================================================

Windows Server 2012 R2 - Hyper-V NIC Teaming Issue

Hi All,
I have cluster windows server 2012 R2 with hyper-v role installed. I have an issue with one of my windows 2012 R2 hyper-v host.
The virtual machine network adapter show status connected but it stop transmit data, so the vm that using that NIC cannot connect to external network.
The virtual machine network adapter using Teamed NIC, with this configuration:
Teaming Mode : Switch Independent
Load Balance Algorithm : Hyper-V Port
NIC Adapter : Broadcom 5720 Quad Port 1Gbps
I already using the latest NIC driver from broadcom.
I found a little trick for this issue by disable one of the teamed NIC, but it will happen again.
Anyone have the same issue with me, and any workaround for this issue?
Please Advise
Thanks,

Hi epenx,
Thanks for the information .
Best Regards,
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Server 2012 r2 Hyper-v guest network speed with 10 GB NIC's

Hi
Setting up a Server 2012 r2 Hyper-v host with an onboard 4 port 1 GB nic and a offboard dual port 10 GB nic. We are using the 1gb quad port for management. The 10 Gb we intend using for hyper-v guest use however we don't seem to be able to achieve very high
speeds though the 10 GB adapter when assigned to a virtual switch. Testing the 10 Gb nic from the host confirms that we can transfer/get 10 GB speeds. When assigned to a virtual switch however the speed drops to about 1-2 Gbps. Has anybody seen anything like
this ?. We've tried a variety of settings and i can confirm that the network traffic is using the 10 GB nic.

Hi,
I am almost certain what you see is by design. I don't want to go into to much detail because I'm in a bit of a hurry. But allow me to explain.
Suppose you have a 10Gb NIC interface and an multi-core CPU. When you have RSS (Receive-Side Scaling) disabled a single core can normally handing
around 2.5-4.3Gbps. When you enable RSS the data streams/traffic is spread across multiple cores.
But RSS is a network optimization feature for the Management OS, not for a vSwitch. Instead you should use VMQ (Virtual Machine Queuing). VMQ is
the equilavant of RSS, but then intended for VMs. But... there is a difference. VMQ does not spread single data streams/traffic across multiple cores. Instead is (dynamically) assigns each vmNIC its own core. So... you don't use multiple-cores at a time for
a single vmNIC. You can't use RSS and VMQ at the same time. Keep that in mind.
But... you can accomplish this by enabling vRSS as well. That's another story.
If you watch the following video, at the end you know all about VMQ.
Hyper-V dVMQ
http://www.hypervrockstar.com/tag/dvmq/
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

Windows Server 2012/2012R2 NIC Teaming Mode

Hi,
Question 1:
In Windows Server 2012 the following teaming mode was recommended for Hyper-V NIC teams:
Teaming mode: Switch Independent
Load balancing mode: Hyper-V Port
All Adapers Active
In a session at TechEd 2014 it was stated that Dynamic is the new recommendation for Windows Server 2012 R2. However, a Microsoft PFE stated a few weeks ago that he would still recommend Hyper-V Port for Windows Server 2012 R2. What is your opinions around
this?
Question 2:
We have a Hyper-V Failover Cluster which isn`t migrated to 2012 R2 yet, it`s running 2012. In this cluster we use Switch Independent/Hyper-V Port for the team. We also use converged networking, having 2 physical adapters bound to the NIC team, as well as
3 virtual adapters in the management OS for management, CSV and Live Migration. Recently one of the team NICs failed, and this incident also caused the cluster membership on the affected node to go offline even though the other team NIC was
connected. Is this expected behaviour? Would the behaviour be different if 2012 R2 with Dynamic mode was being used?

Hello,
As for question number 1:
For Hyper-V workload it's recommended to use Dynamic with
Switch Independent mode. Why?
This configuration will distribute the load based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm will redistribute flows to optimize team member bandwidth utilization so individual
flow transmissions may move from one active team member to another. The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets so it takes steps to minimize that possibility.
The receive side, however, will look identical to Hyper-V Port distribution. Each Hyper-V switch port’s traffic, whether bound for a virtual NIC in a VM (vmNIC) or a virtual NIC in the host (vNIC), will see all its inbound traffic arriving on a single
NIC.
This mode is best used for teaming in both native and Hyper-V environments except when:
1) Teaming is being performed in a VM,
2) Switch dependent teaming (e.g., LACP) is required by policy, or
3) Operation of a two-member Active/Standby team is required by policy.
As for question number 2:
The Switch Independent/Hyper-V Port will send packets using all active team members distributing the load based on the Hyper-V switch port number. Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port
is affinitized to exactly one team member at any point in time.
In all cases where this configuration was recommended back in Windows Server 2012 the new configuration in 2012 R2, Switch Independent/Dynamic, will provide better performance.
Microsoft recommend for a clustered Hyper-V deployment
in Windows server 2012 to use Switch Independent/Hyper-V Port as you mentioned and to configure
Hyper-V QoS that applies to the virtual switch. (Configure minimum bandwidth in
weight mode instead of in bits per second and Enable and configure QoS
for all virtual network adapters
Did you apply QoS on the Converged vSwitch after you
created the team?? However Nodes are considered down if they do not respond to 5 heartbeats. The Switch Independent/Hyper-V Port does not cause the cluster to goes down if one NIC failed. The issue is somewhere else and not in the teaming mode
that you choose.
Hope this help.
Regards,
Charbel Nemnom
MCSA, MCSE, MCS, MCITP
Blog: www.charbelnemnom.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if
a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!
http://www.youtube.com/watch?v=8mOuoIWzmdE
Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain as best I can and apologies from the start.
It’s a bit of both Hyper-v and Server 2012R2.
I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below
examples.
New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false
Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"
Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the
HostSwitchTeam for selection. When installed it shows the Microsoft Network Multiplexor Driver as the only option.
Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.
Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!
Any help would be much appreciated.
Paul
Paul Edwards

Hi P.J.E,
>>I have teams so a bit confused as to the adapter bindings and if the teams need to be added or just the vEthernet Nics?.
Nic 1,2
HostVMSwitchTeam
Nic 3,4,5
HostMgmtSwitchTeam
>>The adapter Binding settings are:
HostMgmtSwitchTeam
V-Curric
Nic 3
Nic 4
Nic 5
V-Livemigration
HostVMSwitch
Nic 1
Nic 2
V-iSCSI
V-HeartBeat
Based on my understanding of the description , "HostMgmtSwitchTeam and
HostVMSwitch " are teamed NIC .
You can think of them as two physical NICs (do not use NIC 1,2,3,4,5 any more , there are just two NICs "HostMgmtSwitchTeam and
HostVMSwitch").
V-Curric,
V-Livemigration , V-iSCSI ,
V-HeartBeat are just VNICs of host (you can change their name then check if the virtual switch name will be changed )
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Server 2012 R2 NIC Teaming and DHCP Issue

Came across a weird issue today during a server deployment. I was doing a physical server deployment and got Windows installed and was getting ready to connect it to our network. Before connecting the Ethernet cables to the network adapters, I created a
NIC Team using Windows Server 2012 R2 built-in software with a static IP address (we'll say its 192.168.1.56). Once I plugged in the Ethernet cables, I got network access but was unable to join our domain. At this time, I deleted the NIC team and the two network
adapters got their own IP addresses issued from DHCP (192.168.1.57 and 192.168.1.58) and at this point I was able to join our domain. I recreated the NIC team and set a new static IP (192.168.1.57) and everything was working great as intended.
My issue is when I went into DHCP I noticed a random entry that was using the IP address I used for the first NIC teaming attempt (192.168.1.56), before I joined it to the domain. I call this a random entry because it is using the last 8 characters of the
MAC address as the hostname instead of the servers hostname.
It seems when I deleted the first NIC team I created (192.168.1.56), a random MAC address Server 2012 R2 generated for the team has remained embedded in the system. The IP address is still pingable even though an ipconfig /all shows the current NIC team
with the IP 192.168.1.57. There is no IP address of 192.168.1.56 configured on the current server and I have static IPs set yet it is still pingable and registering with DHCP.
I know this is slightly confusing but I am hoping someone else has encountered this issue and may be able to tell me how to fix this. Simply deleting the DHCP entry does not do the trick, it comes back.

Hi,
Please confirm you have choose the right NIC team type, If you’ve previously configured NIC teaming, you’re aware NIC teams usually require the assistance of network-side
protocols. Prior to Windows 2012, using a NIC team on a server also meant enabling protocols like EtherChannel or LACP (also known as 802.1ax or 802.3ad) on network ports.
More information:
NIC teaming configure in Server 2012
http://technet.microsoft.com/en-us/magazine/jj149029.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V vSwitch on a NIC-Team (Server 2012 R2) has limited connectivity

Hi,
I have two servers both running Server 2012 R2. One of these servers is serving as a DC and is working fine. The other is supposed to be a Hyper-V-Host, but I cannot get networking working on this system. Both systems have Hyper-V role installed. Both have
2 NICs configured as a team. The team is configured as switch-independent, Hyper-V-Port, None (all adapters active). A Hyper-V-Switch using this team as external network is configured and is shared with the host operating system. This should work fine and
does on one of the servers. On the other I get a warning sign stating limited connectivity. The server seems to sent packages but it receives none. Deleting the switch and simply using the team for network access works fine. So it has to be related to the
switch. But I do not know what's wrong with it. Any ideas?
Regards,
Oliver

Hi ogerlach_isw,
Generally please don’t install others role on Hyper-V server, if your DC using NIC teaming, please break the teaming then monitor this issue again.
More information”
Everything you want to know about Network Teaming in Windows Server 2012
http://blogs.msdn.com/b/virtual_pc_guy/archive/2012/12/07/everything-you-want-to-know-about-network-teaming-in-windows-server-2012.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

NIC teaming shows no adapters (server 2012 R2)

I think you are almost to the point of nuke and pave to fix the issue. (well not totally yet).
What I would do is go into the device manager and remove all physical network adapters. Reboot and then let windows redetect and add them. This should fix the network communication issue.
With that done, you need to answer what Rod-IT asked, how are you teaming these NICs? Are you using the computer manufacturer's program, the network adapter manufacturer's program or something else? Once you get beyond that what type of teaming are you trying to setup fail over (hot spare), LACP, switch assisted load balancing. Some load balancing settings need you to change the switch settings too.
Also what brand of NICs are these?

I have a server 2012 R2 system and on the NIC teaming it shows no adapters and windows network and sharing center shows none as well.
I do not want to have to reinstall :( I've tried rebuilding wmi repository and it doesn't work)
This topic first appeared in the Spiceworks Community

Server 2012 Direct Access Single NIC cant get it to work

Hi,
I am having some real issues with setting up Direct Access with Server 2012 and a Windows 8 client, it simply won’t work at all.
First of all I should describe my setup:
I have an internet connection with a static IPv4 address on the external network adapter of the router
The internal network address (the address of the router which has the internet connection) is 192.168.1.1
Server1 (windows 2008 R2 Standard) has a static IPv4 address 192.168.1.2 and has some ports forwarded from the router (443, 25, 80) this server is a domain controller, email server, and has the DNS, DHCP and
certificate services
Server 2 (Windows 2008 R2 standard) has static IPv4 address 192.168.1.3 it has no ports forwarded from the router as it has no services accessed externally, it is used as a file server and print server, backup
domain controller and backup DNS.
Server 3 (Windows 2012) has static IPv4 address 192.168.1.4 and has the Remote Access server role installed along with all the other default features and roles it requires in the setup process.
These servers have all got an IPv6 address which I assume the server has configured automatically, there has been no deliberate configurations made to disable IPv6
I have no UAG or proxy server or anything else to route packets to internal servers. Just this router which has the option for port forwarding (I assume that’s NAT isn’t it?) sorry don’t know much about that
area.
I go through the setup wizard in remote access to configure direct access, in the external URL I have entered da.mydomain.com and created a host A record in my external domain name providers DNS which points
the da record to my external IP address. The wizard creates all the GPO’s, scoped correctly, and applied to a Windows 8 client. The operational status shows its all working and I got green ticks. However, when I connect the client to the internal network it
doesn’t seem to have correctly got the DA settings. I run the following in powershell
Get-DnsClientNrptPolicy
Nothing displays – at all
Get-NCSIPolicyConfiguration
Description
: NCSI Configuration
CorporateDNSProbeHostAddress
: fdd8:dd4a:ea42:7777::7f00:1
CorporateDNSProbeHostName
: directaccess-corpConnectivityHost.mydomain.local
CorporateSitePrefixList
: {fdd8:dd4a:ea42:1::/64, fdd8:dd4a:ea42:7777::/96, fdd8:dd4a:ea42:1000::1/128,
fdd8:dd4a:ea42:1000::2/128}
CorporateWebsiteProbeURL
: http://directaccess-WebProbeHost.mydomain.local
DomainLocationDeterminationURL : https://DirectAccess-NLS.mydomain.local:62000/insideoutside
Get-DAConnectionStatus
Get-DAConnectionStatus : Network Connectivity Assistant service is stopped or not responding.
At line:1 char:1
+ Get-DAConnectionStatus
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo
: NotSpecified: (MSFT_DAConnectionStatus:root/StandardCi...onnectionStatus) [Get-DAConnect
   ionStatus], CimException
+ FullyQualifiedErrorId : Windows System Error 1753,Get-DAConnectionStatus
I go into services.msc and find that the network connectivity assistant is not started, it wont start either something must trigger it but I have no idea how to get it triggered to start… this might be my only
source of problem perhaps but on a more network level question:
If I have such ports as 80, and 443 (which I assume DA uses in some form with a public IPv4 internet address) directed at server 1, how does the DA connection get to server 3 which has the DA role installed?
I could create another record on the server which also opens port 443 to server as well as for server 1, but then how would the router know which server to pass the DA connection to if the same port is open for two different servers?
Either way, this first issue is that the client doesn’t seem to have the ability to connect internally correctly yet, so maybe this connectivity service is a good place to start? My understanding is that the
networks icon in the system tray should show that there is a corporate connection, but it doesn’t. also, the client seems to have the NLS certificate in the computer certificate store, so the cert side of things is working and the GPO side is working.
Many thanks
Steve

ahh i see, so just to enlighten me even further...
If a company has two web servers that would mean they would need two different public facing IP addresses so they can route to each internal web server. If, like the big companies have, they
may have many web servers (possibly more than 100) I’m assuming that simply buying more public IP addresses would have a limit, especially since the IPv4 address space is pretty much exhausted. So is this where proxy systems come into play like ISA and Forefront,
is this what they do?
I assume if such a product was implemented you could go down to just one or two public IP addresses, point all traffic to the ISA server and that in turn would do all the routing of packets
to each server behind the NAT/router (probably based on some sort of domain name or sub domain namespace as it’s parameter for forwarding?)
Secondly, what I have done is installed windows server 2012 and used that as a direct access client (I read on another forum that the windows 8 RP doesn’t have the enterprise bits to make this
work). I have got much further with the 2012 server acting as a client (installed on laptop, installed desktop experience and wireless LAN),
but when I run the following command on my DA client I get the following status
Get-DAConnectionStatus
Status:
connectedlocally
Substatus:
none
This appears to work fine, when im connected to the local network. But then I disconnect and run the command again and I get the following:
Status:
Error
Substatus:
NameResolutionFailure
On my router what I did is temporarily disable port 443 going to my original server and instead opened it up pointing to my other server, so 443 traffic should be going to my DA server now, but I don’t understand why its giving the name resolution failure
status. I have a host A record called “da” with my domain hoster, and entered the full domain namespace in the DA wizard as da.mydomain.com (the Host A record has been up there for more than a week so it’s propagated through the net)
So, a bit further but stuck again.

Server 2012 emulation

Can anyone tell me if server 2012 emulates server 2003, we have old in house developed software that runs on sever 2003 or PC's that emulate XP Pro and Win7 only, we use the software for our manufacturing facility and currently don't
have the resources to redevelop this software

Install the telnet client software on the server and then run telnet.exe to open a link to the remote device to manage it - that works with things like routers that are connected via the network.
If you need to connect to a true serial device over a serial cable, you will need to get a USB to serial adapter and the driver to go along with it. Then use something like putty to talk over that cable.
.:|:.:|:. tim
I apologize, my question is a little misleading. The switches and routers I connect to are not on any network, I work at a station where I frequently configure routers and switches via CLI and then ship them to other people (this computer that got tossed
in my lap has Server 2012 included, which is why we're using it and I have no familiarity with it). The second part of your answer effectively is the answer ("get a third-party solution/puTTY"); I downloaded puTTY and it is working fine.
I'm not sure why Server 2012 refuses to associate files with Hyper-Terminal (HT runs fine if you have the .exe and the .dll, but if you try to associate the .ht file-type with the .exe, you get a message that says "Server cannot associate files to this program",
I might have to dork around in the registry to get the file type recognized).

Server 2012 r2 emulated nic's

Similar Messages

Maybe you are looking for