Cannot Authenticate to Server: Incorrect Function

[reni007]

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.local

I 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.

Thanks

Reni007

[Jazkal]

Is your DHCP server handing out DNS info?

On your WInPE build, once you get it loaded and it has an IP, run:

ipconfig /all

And see what it has for DNS.

[reni007]

Thanks for the reply

The 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 great

Thanks

Reni007

[gadget]

It's not a simple case of user the correct syntax for domain users ie net use t: \\server\share\ password /user:[domain]\username.

[reni007]

still doing the same

heres my winbom.ini

[Version]

signature=$CHICAGO$

[Factory]

Username=\\titan--sbs\OEM

Password="Install"

Logfile = a:\winbom.log

Logging = Yes

LogLevel = 2

LogPerf = No

[ComputerSettings]

AuditAdminAutoLogon=Yes

SourcePath=%windir%

[NetCards]

[WinPE]

Restart=Reboot

Lang=ENG

Sku=pro.sp2

ConfigSet=TitanXP32

Domain= smallbusiness.local

SourceRoot=\\titan--sbs.smallbusiness.local\OPKTools

Username=\\titan--sbs\OEM

Password="Install"

[WinPE.net]

StartNet=Yes

[DiskConfig]

Disk1=Disk1.config

[Disk1.config]

Size1=*

PartitionType1=primary

FileSystem1=ntfs

QuickFormat1=yes

[OemRunOnce]

[startMenuMFUlist]

Link0=

Link1=

Link2=

anyone any ideas ??

[Tripredacus]

We get this if the NIC uses a different driver than is included in the PE.

[reni007]

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 ??

[Tripredacus]

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.