Excellent point. Here's an additional thought: If the machine(s) that can't get an address use MSFT DirectAccess, and can't find the NLA internal web site (the site is down, or its SSL cert has expired), then there will be access problems for internal resources, for sure! (ask me how I know...)
Kurt On Fri, Mar 10, 2017 at 3:21 PM, Richard Stovall <rich...@gmail.com> wrote: > I saw similar weirdness once, many moons ago, and it had to do with the > "Network Location Awareness" service not being able to start. It was so > long ago that I don't remember the fix for that particular instance, but > Googling DHCP and "network location awareness" shows right many hits. Just > a thought. > > On Fri, Mar 10, 2017 at 5:20 PM, Calvin McLennan <cal...@mcltech.ca> wrote: >> >> How about a basic item (that I do not recall being requested of seen as >> yet) >> >> Cmd line - 'ipconfig /all' - send us the results of that >> >> Would be concerned if any IP address given is not on the desired network >> or is one of the 169 set. >> >> DHCP server should be yours - not some other unknown DHCP service. >> >> Cal >> >> -----Original Message----- >> From: listsad...@lists.myitforum.com >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Melvin Backus >> Sent: March 10, 2017 11:41 AM >> To: ntsysadm@lists.myitforum.com >> Subject: [NTSysADM] RE: Unable to obtain IP from DHCP server >> >> We still haven’t had an answer to the “what do the logs say” question. >> They’re there for precisely this purpose. >> >> -- >> There are 10 kinds of people in the world... >> those who understand binary and those who don't. >> >> From: listsad...@lists.myitforum.com >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Pierre-Marie Camilleri >> Sent: Friday, March 10, 2017 8:26 AM >> To: ntsysadm@lists.myitforum.com >> Subject: [NTSysADM] RE: Unable to obtain IP from DHCP server >> >> DHCP server is running on a Windows 2008 R2 domain controller >> It is on the same subnet and this is an existing machine. We are not >> having issues with new or other current machines. Just 2/3. >> >> Pierre-Marie Camilleri >> >> B.Sc. (Hons.), MBCS >> ICT Systems Engineer >> >> Laferla >> Direct >> (+356) 20939321 <tel:(+356)%2020939321> >> Dept >> (+356) 20939300 <tel:(+356)%2020939300> >> Mobile >> (+356) 79007864 <tel:(+356)%2079007864> >> Email >> pmcamill...@laferla.com.mt <mailto:pmcamill...@laferla.com.mt> >> Web >> www.laferla.com.mt <http://www.laferla.com.mt/> >> Address >> 204A | Old Bakery Street | Valletta VLT 1453 | Malta >> >> Facebook <http://facebook.com/LaferlaInsurance/> >> Twitter <http://twitter.com/laferlains> >> Google <http://google.com/+laferlainsurancevalletta> >> YouTube <https://www.youtube.com/user/laferlainsurance> >> ITunes >> <https://itunes.apple.com/mt/app/laferla-insurance/id896547301?mt=8> >> Android >> <https://play.google.com/store/apps/details?id=com.conduit.app_363d89b63be84bbc8f6b85fe86fe2e01.app&hl=en> >> Laferla Insurance Agency Limited is licensed to act as an insurance agent >> for Mapfre Middlesea p.l.c. and both companies are authorised to transact >> insurance business by the Malta Financial Services Authority. >> >> Consider the environment. Do you really need to print this email? >> Disclaimer <http://www.laferla.com.mt/laferla-email-disclaimer> >> From: listsad...@lists.myitforum.com >> <mailto:listsad...@lists.myitforum.com> >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Melvin Backus >> Sent: 10 March 2017 12:56 >> To: ntsysadm@lists.myitforum.com >> Subject: [NTSysADM] RE: Unable to obtain IP from DHCP server >> >> There are numerous possible causes but without more detail it’s hard to >> provide anything meaningful. >> >> What DHCP server is running? >> Is it on the same IP subnet / vlan? >> Are there any log entries or either the client or the server to indicate >> attempts to communicate? >> Are these new machines or existing machines which suddently stopped >> getting an IP? >> >> -- >> There are 10 kinds of people in the world... >> those who understand binary and those who don't. >> >> From: listsad...@lists.myitforum.com >> <mailto:listsad...@lists.myitforum.com> >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Pierre-Marie Camilleri >> Sent: Friday, March 10, 2017 5:41 AM >> To: ntsysadm@lists.myitforum.com >> Subject: [NTSysADM] Unable to obtain IP from DHCP server >> >> Hi all >> >> We are encountering a problem with some of our Windows 7 workstations and >> which are on the same LAN. They are unable to obtain an IP from the DHCP >> server and the only solution is to set a static IP which of course works. I >> cannot understand why this is happening to just a few. The others work fine. >> Could this be due to some system corruption? I’ve tried resetting the TCP/IP >> network stack and the Winsock all to no avail. >> Has anyone encountered this issue before? Any help would be much >> appreciated. >> >> Thanks >> Pierre >> >> Pierre-Marie Camilleri >> >> B.Sc. (Hons.), MBCS >> ICT Systems Engineer >> >> Laferla >> Direct >> (+356) 20939321 <tel:(+356)%2020939321> >> Dept >> (+356) 20939300 <tel:(+356)%2020939300> >> Mobile >> (+356) 79007864 <tel:(+356)%2079007864> >> Email >> pmcamill...@laferla.com.mt <mailto:pmcamill...@laferla.com.mt> >> Web >> www.laferla.com.mt <http://www.laferla.com.mt/> >> Address >> 204A | Old Bakery Street | Valletta VLT 1453 | Malta >> >> Facebook <http://facebook.com/LaferlaInsurance/> >> Twitter <http://twitter.com/laferlains> >> Google <http://google.com/+laferlainsurancevalletta> >> YouTube <https://www.youtube.com/user/laferlainsurance> >> ITunes >> <https://itunes.apple.com/mt/app/laferla-insurance/id896547301?mt=8> >> Android >> <https://play.google.com/store/apps/details?id=com.conduit.app_363d89b63be84bbc8f6b85fe86fe2e01.app&hl=en> >> Laferla Insurance Agency Limited is licensed to act as an insurance agent >> for Mapfre Middlesea p.l.c. and both companies are authorised to transact >> insurance business by the Malta Financial Services Authority. >> >> Consider the environment. Do you really need to print this email? >> Disclaimer <http://www.laferla.com.mt/laferla-email-disclaimer> >> >
