Ghost Solution Suite

Here's the issue guys.

We have a whole lab dedicated to imaging within the network. We want to seperate it. So we have one server managing the imaging. 3com suggest 2 one for DHCP and 1 for TFTP i know that it can be done without 2 though. This server will be doing PXE, TFTP, AD and DHCP.

Were using Symantec Ghost Soloution Suite 2.5 and 3com boot services to do all this
DHCP is working correctly it seems. Same with the PXE rep we are using with 3com.
Where the issue is lying is with Port 67 which 3coms TFTP services use.

at the client machine which is a Gateway M285-E i get the following

•    PXE Menu Boot File V.1.10
•    Transfering Image File
•    ERROR: TFTP failed opening file

At Server side:

PXE Server recognized client and the TFTP Server starts to try and push the image down to the client but times out.
Again after starting 3com PXE & TFTP server i am supposed to start both of the services in services.msc. PXE works TFTP errors out with a generic error to look at eventvwr
the 3com TFTP Server states the following after i try it without the service started which of course shouldnt work

1/7/10  11:21 AM  TFTP Read C:\TFTPBOOT\mba.pxe from Ip
1/7/10  11:21 AM  TFTP Read C:\TFTPBOOT\mba.pxe from Ip
1/7/10  11:21 AM  TFTP Read C:\TFTPBOOT\mba.pxe from Ip Done
1/7/10  11:21 AM  TFTP Read C:\TFTPBOOT\Standard M285-e.go  from Ip
1/7/10  11:22 AM  TFTP Read C:\TFTPBOOT\ Standard M285-e.go from Ip Done
1/7/10  11:22 AM  TFTP Read C:\TFTPBOOT\mba1.pxe from Ip  TimeOut

What seems to be happening is i try to start the TFTP Service in services.msc and it errors out telling me to view the event log in which it gives me the following issue.
      Source 3ctftps Event ID: 12
     
     Description:

• 3com TFTP Service was unable to start do to error binding windows socket WSAGetLastError() returns 10048

So i started trying to hunt this issue down on google and forums most things point to issues with other TFTP services running, RIS & WDS,  or scope option 60 in DHCP or issues with Port 67, 68 and 4011

So i checked for any services relating to tftp and i pretty much knew before hand there was none on there since it was a clean install with just  Ghost/AD & 3com
Didnt install RIS or WDS
Scope 60 was already checked and ready on our DHCP Scope
so i did a netstat -antb for the ports

• Port 67 was in use by DHCP services

So i went to "C:\Windows\System32\Drivers\etc" and opened up the services file with notepad since it shows what ports are being used and i read in an article that you could change the ports through this file. So i tried to do that by putting a # before the line that the port was being used on. Restart no luck
Tried just changing the digit. Restart no luck.

Im at a loss right now any help would be greatly appreciated.

Z

A couple of things.

TFTP uses port 69 UDP.

DHCP uses port 67 UDP

The two won't conflict.

The 3com boot services are really starting to show their age. The images and image editor are still fantastic but the PXE/TFTP servers are ........well let's just say there are better alternatives out there. Depending on the size of your lab, I would ditch the Windows DHCP and the 3com pxe/tftp in favor of TFTPD32 which can do all of those (unless you need some of the advanced MS features) There are several versions which can be found here: http://tftpd32.jounin.net/tftpd32_download.html

If you do want to keep those applications you can try using only the tftp server in tftpd32 or the solar winds tftp app. Also, when troubleshooting the 3com apps, don't run them as services. Start them as apps and keep an eye on everything - often times you'll see the problem right in front of you. Keep us posted this should be an easy one to figure out.

Cheers.

Have tried it with out going into services.msc and turning it on. Read in an article to start the 3com services. and both ways it errors out with the same error. Got any reading material on how to implement it with Ghost? TFTPD32 seems fairly easy just want to make sure i dont screw it up.

Thanks,
Z

Here's an extremely detailed account for my setup here: https://www-secure.symantec.com/connect/forums/one-pxe-menu-unite-them-all-dos-linux-winpe
It covers the setup for tftpd32. If you wish to keep using the 3com PXE menu then you'll serve out the mba.pxe (that's the default name - yours might be different) instead of pxelinux.0

This guide goes into a little more depth on the TFTPD32 side if you need it. http://www.freewarereview.info/2007-06/tftpd32_for_windows_-_unleash_the_pxe_bios_network_boot_feature_within.html

Cheers.

btw. please mark this as a solution if you get up and running. - thanks.

i need some help setting up the tftpd32 to work with symantec ghostcast server.
any advice will help

thanks