No one cannot access a file server after RRAS was installed

I have a Windows 2008 server. I installed RRAS last night remotely and lost connection to the server.
This morning I came to the site and uninstalled RRAS and rebooted a file server.
But no workstation can see the file server. The file server cannot ping itself and cannot ping Linksys router(192.168.1.1)

Server Ip address 192.168.1.11
Subnet : 255.255.255.0
Gateway: 192.168.1.1
DNS: 192.168.1.11/127.0.0.1
sgleeAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
sgleeConnect With a Mentor Author Commented:
I got the problem resoved by disabling the current adapter card, enabling another adapter card on the server box, and populating the same TCP/IP information.
Apparently when RRAS was installed, something happened to the main NIC.

When I arrived at the site, all TCP/IP related information remained unchanged. So I remove RRAS role from Server Manager and rebooted. WHen I logged back in, it was able to ping other servers on the network and surf the internet. However in about 1 min. I could not ping any device on the network nor I could surf the internet until I reboot & relogin.
So I learned that something(some services or program)  is taking over the NIC operation ,but I could not figure it out.
So I opened the ticket with Microsoft Support Engineer and wasted about 3 hours this morning. The support engineer's primary focus was to clean up TCP/IP settings and disabling all other 3 party servicves other than Microsoft services. We were not going anywhere. So I suggested to him "you know what, we have two NIC card - one enabled & been used& not working right now and another one disabled & not been used. How about we enable the other one? He said I could and that would not affect DOMAIN related settings. So I did and it started working.

He said that Microsoft DO NOT recommend installing RRAS on Domain Controller, even though they know it works ,but it causes problem like what I have experienced.
0
 
sgleeAuthor Commented:
In event viewer, i see an error. The processing of group policy failed. Windows can not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your DNS.


So i tried to open up a group policy, but it fails to open saying it can not find domain controller.
0
 
Pramod UbheCommented:
In the network properties make sure that below things are selected -
1. Client for Microsoft network
2. QoS Packet Scheduler
3. File and Printer Sharing for Microsoft Networks.

If that server is not a dns server, change primary or secondary DNS in network properties to actual dns server's IP address.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
sgleeAuthor Commented:
DHCP Server is showing that it started in Services.msc.
When I opened DHCP Server it has RED X.
0
 
sgleeAuthor Commented:
Qos and print file sharing are checked. Dns server is running.
0
 
sgleeAuthor Commented:
When i do ipconfig /all, i see the following in DNS.
::1
192.168. 1.11 (DC)
127.0.0.1
0
 
sgleeAuthor Commented:
All error messages are pointing to DHCP server not functioning and cab not contact domain controller.
0
 
sgleeAuthor Commented:
I found the solution by working with Microsoft Engineer.
0
All Courses

From novice to tech pro — start learning today.