首页
学习
活动
专区
圈层
工具
发布
首页
学习
活动
专区
圈层
工具
MCP广场
社区首页 >问答首页 >WDS 2008 R2 DHCP错误

WDS 2008 R2 DHCP错误
EN

Server Fault用户
提问于 2011-04-12 07:22:02
回答 1查看 3.5K关注 0票数 0

在从DHCP服务器获取IP地址时,我遇到了错误‘。请检查从从Windows7dvd获取的标准WDS boot.wim映像启动时,这个网络段上是否有一个可操作的DHCP服务器。

我使用的是服务器2008 R2,并且使用WDS将驱动程序添加到引导中,但如果驱动程序事先使用DISM注入,也会出现问题。

当错误发生时,我可以转移+ F10和IPCONFIG,并看到它已经从DHCP获取了内部IP。似乎是在它得到IP之前就已经超时了?DHCP服务器不在WDS框上,而是在同一子网中。

根据我读过的一些修复程序,我在交换机上启用了RSTP,但这没有帮助。

我加入了setupact.log的末尾,看看你们中是否有人有任何想法。似乎失败了,但正如我所说的,网络是初始化的,因为我可以看到DHCP在运行IPCONFIG时分配的内部IP。

我不认为有什么办法可以增加超时时间?

谢谢。

代码语言:javascript
运行
复制
2011-04-11 17:26:31, Info       [0x0b0022] WDS    StartNetworking: Trying to start networking.
2011-04-11 17:26:31, Info                  WDS    Network service dhcp not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lmhosts not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lanmanworkstation not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service bfe not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service ikeext not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service mpssvc not running or could not be queried: 264e18 1 1
2011-04-11 17:27:24, Info                  WDS    Installing device pci\ven_14e4&dev_1691&subsys_04aa1028 X:\WINDOWS\INF\oem37.inf succeeded
2011-04-11 17:27:25, Info                  WDS    No computer name specified, generating a random name.
2011-04-11 17:27:25, Info                  WDS    Renaming computer to MININT-VN2P876.
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Service winmgmt disable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt stop: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt enable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Released profiling mutex
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Install MS_MSCLIENT: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_NETBIOS: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_SMB: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_TCPIP6: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Install MS_TCPIP: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Service dhcp start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service lmhosts start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service ikeext start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service mpssvc start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Released profiling mutex
2011-04-11 17:27:26, Info                  WDS    Spent 967ms installing network components
2011-04-11 17:27:28, Info                  WDS    Spent 2247ms installing network drivers
2011-04-11 17:27:38, Info                  WDS    QueryAdapterStatus: no operational adapters found.
2011-04-11 17:27:38, Info                  WDS    Spent 10140ms confirming network initialization; status 0x80004005
2011-04-11 17:27:38, Info                  WDS    WaitForNetworkToInitialize failed; ignoring error
2011-04-11 17:27:38, Info                  WDS    GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:   
2011-04-11 17:27:38, Error      [0x0b003f] WDS    StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-11 17:27:38, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment.]
EN

回答 1

Server Fault用户

回答已采纳

发布于 2011-06-13 14:05:30

不是一个完美的答案,但可能会帮助其他人。

  1. 挂载boot.wim文件的索引2。
  2. 在图像的根目录中将setup.exe重命名为setupx.exe。
  3. 在挂载图像中编辑\windows\system32\startnet.cmd

@echo关闭

代码语言:javascript
运行
复制
@echo Loading WinPE...
wpeinit

@echo Starting networking...
:testagain
ping -n 1 SERVERNAME > NUL
if %errorlevel% == 0 goto pingok
REM wait 3 sec. and try it again
ping -n 3 127.0.0.1 >nul
goto testagain
:pingok

@echo Running Setup...
x:\setupx.exe /wds /wdsdiscover /wdsserver:SERVERNAME
  1. 保存和卸载索引2并添加到WDS中。

在我看来,这是一个黑客,不应该被要求。肯定有一个原因,网络是这么长时间来削弱,但这将是暂时的。

我很想知道是否还有其他人有更优雅的解决方案。

票数 1
EN
页面原文内容由Server Fault提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://serverfault.com/questions/258631

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档