I have just installed WDS on a Windows 2008 server. I'm having a timeout problem when the PXE clients try to tftp the boot images. I have tested this with a tftp command from the command prompt on my workstation, and I get the same results.
The ftpcconnect function starts the FTP client on the TCPnet system. This causes the FTP client to then start a FTP session by connecting to a FTP server on the TCP port specified in the function argument. If the port is not specified, that is the argument port has a value of 0, the system uses a standard FTP server port to connect to. The argument ipadr points to an array of 4 bytes.
If I run the following command:tftp -i wds get bootx86pxeboot.comIt sits for 30 seconds, and then returns:Timeout occurredConnect request failedSo my initial thought was that it was a network issue, firewall, etc. However, my workstation and the WDS server are on the same subnet, and Windows Firewall is disabled, so that's not the issue.
Doing a netstat on the server, I see it listening on UDP ports 67-69. I also see this in the WDS logs:The Following Client failed TFTP Download:IP: 172.20.12.30Filename: bootx86pxeboot.comErrorCode: 1460So the tftp clients are connecting, but they are having troubles actually downloading files. Any ideas here?
I saw a Microsoft KB about the 2008 version of WDS increasing the tftp block size from 512 bytes up to about 1400 bytes, and this could cause problems on some networks. However, could this still be an issue in my case where there is no router or firewall between the machines? There may not be router and firewalls between machines but there are network switches.This issue can occur because Windows Server 2008 and Windows Server 2008 R2 increased the TFTP block size from 512 bytes to 1,456 bytes.
Because of this increase in TFTP block size, WDS cannot perform an operating system deployment over a network that has a TFTP block size of less than 1,456 bytes.you need to install a hotfix, and then you can change the packet size in the registry, see Microsoft Technet Article, if you've not already read it.Good Luck. I'm opening a ticket now to get that hotfix. I have a bit of further information, too. Further testing has revealed that the built-in tftp client in Windows 7 does not work (both 32 and 64 bit), while the Windows XP client does work. I also tried a 3rd party tftp client and it does work.So this is apparently not a network issue, since.some. clients work and some don't.
It's possible the Windows 7 tftp client along with my motherboard's PXE TFTP client don't support the block size that WDS uses. So, maybe that hotfix will do the trick. I'll get it applied and see what happens. I finally got the hotfix from Microsoft. (Took a long time!) Unfortunately, it did not fix the issue. I applied the hotfix, set the necessary registry setting to use 512 byte blocks, and rebooted the WDS server. I'm still having the same problems.
Our PXE boot clients on our workstations try to connect and immediately get an Access Violation error, while our Windows 7 tftp clients timeout with the error I posted in my original post. Our Windows XP and 3rd party tftp clients, however, still work fine. Very strange. Interesting info. After applying the hotfix and setting the block size to 512, our PXE clients are actually getting the files from WDS successfully. Sorry about the confusions in my last couple of posts.
However, the Windows 7 tftp client still isn't working. That would suggest some bug or problem in the Win7 tftp client.So anyway, the PXE clients are getting the files now, so we can probably call this issue closed. That being said, I still can't make the machines boot from PXE, even though they are downloading the wdsnbp.com file and then the pxeboot.com file. They download the files, and then do nothing. But I guess that's a different issue.:).
HI- Sorry if this doesn't belong here but I can't find where else to put this issue.I have Windows Server 2008 R2 Enterprise box. I want it to host an TFTP server. I installed OpenTFTP. On my workstation (8.1 enterprise) I added the TFTP client.
When I try to connect to my TFTP server, I get the following:.C:Windowssystem32tftp 10.0.0.24 GET test.txt c:tempError on server:?????????????ss (x86)Microsoft SQL Server110ToolsBinnManagementStudio;c:Program Files (x86)Microsoft QL Server110ToolsBinn;c:Program FilesMicrosoft SQL Server110ToolsBinn;c:Program Files (x86)Microsoft SQL Server110DTSBinn;C:ProgramFiles (x86)SkypePhone;Connect request failed.First, why would it even list SQL Server paths? And why no connection? Both workstation and server are on the same subnets; firewalls are turned off.ThanxYou should never, never doubt what nobody is sure about.Willy Wonka. Hi,You have mentioned “OpenTFTP”, if it is a 3rd party software instead of Microsoft product, I would recommend you to contact the software’s supporter/developer for official support.Besides, the TFTP client is an optional software, and marked as deprecated on Windows Vista and later versions of the Windows operating system.As Microsoft server system, WDS includes a simple TFTP server, but it's hosted in the same svchost.exe process as the rest of WDS, and there is no separate service listed for TFTP. It only supports read operations, and not write operations.Detailed configuration steps you may reference link below:Best Regards,Eve WangPlease remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Support, contact [email protected]. Also, TFTP server in above scenario was set to 'run as service'. Changed to standalone so I could see real-time. Shows this:starting TFTP.alias / is mapped to D:TFTPHomeDirpermitted clients: 10.0.0.1-10.255.255.254server port range: allmax blksize: 65464default blksize: 512default timeout: 3file read allowed: Yesfile create allowed: Yesfile overwrite allowed: Yesthread pool size: 1Listening On: 10.0.0.24:69Client 10.0.9 D:TFTPHomeDirtest.txt, File not found or No AccessClient 10.0.9 D:TFTPHomeDirtest.txt, File not found or No AccessYou should never, never doubt what nobody is sure about.Willy Wonka. Hi,You have mentioned “OpenTFTP”, if it is a 3rd party software instead of Microsoft product, I would recommend you to contact the software’s supporter/developer for official support.Besides, the TFTP client is an optional software, and marked as deprecated on Windows Vista and later versions of the Windows operating system.As Microsoft server system, WDS includes a simple TFTP server, but it's hosted in the same svchost.exe process as the rest of WDS, and there is no separate service listed for TFTP. It only supports read operations, and not write operations.Detailed configuration steps you may reference link below:Best Regards,Eve WangPlease remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Support, contact [email protected].
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |