iPXE deployment with WDS
|
2013-11-29, 23:40
Post: #6
|
|||
|
|||
RE: iPXE deployment with WDS
It is normal that the iSCSI server reports that the connection is dropped and re-established. This is part of the hand-over from iPXE to Windows. Which is done using the iBFT memory region.
Is WinPE having problems getting an IP if iSCSI is not connected (no sanhook command used)? If so, the iSCSI connection might be causing some form of problem. You might also have the typical routing issue in your network, which can be worked around with set netX/gateway 0.0.0.0 to ensure Windows will connect directly to your iSCSI target instead of going through your router. Obviously you can't do that if your iSCSI client and server are on different subnets. You put it before the sanhook command. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
iPXE deployment with WDS - Draculea - 2013-11-26, 18:35
RE: iPXE deployment with WDS - robinsmidsrod - 2013-11-27, 21:46
RE: iPXE deployment with WDS - Draculea - 2013-11-28, 11:30
RE: iPXE deployment with WDS - Draculea - 2013-11-28, 21:38
RE: iPXE deployment with WDS - Draculea - 2013-11-29, 11:15
RE: iPXE deployment with WDS - robinsmidsrod - 2013-11-29 23:40
RE: iPXE deployment with WDS - Draculea - 2013-11-30, 18:37
RE: iPXE deployment with WDS - robinsmidsrod - 2013-12-04, 18:00
RE: iPXE deployment with WDS - Draculea - 2013-12-04, 22:05
|
User(s) browsing this thread: 1 Guest(s)