[wds] ReInstalling wds, the share name is already in use on this server

[denmyos]

I had to reinstall my WDS but when i want to configure it i get a "the share name is already in use on this server"

I try to give the share a different name, but i still get the same error.

 

I tryed this commands

WDSUTIL /uninitialize-server

WDSUTIL /initialize-server /RemInst:E:\NewRemoteInstall

 

But no cigar

 

I'm very close to deleting my whole server MDT/wds and start all over. :(

Edited July 11, 2014 by denmyos

[free780]

Have you tried removing the role and the reminst folder?

[denmyos]

Have you tried removing the role and the reminst folder?

 

 

Thank you, that worked.

I was close to giving up. :S

 

are you hardcore at Vmare.?

 

I need to pxeboot from a real client, into my MDT/WDS server.

I can ping both ways, but when i try to pxe boot my client it just timeout and goes into windows.

 

I can pxe boot all my virtuel clients into the MDT/WDS and get a image, so I know it's working.

[kmount]

Is your real client using the same DHCP server & network subnet(broadcast address) to that of your client / server within the VMware setup?

[denmyos]

Is your real client using the same DHCP server & network subnet(broadcast address) to that of your client / server within the VMware setup?

 

 

yes totally the same.

I checked

And i can ping between the real client and the vmware server and back.

[kmount]

Do you see a DHCP lease be issued for your physical client properly?

 

(on the same DHCP server that issues your vmware pxe client)

[denmyos]

Do you see a DHCP lease be issued for your physical client properly?

 

(on the same DHCP server that issues your vmware pxe client)

 

Not sure how to check that.

 

When i pxe boot my client it boot into dhcp.........

and the goes to .......no file name received..

And the boot into windows.

 

In windows client the ip, subnet, gateway

is the same as my vmware server

 

 

Yes there is a lease being issued on the client.

 

And its the same dchp server for both vmware server and physical client

 

 

BTW: i'm in a workgroup

Edited July 12, 2014 by denmyos

[kmount]

That's why I'm trying to ascertain whether your DHCP server that the physical client is receiving information from is receiving the same information it would have done from the VMware client.

 

If you're certain that the DHCP server, subnet, and DHCP options are identical in both circumstances I wonder if it's having a different problem.

 

Is your WDS server also the DHCP one or is that a separate machine?

[denmyos]

That's why I'm trying to ascertain whether your DHCP server that the physical client is receiving information from is receiving the same information it would have done from the VMware client.

 

If you're certain that the DHCP server, subnet, and DHCP options are identical in both circumstances I wonder if it's having a different problem.

 

Is your WDS server also the DHCP one or is that a separate machine?

 

 

I'm having the MDT and the wds on the same server.

The Dhcp is on a different network/segment, which i have no control off.

[kmount]

OK cool, so DHCP is the common here outside of both of your physical client and VMware environment that's good.

 

Can we confirm conclusively that your VMware PXE client receives the same IP range, netmask, etc as the physical client?

 

Also, is your physical client plugging into the same network port configuration as your VMware one? (same VLAN, same switch, etc)

[denmyos]

OK cool, so DHCP is the common here outside of both of your physical client and VMware environment that's good.

 

yes, Correct

 

 

Can we confirm conclusively that your VMware PXE client receives the same IP range, netmask, etc as the physical client?

 

Yes, correct

 

Also, is your physical client plugging into the same network port configuration as your VMware one? (same VLAN, same switch, etc)

 

Same Vlan

 

But I can't confirmed that its on the same switch.

But my network administrator assured me that I was good to go.

 

 

 

Is there a way to test if the pxe boot actually is trying to reach my wds, and where it gets stopped.?

 

 

When the physical client boots into windows it can share foldes with the MDT/WDS server, so there is some kind of connection.

Edited July 12, 2014 by denmyos

[kmount]

Yep, you could run wireshark on the WDS box and compare the traffic from when the VMware client PXE's and when the physical client does.

[denmyos]

Yep, you could run wireshark on the WDS box and compare the traffic from when the VMware client PXE's and when the physical client does.

 

 

Hi Kmount

 

I will start a seperate thread about this. since it is a big mystery to both me and our network administrator.

 

Thanks you for your help.