Client receiving old data from DHCP/DNS/DC?

[Atomic12]

Hi,

 

I had to open this topic because my solution to my topic does not work.

http://www.windows-noob.com/forums/index.php?/topic/11284-mdt-2013-udi-wizard-domain-join-not-working/

 

The problem is that clients join and not join the domain, it is different result every time.

My first question is from where does the client get the info that is included in netsetup.log from Windows\debug?

Please see attachment NetSetup Bad.LOG

Here you can see that it always pulls some infor from the 31.08.14 but today we are at 24.09.14. and it pulls the CLIENT 02 name even if I give it another name in UDI wizard.

 

This is how netsetup.log look like when it works, when it works and that is every 2nd or 3rd try or better to say random. See attachment NetSetup Good.LOG

I always get the old entry.

 

What I have tried:

1. New boot image.

2. Check network drivers.

3. New TS

4. My college who is a main system engineer had a look at the dhcp/dns setting and could not find anything unusal.

5. Bios time on VM is up to date, DC, DB and SCCM as well. Is there some different time section that i should check?

 

Another interesting thing is the lease obtained on the client while in Windows PE:

 

1878? Really?

 

 

Other info:

DNS:

DNS Dynamic updates: secure and nonsecure.

Refresh interval: 15min

Retry: 10min

Expires after: 1 hour? Changed this one is it too short?

Enable round robin/Enable netmask ordering checked

 

DHCP:

Always dynamically update DNS Records

Discard A and PTR records when lease is deleted

 

DHCP Scope options:

Always dynamically update DNS Records

Discard A and PTR records when lease is deleted

Dyn. update DNS recored for DHCP licent that do not request updates

Lease duration: 4 hours

 

Any help appreciated!

 

 

[Atomic12]

Anybody(web)?

[anyweb]

if netsetup.log is not updating then i'd suggest it fails before trying to join the domain, does the smsts.log hint at that ?

 

i've seen the 1878 year before and laughed, can't recall the reason, but it's probably a bug.

[Atomic12]

Hi,

 

thanks for answering, well to be true lots of things are not going for me (apps not installing, dommain join, frontend...) and i am thinking of starting over with the whole lab setup.

But I will give my self one more shot after you try to read out something smart from smsts-20140924-170205.log

 

 

Cheers,

[Atomic12]

I have started with complete new lab setup as I could not find a solution for this problem.

[anyweb]

ok good luck with this one

[Atomic12]

2nd setup, again same error, starting to think that the error comes from VMware workstation...will post results but i think i will be switching to hyper-v...

 

Edit:

 

Solution FOUND!

 

I am using VMware Workstation 10 as my virtualization solution and I have discovered that during boot into winPE my ip address is always bellow 192.168.123.200 range that i have manually setup on my DHCP server. I would always get .130 or .131 which is not normal, then when I did the WHOLE lab setup 2nd time and failed again after installing MDT 2013 I said to myself it must me VMware Workstation causing the problem. So I went to VMware workstation "Edit" menu and then "Virtual network editor" only to find that Workstation was acting as DHCP server and leasing IP addresses to my test VM!!!!!!!!!!!!!!!!! Horrible!

 

 

When I removed the checkmark from "Use DHCP service to distribute IP address to VMs" everything started working like described in Anyweb's valuable tutorials.

 

How many hours of troubleshooting, google-ing did I spent, I think I got gray hair but I found the solution and that is what matters.