reni007 Posted August 14, 2007 Share Posted August 14, 2007 I am having trouble with Windows PE 2004. I created a custom WinPE disk with the network drivers and can connect to the network and lease an IP Address from our DHCP server. Our server is a Small Business Server 2003. The FQDN is Titan-SBS.smallbusiness.localI cannot get past part 4 of the WinPE installation Installing Configuration Set.I have tried putting the server name before the username but this still doesn't seem to work.I can ping the new machine from the server and back again using IP addresses, but I can't ping the server using it's name.Any help would be appreciated.ThanksReni007 Link to comment Share on other sites More sharing options...
Jazkal Posted August 14, 2007 Share Posted August 14, 2007 Is your DHCP server handing out DNS info?On your WInPE build, once you get it loaded and it has an IP, run:ipconfig /allAnd see what it has for DNS. Link to comment Share on other sites More sharing options...
reni007 Posted August 14, 2007 Author Share Posted August 14, 2007 Thanks for the replyThe IPConfig /all gives the IP Adress of the SBS for the DHCP and DNS.The DNS has Host (A) pointing to the SBS for Titan-SBS and the DHCP has DNS pointing to itself.I have tried searching for the OPKTools share over the command prompt and it is giving me a System Error 5, access is denied.It seems like I can get it to find the Small Business Server but now connecting is the problem.Any ideas would be greatThanksReni007 Link to comment Share on other sites More sharing options...
gadget Posted August 14, 2007 Share Posted August 14, 2007 It's not a simple case of user the correct syntax for domain users ie net use t: \\server\share\ password /user:[domain]\username. Link to comment Share on other sites More sharing options...
reni007 Posted August 15, 2007 Author Share Posted August 15, 2007 still doing the same heres my winbom.ini [Version]signature=$CHICAGO$[Factory]Username=\\titan--sbs\OEMPassword="Install"Logfile = a:\winbom.logLogging = YesLogLevel = 2LogPerf = No[ComputerSettings]AuditAdminAutoLogon=YesSourcePath=%windir%[NetCards][WinPE]Restart=RebootLang=ENGSku=pro.sp2ConfigSet=TitanXP32Domain= smallbusiness.localSourceRoot=\\titan--sbs.smallbusiness.local\OPKToolsUsername=\\titan--sbs\OEMPassword="Install"[WinPE.net]StartNet=Yes[DiskConfig]Disk1=Disk1.config[Disk1.config]Size1=*PartitionType1=primaryFileSystem1=ntfsQuickFormat1=yes[OemRunOnce][startMenuMFUlist]Link0=Link1=Link2=anyone any ideas ?? Link to comment Share on other sites More sharing options...
Tripredacus Posted August 15, 2007 Share Posted August 15, 2007 We get this if the NIC uses a different driver than is included in the PE. Link to comment Share on other sites More sharing options...
reni007 Posted August 15, 2007 Author Share Posted August 15, 2007 We get this if the NIC uses a different driver than is included in the PE.ive intergrated the nic (broadcom) into a custom PE build and its detecting the network just failing at step 4 do you have workaround ?? Link to comment Share on other sites More sharing options...
Tripredacus Posted September 14, 2007 Share Posted September 14, 2007 We get this if the NIC uses a different driver than is included in the PE.ive intergrated the nic (broadcom) into a custom PE build and its detecting the network just failing at step 4 do you have workaround ??We get this problem only on about 5% of the machines we set up. In those cases when we have to "work-around" the issue, we put a Kingston NIC in there which uses the ndis driver. Link to comment Share on other sites More sharing options...
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