Home > Unable To > Unable To Contact A Dhcp Server. The Automatic Private Ip Address

Unable To Contact A Dhcp Server. The Automatic Private Ip Address


Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More... It has only one LAN adaptor. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. IPCONFIG on the member/RRAS server shows: Windows IP Configuration Host Name . . . . . . . . . . . . : MSDATA Primary Dns Suffix . Check This Out

I would like to use DHCP to assign my RAS addresses and am getting to the stage where i may reinstall ISA as i think this is the problem. Thanks very much. 0 Comment Question by:TriumphLTD Facebook Twitter LinkedIn Best Solution byTriumphLTD Thanks for all your help Robwill but none of the suggestions are doing the trick. It turns it into a multihomed DC. Also restarted DHCP and RRAS as well a few times.

Unable To Contact A Dhcp Server. The Automatic Private Ip Address

Ace Fekay MVP, MCT, MCITP Enterprise Administrator, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft The IP got assigned but could not ping remote ips. Remote access Server issuing private ip Discussion in 'Windows Server' started by EricBee, Apr 29, 2011. Going through the config, we disabled the feature, then the DCs were able to replicate. .

Ace . srhoades, Apr 30, 2011 #2 EricBee Thread Starter Joined: Apr 5, 2011 Messages: 5 Hello Srhoades, Thank you for your contribution. Click Apply and OK. Now, after an overnight reboot, we are back to the earlier scenario - no DHCP.

I have verified I can ping the DHCP server with no issues8. Rras 20169 So, I started Wireshark again - and it works!! Concepts and definitions will form the solid foundation of your future DBA expertise. If not this might cause the DHCP service not to be started when RRAS starts up and therefore switch the static address pool setting, but that is just a wild guess.

x 10 Private comment: Subscribers only. This is very strange. Storage Software SBS Windows Server 2003 Windows Server 2008 Setup Mikrotik routers with OSPF… Part 1 Video by: Dirk After creating this article (, I decided to make a video (no DHCP Server: Added Broadcast Address to scope option.

Rras 20169

Note that I have specifically not enabled anypacket filtering on the RRAS machine. x 16 Cesar Caminero I had this error on a Small Business Server with ISA Server installed after I enabled the VPN Client Access. Unable To Contact A Dhcp Server. The Automatic Private Ip Address I undertand the other issues you riase. Thanks any way. 0 LVL 77 Overall: Level 77 SBS 47 VPN 36 DHCP 11 Message Active today Expert Comment by:Rob Williams ID: 221610532008-08-05 Let us know how you make

TECHNOLOGY IN THIS DISCUSSION Read these next... © Copyright 2006-2017 Spiceworks Inc. his comment is here Run through this checklist and verify that the DHCP server is on the same subnet as RRAS and also verify your relay agent. How many DCs do you have? I know you said you have but just run through it again. View this "Best Answer" in the replies below » 3 Replies Pure Capsaicin OP Best

It did not have the relay agent configured, but acted as if it did. I suggest a member server. AD is correctly replicating between DCs. Event ID: 20169 Source: RemoteAccess Source: RemoteAccess Type: Warning Description:Unable to contact a DHCP server.

Turns out NIC drivers issue, so each time I restart the server my NIC is in a not-ready state in which RRAS service is already running.  Once I resolve the NIC Same with WINS proxy, and that should be disabled, too. No, create an account now.

I just restarted them again for good measure.

Obviously, I can't run Wireshark continuously to fix this, and I guess the problem is some low level network filters that for some reason are negated while Wireshark is capturing. Ace . Notice how in the ipconfig that it shows IP routing is enabled? It has been restarted several times.

Reason I'm asking, part of the problem is that it may not be able to contact AD to get authorization information. On the IPv4 tab, select an address pool, and then click Edit. In environments that I work with - typically single server - there is no option but to put RRAS on the DC, and I generally do not have issues with this. navigate here Short URL to this thread: Log in with Facebook Log in with Twitter Log in with Google Your name or email address: Do you already have an account?

To use Google Groups Discussions, please enable JavaScript in your browser settings, and then refresh this page. . It appears that this was allowing 'normal' dhcp requests from workstations to be answered, but not the requests from RRAS - possibly becuase it was seeing multiple requests from the same I 'll use it for IT Task Documentation. Notice how in the ipconfig that it shows IP routing is enabled?

RAS is set to issue ips through DHCP. srhoades, May 2, 2011 #6 EricBee Thread Starter Joined: Apr 5, 2011 Messages: 5 no just one EricBee, May 2, 2011 #7 srhoades Joined: May 15, 2003 Messages: 2,282 "DHCP I also looked at an SBS machine that was set up with the "Configure remote access" wizard. You’ll be auto redirected in 1 second.

AD communications can cause this, too. If it is set to the WAN adapter or default, which doesn't always work, it will not see a DHCP server and default to 169.254.x.x 0 Message Author Comment by:TriumphLTD Rebooted computer, and network card went offline (unable to establish a connection)3. Do you have any idea about the first error?

NOw one interesting thing I just tried: I launched a manual VPN using the same user account as the router and it connects right away and lets me ping remote ips. Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. English: Request a translation of the event description in plain English. I have restarted the server 3 times today.

Follow the procedures in the order in which they appear until the problem is resolved. Are any errors reported in the event viewer? I checked the Remote Access Server settings and found out that the clients are being issued private ip addresses ( I also checked all the services that were automatic.