• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1703
  • Last Modified:

Routing and Remote Access causing problem with IPV6

Hello,

We have just deployed Windows 2008 Enterprise Server as DC with Exchange 2010 on the same server.  Everything works fine until I enable Routing and Remote Access which results in server registering itself in DNS with an additional IP.   When I ping the server with server name it replies back with IPv6 address..NSLOOKUP results in Unknown and first 10 IPs in DHCP scope appear in Leased as RAS.

How can I resolve this issue?
0
fais79
Asked:
fais79
  • 5
  • 4
1 Solution
 
losipCommented:
First of all, do NOT disable IPv6 by changing the DisabledComponents value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ because this will make RRAS stop working.

However, you should uncheck TCP/IPv6 in the Properties pane of the status of the network interfaces.  This will stop them registering the IPv6 address in DNS.  This will cause a couple of warning events on RRAS service start but these are benign and you will find that RRAS will operate as expected.

The leases in DHCP for the VPN virtual ports are normal and required so that clients connecting to RAS can be given appropriate IP addresses on your network.

I hope I've understood your problem correctly.
0
 
fais79Author Commented:
Unticking  TCP/IPv6 in the Network Interface Properties will not stop Exchange from working will it?
0
 
losipCommented:
No, Exchange does not need IPv6 providing that you have proper IPv4 communication internally and externally.

I have a system running here very close to yours: Windows Server 2008R2 as a DC with DNS, DHCP, CertSvcs, Exchange 2010 and RRAS, amongst other roles.  All works very cleanly.

The only other thing you may want to do is to check the protocol bindings and order.  To do this, click Control Panel  / Network and Internet / Network Connections, press Alt, then click on Advanced / Advanced Settings and make sure that, for your "internal" NIC your are binding only IPv4 to File and Printer Sharing and also for Client for Microsoft Networks - and then for your "external" NIC, no bindings are checked for File & Print or Client for Microsoft.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
fais79Author Commented:
I've just tried this and when I restarted the server it came back up and login screen came on instantly.  When I logged in I noticed that several Exchange Services were either not ON or were starting up also the network card had cross on.  I waited 30mins but no joy therefore, I had to force restarted server and go in Windows with Network mode and had to tick IPv6 in Network Interface Properties.  Restarted the server and it came on ok with all exchange services starting up ok.

But now everytime I login the network card has a cross and takes 2mins to come on after logging in..

0
 
losipCommented:
I'm a little confused that you refer to THE network card.  If you're running Routing and Remote Access Server, where are you routing from and to?  Or are you just trying to build a Remote Access Server with no routing?  In my previous replies, I referred to "internal" and "external" NICs as if you have two.  Do I take it that this is not the case?  Can I also confirm that your network is IPv4 and you haven't installed everything as IPv6?

Where does the network card show the cross? In Network & Sharing Center?  If you click on it and click Properties, then you DO find a check mark alongside TCP/IPv4, don't you?

Can you do ipconfig /all from a command prompt and post the results?  Meanwhile, reverse the changes you made and check that the system behaves as before because something isn't quite adding up.
0
 
fais79Author Commented:
Please see the attached image to see the exact problem I am having..  As you can see the static ip for the server is set to: 10.0.0.2

But then it picks up 10.0.0.109 which causes problems for some clients because they try tp resolve the server name with the: 10.0.0.109 rather than 10.0.0.2.

So if I do ping servername it returns with 10.0.0.109

Please advise?
IPCONFIG.jpg
0
 
fais79Author Commented:
I have solved the problem myself!

All I had to do is in DNS takeout the RAS IP under Interfaces --> Listen to
0
 
losipCommented:
Well done for finding this before I had a chance to tell you!  The multiple IP addresses is normal on a RAS server - it effectively becomes dual-homed and the precautions needed for dual-homed devices are important.  As well as removing the DNS entry, you might wish to check the network bindings in the manner I pointed out on November 10.
0
 
fais79Author Commented:
I have solved the problem myself!
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now