neotrin2000

For anyone that is still reading this... I have (With the help of Jason from the technet forums) figured out the answer. So here it is. My Server is providing DHCP. I have DHCP turned off on the router. DNS however is being handled by my router. Not sure how to provide DNS services to my network if I point it to my server......EUREKA!!!! As I typed the 2nd Line it was clear to me what was going on...DNS what being handled by my router!!! DUH!!!! So what I did to fix it was 1. Started the DHCP console 2. Expanded the IPv4 tree 3. Highlighted Scope Options 4. On the right pane changed DNS Servers to point to my server rather than my router I feel like such a dunce.

Already did that. This is something I knew from back when I had a server setup the exact same way minus SCCM and just running WDS.

Peter, Thats what someone on the technet site is thinking as well. He suggested setting up a conditional forwarder. Sooo I tried and... In trying to setup a Conditional Forwarder I get 1 of 2 errors 1. IP Address invalid when I use morpheous.zion.com or just plane old Morpheous for the DNS Domain. (Yes I know Morpheous is not a valid FQDN I just tried for troubleshooting purposes) 2. Zone already exists when I just user zion.com for the DNS Domain What information could I provide you or anyone else that wants to help? I would rather not start all over and rebuild this server using a FQDN that is not on the internet already. Incidently I checked all over the place on my DNS Server for any IP address's that are not part of my network. There is only a couple places and they are; 1. DNS Server > Morpheous > Root Hints & Forwarders.. then on the Root Hints Tab there is a.root-servers.net all the way to i.root-servers.net and then on the forwarders tab there is the IP address of cox.net But again, No where on my server do I see a 72.x.x.x IP address. I should note that I have DHCP, DNS, IIS, AD DS, and SCCM all on one server. I know it's not best practice to do this but I do have my reasons for doing it. Again tho the thing that boggles my mind is back in the day I did all this and got WDS to work just fine. The only thing differant now is that I am using SCCM instead of WDS. Otherwise FQDN's, IP, Scopes, ALL is the same as when I was using WDS.

Another thing to note at this point, From the server I cannot ping the PXE Client but again from the client I can ping the server using only the IP address 192.168.1.109 but I cannot ping it using the servers FQDN

OK, So as the title suggests I have SCCM 2012 installed on a fresh install of Server 2k8 R2. I am trying to PXE Boot and it gets as far as "Prepairing network connections" and then reboots. I have searched and searched for this issue both on here and google. I found multiple "possible solutions" and tried everything I found but could not get this to work. 1. I enabled command prompt and I do get an IP Address. 2. I cannot ping morpheous.zion.com (FQDN) which resolves to IP 72.215.225.9 3. I can ping the servers real IP of 192.168.1.109 4. When looking at the smsts.log file though cmtrace the only line highlighed in red says "failed to get information for MP:http://morpheous.zion.com. 80004005" I think this has something to do with the fact that morpheous.zion.com is resolving to 72.215.225.9. I think that because it's not even in the same IP range as the server itself let alone the same subnet. My question is, is it because of the 72.x.x.x IP?? If so how do I change it to be in the same IP range and of course subnet? If this is not the issue can someone tell me the various things I can do to troubleshoot MP Connectivity issues? How can I make sure I have the corrects permissions setup for everything to run flawlessly..ect..ect.. Any help or advice would be greatly appreciated.