We setup a test SCCM2007SP1 server. It was able to do network discovery just fine. That server had a pretty small hard drive and a better server became available so I stood up a new SCCM2007SP1 server on it. It has a different site code than the original SCCM2007 server that we used for testing.
Ever since I set up the new SCCM server, it has only been able to discover itself and the router using Network Discovery. It never sees anything else. I finally added AD discovery and it adds everything it sees in AD.
I've got the network discovery configured exactly the same on the new SCCM as it is configured on the test SCCM server. They are both on the same subnet. All the clients are on the same subnet as the SCCM servers. Site Boundaries were setup the same as well. I deleted the site boundaries on the test SCCM. It's still able to perform network discovery just fine.
On the new SCCM server, it is running Server 2008 Standard. The test server is running Server 2003 Standard. Windows firewall is disabled on both SCCM servers.
Clients are all reporting into the new SCCM server just fine and I'm using the new SCCM server to deploy operating systems and task sequences without any problems and can PXE boot from it.
Looking at the netdisc.log on each server, both have entries that say: "ADM: Using NULL sessions for NTBrowser discovery". I've seen postings that have discoveries of systems in the netdsic.log file but no DDRs are created. But I'm not seeing any entry for discovered systems except itself and the router. On the test server, network discovery runs for several minutes. On the new server, it runs for less than a minute.
Thanks in advance!
Ever since I set up the new SCCM server, it has only been able to discover itself and the router using Network Discovery. It never sees anything else. I finally added AD discovery and it adds everything it sees in AD.
I've got the network discovery configured exactly the same on the new SCCM as it is configured on the test SCCM server. They are both on the same subnet. All the clients are on the same subnet as the SCCM servers. Site Boundaries were setup the same as well. I deleted the site boundaries on the test SCCM. It's still able to perform network discovery just fine.
On the new SCCM server, it is running Server 2008 Standard. The test server is running Server 2003 Standard. Windows firewall is disabled on both SCCM servers.
Clients are all reporting into the new SCCM server just fine and I'm using the new SCCM server to deploy operating systems and task sequences without any problems and can PXE boot from it.
Looking at the netdisc.log on each server, both have entries that say: "ADM: Using NULL sessions for NTBrowser discovery". I've seen postings that have discoveries of systems in the netdsic.log file but no DDRs are created. But I'm not seeing any entry for discovered systems except itself and the router. On the test server, network discovery runs for several minutes. On the new server, it runs for less than a minute.
Thanks in advance!