network card | PeteNetLive

Problem

Seen on Windows Server 2012, when configuring direct access, while running the ‘Getting Started Wizard’ you have to choose the network topology. You have a choice of edge, behind an edge device (with 1 NIC), or behind an edge device (with 2 NICs). Each choice you make will present you with one of the following errors.

An external adapter with a public IP address, IPv6 enabled and without a domain profile cannot be located.

An internal adapter with a valid IP address, DNS settings and a domain profile cannot be located.

An internal adapter with a valid IP address, IPv6 enabled, DNS settings and a domain profile cannot be located.

Solution

The reason you are getting this error is because the network card (or cards) in this server are NOT set with a domain profile, in my case it had been set to public (which was confusing as this was a domain controller).

The fix is a little unusual, and why it works I have no idea, but it worked for me.

1. Windows Key+R > ncpa.cpl {Enter} > Right click the NIC > Properties > REMOVE the tick from IPv6 > OK > Then RETICK IPv6 > OK.

2. Now if you look in ‘Network and Sharing Center’ you will see it labelled as ‘Domain network’. The wizard should now proceed without error.

KB ID 0000996

Problem

A while back I got an email “Here is a suggestion for an article. ‘How to link GNS3 with VMware Workstation'”. Sorry it’s taken me so long to get round to it, here you go Daniel Newton.

Solution

Before we start I’m assuming you have installed VMware Workstation, and you’ve installed and configured GNS3.

1. Launch VMware Workstation > Edit > Virtual Network Editor > By default there will be three networks, the one we are concerned with is the ‘NAT‘ one. I change the default IP range, (in the example below to 123.123.123.123 255.255.255.0) > Apply > OK.

2. NAT Settings > Set the default gateway for the network (Tip: Don’t choose .1, I’ve had problems with that in the past) > OK.

3. DHCP Settings > Even if you’re not going to use DHCP, enter a range of IP addresses on your network > OK.

4. Windows Key + R > ncpa.cpl {Enter} > Notice there’s two new network connections, one for the NAT network, and one for the ‘Host only’ network.

5. To avoid confusion, I rename them.

6. So they are easily identifiable, (you will see why later).

7. In GNS3 drag a ‘Cloud’ onto your workspace.

8. Right click > Configure > NIO Ethernet > Select the Network drop-down box > Select your VMware NAT interface.

9. Add > Apply > OK.

10. Note: If you are working with Cisco ASA firewalls, you cannot simply connect it to the cloud, you need to put a hub/switch or router in between them, or you will see this error message;

Dynamips error
Device does not support this type of NIO. Use an ETHSW or
hub to bridge the connection to the NIO instead.

11. With a switch in between you can connect them together.

12. Now if you give the outside of the firewall an IP on the correct network range (you configure in step 1), and set its default route to point to the gateway address, (you configured in step 2). You will have public Internet access, (assuming the host computer has Internet access).

13 Working with routers (and switches) you can connect them directly to the cloud.

14. Again set the interface IP correctly, and the default route, and you will have public Internet access.

PeteNetLive

Technology that 'Just Works'

Tag Archives: network card

Direct Access – Error While Running The Remote Access Wizard

Problem

Solution

Related Articles, References, Credits, or External Links