newpersn Posted June 28, 2017 Posted June 28, 2017 I got a problem with our WDS server. Its not letting me do anything. I hit F12 to network boot. Computers get a IP address. They cant contract the WDS Server. I've checked all the DHCP options and they look fine. Any where else I need to check? I had to move the Server to another host (if you need that extra bit of info) IP Address hasn't changed.
Roopert Posted June 28, 2017 Posted June 28, 2017 It is likely to have a dns entry that will need configuring - check it is correct. Also DHCP option 66 - i presume you mean this anyway should point to WDS server. Also ensure client and server are on same subnet / not crossing routers etc.
newpersn Posted June 28, 2017 Author Posted June 28, 2017 It is likely to have a dns entry that will need configuring - check it is correct. Also DHCP option 66 - i presume you mean this anyway should point to WDS server. Also ensure client and server are on same subnet / not crossing routers etc. Nothing has changed. 66 is IP of the server and 67 is the "boot\x86\wdsnbp.com"
DJ-1701 Posted June 28, 2017 Posted June 28, 2017 What version of Windows Server is it installed on, and is it hosting DHCP? Has the Windows Deployment Service Server been disabled on the old server and restarted on the new one?
newpersn Posted June 28, 2017 Author Posted June 28, 2017 What version of Windows Server is it installed on, and is it hosting DHCP? Has the Windows Deployment Service Server been disabled on the old server and restarted on the new one? Same server. Different host. Server 2012 r2 with mdt installed.
eddyc Posted June 28, 2017 Posted June 28, 2017 Have you tried cycling the WDS services on your WDS server? Looks like server isn't listening
LytchettNM Posted June 28, 2017 Posted June 28, 2017 As I'm sure you have realised this picture show the client trying to PXE boot from 172.18.32.31 using it gateway of 172.18.35.1 so the client and server are on different subnets, and that the server has not replied. If you have a route from the server subnet to the client subnet then the issue is with the server at 172.18.32.31, if you have moved / setup a new WDS service have you enabled PXE and added a boot image?
newpersn Posted June 29, 2017 Author Posted June 29, 2017 Have you tried cycling the WDS services on your WDS server? Looks like server isn't listening Restarted the services and still no luck. As I'm sure you have realised this picture show the client trying to PXE boot from 172.18.32.31 using it gateway of 172.18.35.1 so the client and server are on different subnets, and that the server has not replied. If you have a route from the server subnet to the client subnet then the issue is with the server at 172.18.32.31, if you have moved / setup a new WDS service have you enabled PXE and added a boot image? Yep. I only moved the virtual server to a different host. The server still in tract. This worked fine last week before we was hit by ramsomware.
LytchettNM Posted June 29, 2017 Posted June 29, 2017 I would try plugging a PC in on the server network (same subnet) and try to PXE from there to check if the WDS server is responding. Was the WDS server effected by ransomware? Have you got a backup of the WDS server? Why did you need to move to another host?
newpersn Posted June 29, 2017 Author Posted June 29, 2017 I would try plugging a PC in on the server network (same subnet) and try to PXE from there to check if the WDS server is responding. Was the WDS server effected by ransomware? Have you got a backup of the WDS server? Why did you need to move to another host? It's clean. Been scanned and checked. Just need to change the mdt user name and password as all passwords have been reset.
newpersn Posted June 29, 2017 Author Posted June 29, 2017 It's clean. Been scanned and checked. Just need to change the mdt user name and password as all passwords have been reset. [ATTACH]44219[/ATTACH] Anyone know where I can find it. Minds gone blank....
SHimmer45 Posted June 29, 2017 Posted June 29, 2017 the username and password for accessing the MDT share can be anything which has access to the share - if you are automating the connection to the deployment share remove that bit and attempt to do it manually (its the 1st part of the wizard when it boots MDT) check to make sure you can ping the IP and hostname of the MDT server just in case there is anything funny going on
sted Posted June 29, 2017 Posted June 29, 2017 Anyone know where I can find it. Minds gone blank.... the password its in deploymentshare\control bootstrap.ini and customsettings.ini if you change bootstrap.ini you will need to rebuild/reimport to wds your wim file for it to take effect 1
NB9457 Posted June 29, 2017 Posted June 29, 2017 May not be a proper solution, but given you're using a VM, is it not just easier to get a blank copy of Win Server and start again? I did this when ours went pear shaped, only took me an hour to install the Server, WDS and MDT and then I just copied the drivers and images over onto the new share and imported them to MDT. Again, I know it's not a proper fix, but it is a solution and in the long run, could work out quicker for you?
newpersn Posted June 29, 2017 Author Posted June 29, 2017 May not be a proper solution, but given you're using a VM, is it not just easier to get a blank copy of Win Server and start again? I did this when ours went pear shaped, only took me an hour to install the Server, WDS and MDT and then I just copied the drivers and images over onto the new share and imported them to MDT. Again, I know it's not a proper fix, but it is a solution and in the long run, could work out quicker for you? Fixed it. It was permissions disappeared from the folders. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now