Network Discovery
Last month we replaced our old 2003 domain controllers with 2008 domain controllers. The process went smoothly.
Preped domain for 2008,
DCPromo'd new DC's
Moved FSMO Roles and time server.
Demoted old DC's
And ran clean DCDAIG's during and after procedure.
Now everything is working fine except when you view the network, only LAN computers show up.
Previously, all domain computers were shown when you browse the network.
We have several remote offices connected by VPN's.
Those remote computers all log in normally, and are available from the LAN via \\computername.... but no longer show up when you browse the network.
All computers are windows 7
Preped domain for 2008,
DCPromo'd new DC's
Moved FSMO Roles and time server.
Demoted old DC's
And ran clean DCDAIG's during and after procedure.
Now everything is working fine except when you view the network, only LAN computers show up.
Previously, all domain computers were shown when you browse the network.
We have several remote offices connected by VPN's.
Those remote computers all log in normally, and are available from the LAN via \\computername.... but no longer show up when you browse the network.
All computers are windows 7
ASKER
The original 2003 server at the main LAN may have had WINS turned on. I will add WINS to the new server and see.
It worked before with a server at only the main location (not a server at each office), so maybe it will now.
I presumed that the computers being registered in DNS would have been sufficient to see them listed when you browse the domain, but obviously that was wrong.
It worked before with a server at only the main location (not a server at each office), so maybe it will now.
I presumed that the computers being registered in DNS would have been sufficient to see them listed when you browse the domain, but obviously that was wrong.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry it took some time to schedule a reboot of the server.
Installed WINS, and updated the DHCP to include the new service.
Has been several days now.... enough time to ensure most of the computers have been rebooted to get the DHCP update.
No change on the network browsing though.
The only change was replacing the 2003 DC with a 2008 DC.
Thought for sure WINS was the answer :>(
Installed WINS, and updated the DHCP to include the new service.
Has been several days now.... enough time to ensure most of the computers have been rebooted to get the DHCP update.
No change on the network browsing though.
The only change was replacing the 2003 DC with a 2008 DC.
Thought for sure WINS was the answer :>(
ASKER
Well I guess this will remain a mystery.
Thanks RonWill for the information, and the effort. And since you're the only one who responded... you get all the Jelly Beans!
Thanks RonWill for the information, and the effort. And since you're the only one who responded... you get all the Jelly Beans!
ASKER
I give you an A for effort.
Thanks DrPing.
Did all remote clients get the WINS server added to their NIC configurations? Really for WINS to work you need a WINS server at each site with replication between each.
Did all remote clients get the WINS server added to their NIC configurations? Really for WINS to work you need a WINS server at each site with replication between each.
Thus, you need WINS. WINS was enabled by default with 2003 but is not with 2008 or newer. You need a WINS server at each site.