unknown host (gethostbyname failed) (Network Steve Forum)

unknown host (gethostbyname failed)

Hi all, I have been deployed the OS to a test machine using the same TS. Then I clear the PXE advertisement, tried to pxe boot the test machine again, then I have these error. But then I didn't do any changes on the drivers, boot images and etc. What is the problem? Requesting client identityTSPxe23/11/2009 3:59:51 PM608 (0x0260)Formatted header:TSPxe23/11/2009 3:59:51 PM608 (0x0260)<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>0dee474a-9a1a-427a-9515-0d211f6d6ee9</SourceID><SourceHost/><TargetAddress>mp:[http]MP_ClientIDManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-11-23T23:59:51Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="306"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_ClientIDManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>TSPxe23/11/2009 3:59:51 PM608 (0x0260)CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/requestTSPxe23/11/2009 3:59:51 PM608 (0x0260)Error. Received 0x80072ee7 from WinHttpSendRequest.TSPxe23/11/2009 4:00:03 PM608 (0x0260)unknown host (gethostbyname failed)TSPxe23/11/2009 4:00:15 PM608 (0x0260)hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)TSPxe23/11/2009 4:00:15 PM608 (0x0260)sending with winhttp failed; 80072ee7TSPxe23/11/2009 4:00:15 PM608 (0x0260)Will retry in 5 second(s)TSPxe23/11/2009 4:00:15 PM608 (0x0260)Executing command line: X:\WINDOWS\system32\cmd.exe /kTSBootShell23/11/2009 4:00:21 PM752 (0x02F0)The command completed successfully.TSBootShell23/11/2009 4:00:21 PM752 (0x02F0)Successfully launched command shell.TSBootShell23/11/2009 4:00:21 PM752 (0x02F0)Retrying...TSPxe23/11/2009 4:00:21 PM608 (0x0260)CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/requestTSPxe23/11/2009 4:00:21 PM608 (0x0260)Error. Received 0x80072ee7 from WinHttpSendRequest.TSPxe23/11/2009 4:00:33 PM608 (0x0260)unknown host (gethostbyname failed)TSPxe23/11/2009 4:00:45 PM608 (0x0260)hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)TSPxe23/11/2009 4:00:45 PM608 (0x0260)sending with winhttp failed; 80072ee7TSPxe23/11/2009 4:00:45 PM608 (0x0260)Will retry in 12 second(s)TSPxe23/11/2009 4:00:45 PM608 (0x0260)Retrying...TSPxe23/11/2009 4:00:57 PM608 (0x0260)CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/requestTSPxe23/11/2009 4:00:57 PM608 (0x0260)Error. Received 0x80072ee7 from WinHttpSendRequest.TSPxe23/11/2009 4:01:10 PM608 (0x0260)unknown host (gethostbyname failed)TSPxe23/11/2009 4:01:22 PM608 (0x0260)hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)TSPxe23/11/2009 4:01:22 PM608 (0x0260)sending with winhttp failed; 80072ee7TSPxe23/11/2009 4:01:22 PM608 (0x0260)Will retry in 21 second(s)TSPxe23/11/2009 4:01:22 PM608 (0x0260)Retrying...TSPxe23/11/2009 4:01:43 PM608 (0x0260)CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/requestTSPxe23/11/2009 4:01:43 PM608 (0x0260)

November 23rd, 2009 2:56pm

verify DNS is working correctly with an nslookup testmy SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

Free Windows Admin Tool Kit Click here and download it now

November 23rd, 2009 2:58pm

Hi, Yes, DNS is working, nslookup test is working fine.

November 23rd, 2009 3:22pm

look at this post then, does it help ? my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

Free Windows Admin Tool Kit Click here and download it now

November 23rd, 2009 3:25pm

Hi, I believe the driver is fine as I manage to see the ip address in winPE.

November 23rd, 2009 5:37pm

But have you tried to pingSCCM.test.com.my from the WinPE client? That's what the log is saying: name resolution failed for SCCM.test.com.my on the current host.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Free Windows Admin Tool Kit Click here and download it now

November 23rd, 2009 5:50pm

I have seen similar issues with gigabit connections where portfast needs to be enabled or the negotiation between the switch and the client times out for an extended period of time and then finally connects.Mike

November 23rd, 2009 6:29pm

I guess it would be beneficial if I would give you more information. Here are the notes I have from the time when I had the similar issue. Don't recall where I got this info from. I also noticed If I turned on a machine (on the same port) with an OS already installed there would be errors in the eventlog related to DHCP, etc. If I remember right, every time I rebooted it would show a combination of maybe 5 or 6 warmings and errors even though the client continued to work becasue the client would eventually negotiate with the switch. If you see these errors you need to turn on portfast or the vendor equivelant. Issue: When attempting to PXE Boot and install an Operating System Image with System Center Configuration Manager 2007, the Task Sequence may error out and reboot the machine. The SMSTS.LOG files may show error code 0x80072ee7 that points to a name resolution and/or networking issue. Additionally, you may notice that WINPE boots and gets an IP address from the DHCP server initially, however, once it gets to the Graphical User Interface portion of WINPE and try and run the Task Sequence it reverts to an Automatic Private IP Address (APIPA) of 169.354.x.x. Note: If you use Task Sequence Boot Media and manually configure a static IP address and subnet mask, etc. then the Task Sequence runs as expected. Cause: This can occur if portfast is not enabled on your SPT enable Cisco switch. If portfast is not enabled then the port using STP may remain in blocking mode long enough to prevent the client computer from communicating over the network. Resolution: To resolve this issue you can turn on "spanning tree portfast enable" on the Cisco switch. For more information on this feature contact your switch manufacturer or see the following article on Cisco.com's website: http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a00800f0804.shtmlMike

Free Windows Admin Tool Kit Click here and download it now

November 23rd, 2009 6:41pm

Hi all, When in winPE, I tried to nslookup, it says not recognized as an internal or external command. In winPE, I tried to ping SCCM.test.com.my and nbtstat -a sccm, it can't ping and cannot resolve the name. I ping by IP address, then I manage to get replies. After I ping -a IP address, then it seems can resolve the name. If I use one client not with PXE boot, it can nslookup successfully. Does it mean the DNS is ok? How to verify the DNS is working fine?

November 24th, 2009 6:17am

Anyway the SPT is enabled on the cisco switch. It can pxe boot and install OS according the TS before, I wonder why it doesn't work now.

Free Windows Admin Tool Kit Click here and download it now

November 24th, 2009 6:51am

nslookup doesn't exist in PE, you shouldn't use nslookup to test name resolution anyway as it is a direct query to a dns server and not an emulation of what the client does to find IP addresses for network connections.ping -a is a reverse lookup, it is not resolving a name, it is resolving an IP Address to a name.A simple ping is all that is necessary to test resolution. This is not necessarily about your DNS servers, but is about DNS resolution by the client. Given that ping is failing to retrieve an IP address, you need to look at the configuration of the client and other "things" in between the client and the DNS server.If you do an ipconfig /all on the destination system (while in PE of course), what DNS servers are configured? Are they correct for your environment?The guidance put forth above by Mike (above)is not about having SPT enabled or not, itsabout enabling portfast if SPT is enabled. Thus, is portfast enabled on the switch port(s) that you are using?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

November 24th, 2009 9:34am

Hi, Yes, portfast is enabled. Anyway I found out that if the PC same network segment with SCCM server, then it can deploy the OS successfully. If the PC sits in different segment with SCCM server, then it failed with this error. But the OS was deployed successfully before.

Free Windows Admin Tool Kit Click here and download it now

November 24th, 2009 11:04am

Hi all, Thank you very much on all the replies! Finally I found out the root cause, it was somebody have restrict the source port from client to go DNS server, that's why it cannot resolve the name.

November 24th, 2009 2:37pm

glad to hear it's resolved and glad to hear that it was indeed a DNS issue.my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

Free Windows Admin Tool Kit Click here and download it now

November 24th, 2009 2:52pm

Hi, Is there any way to check whether the port is open or not after getting into command prompt of winpe as I am also getting same message in smsts.log Please find a message from smsts.log ) Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 28/06/2011 14:19:12 1200 (0x04B0) unknown host (gethostbyname failed) TSPxe 28/06/2011 14:19:12 1200 (0x04B0) hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 28/06/2011 14:19:12 1200 (0x04B0) sending with winhttp failed; 80072ee7 TSPxe 28/06/2011 14:19:12 1200 (0x04B0) Will retry in 4 second(s) TSPxe 28/06/2011 14:19:12 1200 (0x04B0) Retrying... TSPxe 28/06/2011 14:19:17 1200 (0x04B0) CLibSMSMessageWinHttpTransport::Send: URL: lcsccm02p.thelondonclinic.com:80 CCM_POST /ccm_system/request TSPxe 28/06/2011 14:19:17 1200 (0x04B0) Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 28/06/2011 14:19:17 1200 (0x04B0) unknown host (gethostbyname failed) TSPxe 28/06/2011 14:19:17 1200 (0x04B0) hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 28/06/2011 14:19:17 1200 (0x04B0) sending with winhttp failed; 80072ee7 TSPxe 28/06/2011 14:19:17 1200 (0x04B0) Will retry in 10 second(s) TSPxe 28/06/2011 14:19:17 1200 (0x04B0) Retrying... TSPxe 28/06/2011 14:19:28 1200 (0x04B0) CLibSMSMessageWinHttpTransport::Send: URL: lcsccm02p.thelondonclinic.com:80 CCM_POST /ccm_system/request TSPxe 28/06/2011 14:19:28 1200 (0x04B0) Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 28/06/2011 14:19:28 1200 (0x04B0) unknown host (gethostbyname failed) TSPxe 28/06/2011 14:19:28 1200 (0x04B0) hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 28/06/2011 14:19:28 1200 (0x04B0) sending with winhttp failed; 80072ee7 TSPxe 28/06/2011 14:19:28 1200 (0x04B0) Will retry in 22 second(s) TSPxe 28/06/2011 14:19:28 1200 (0x04B0) Retrying... TSPxe 28/06/2011 14:19:50 1200 (0x04B0) CLibSMSMessageWinHttpTransport::Send: URL: lcsccm02p.thelondonclinic.com:80 CCM_POST /ccm_system/request TSPxe 28/06/2011 14:19:50 1200 (0x04B0) Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 28/06/2011 14:19:50 1200 (0x04B0) unknown host (gethostbyname failed) TSPxe 28/06/2011 14:19:50 1200 (0x04B0) hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 28/06/2011 14:19:50 1200 (0x04B0) sending with winhttp failed; 80072ee7 TSPxe 28/06/2011 14:19:50 1200 (0x04B0) Will retry in 44 second(s) TSPxe 28/06/2011 14:19:50 1200 (0x04B0) Retrying... TSPxe 28/06/2011 14:20:35 1200 (0x04B0) CLibSMSMessageWinHttpTransport::Send: URL: lcsccm02p.thelondonclinic.com:80 CCM_POST /ccm_system/request TSPxe 28/06/2011 14:20:35 1200 (0x04B0) Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 28/06/2011 14:20:35 1200 (0x04B0) unknown host (gethostbyname failed) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) sending with winhttp failed; 80072ee7 TSPxe 28/06/2011 14:20:35 1200 (0x04B0) End of retries TSPxe 28/06/2011 14:20:35 1200 (0x04B0) Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) failed to send the request TSPxe 28/06/2011 14:20:35 1200 (0x04B0) DoRequest (sReply, true), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,5010) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) Failed to get client identity (80072ee7) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) ClientIdentity.RequestClientIdentity (), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,815) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) failed to request for client TSPxe 28/06/2011 14:20:35 1200 (0x04B0) Exiting TSMediaWizardControl::GetPolicy. TSPxe 28/06/2011 14:20:35 1200 (0x04B0) GetPolicy(), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2072) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) RunWizardForPXE(), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2402) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106) TSPxe 28/06/2011 14:20:35 1200 (0x04B0) Exiting with return code 0x80072EE7 TSPxe 28/06/2011 14:20:35 1200 (0x04B0) Execution complete. TSBootShell 28/06/2011 14:20:35 792 (0x0318) Finalizing logging from process 756 TSBootShell 28/06/2011 14:20:35 792 (0x0318) Finalizing logs to root of first available drive TSBootShell 28/06/2011 14:20:35 792 (0x0318) LOGGING: Setting log directory to "X:\SMSTSLog". TSBootShell 28/06/2011 14:20:35 792 (0x0318)

June 28th, 2011 9:55am

This topic is archived. No further replies will be accepted.