Balack
asked on
Why can't browse the DC on other segment?
This is using MS w2k8 AD domain. The only dc is located at different subnet, separated by firewall. I've set the required ports for client workstation to browse for DC. I've successfully join workstation to the domain, but, after logging in to the windows, in windows explorer, I see nothing. What went wrong? any port(s) need to open?
Matt V
Setup the WINS server role on the DC, and specify the DC IP as the WINS server on the clients. This should resolve your issue.
WINS is an obselete protocol that has been replaced by DNS. I would recommend staying away from WINS if you can.
Can you get good name resolution for your DC from the client? I'm assuming so, or otherwise you couldn't have joined the domain.
Can you browse to the DC via UNC? Type in "\\DCsName" into Start > Run or Windows Explorer. If that works, it's just a browsing issue, if it doesn't you still have CIFS ports blocked on the firewall.
Can you get good name resolution for your DC from the client? I'm assuming so, or otherwise you couldn't have joined the domain.
Can you browse to the DC via UNC? Type in "\\DCsName" into Start > Run or Windows Explorer. If that works, it's just a browsing issue, if it doesn't you still have CIFS ports blocked on the firewall.
devinnoel is mistaken, NetBEUI is deprecated. WINS is how network browsing works now.
WINS is the NetBIOS equivalent of DNS. It allows you to browse by NetBIOS name and have the server resolve that to DNS.
If you use a UNC that does not contain the complete hostname (dc.yourdomain.local) then you need NetBIOS and you will need WINS to route it across subnets.
WINS is the NetBIOS equivalent of DNS. It allows you to browse by NetBIOS name and have the server resolve that to DNS.
If you use a UNC that does not contain the complete hostname (dc.yourdomain.local) then you need NetBIOS and you will need WINS to route it across subnets.
http://en.wikipedia.org/wiki/Windows_Internet_Name_Service
"As of Windows 2000, DNS provides the favored alternative to WINS, as part of Active Directory.[1]
In theory, if DNS is available, WINS is only necessary if pre-Windows 2000 clients or servers need to resolve names. In reality, especially in large enterprise environments, applications such as SMS 2003 with its use of the 1A record, MS SQL Server 2000 for use of named pipes, and Exchange Server 2000 and 2003 both require WINS for full functionality.[2]"
WINS is in fact a dying protocol. It's still included in Windows & 2008R2, but most people expect it to not longer be included in the upcoming Windows 8 release.
As far as using just the hostname in a UNC, Windows automatically trys adding the default domain suffix onto every name it resolves. Run ipconfig /all and look for the line labeled "DNS Suffix Search List. . . . . . :" I haven't run WINS on any of my networks (including a 200,000 node network for the U.S. Army over in the sandbox) in years.
"As of Windows 2000, DNS provides the favored alternative to WINS, as part of Active Directory.[1]
In theory, if DNS is available, WINS is only necessary if pre-Windows 2000 clients or servers need to resolve names. In reality, especially in large enterprise environments, applications such as SMS 2003 with its use of the 1A record, MS SQL Server 2000 for use of named pipes, and Exchange Server 2000 and 2003 both require WINS for full functionality.[2]"
WINS is in fact a dying protocol. It's still included in Windows & 2008R2, but most people expect it to not longer be included in the upcoming Windows 8 release.
As far as using just the hostname in a UNC, Windows automatically trys adding the default domain suffix onto every name it resolves. Run ipconfig /all and look for the line labeled "DNS Suffix Search List. . . . . . :" I haven't run WINS on any of my networks (including a 200,000 node network for the U.S. Army over in the sandbox) in years.
WINS is stilled used a lot WINS is not a protocol it is a service.
I still use WINS in a lot of network since older application still require WINS resolution. For My Network Places to work across subnets WINS is needed since NetBios is not routable
http://www.ditii.com/2008/07/29/windows-server-2008-netbios-browsing-across-subnets-fail-issue/
http://blogs.technet.com/b/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx
I still use WINS in a lot of network since older application still require WINS resolution. For My Network Places to work across subnets WINS is needed since NetBios is not routable
http://www.ditii.com/2008/07/29/windows-server-2008-netbios-browsing-across-subnets-fail-issue/
http://blogs.technet.com/b/networking/archive/2008/07/25/netbios-browsing-across-subnets-may-fail-after-upgrading-to-windows-server-2008.aspx
ASKER
May be I didn't told you guys that this is W2K8 R2 server. Because, I can recall is, w2k8 DC got browsing issue for different subnets. Eventually how that problem got resolved was by disabled computer browser services on DC.
For this case, my W2K8 R2 DC's computer browser service is dsabled. And now is changed to on, and system got rebooted. It looks better now.
On the client workstation on different subnet, I can browse \\DC\shared folders, so it wasn't due to ports not opened.
For this case, my W2K8 R2 DC's computer browser service is dsabled. And now is changed to on, and system got rebooted. It looks better now.
On the client workstation on different subnet, I can browse \\DC\shared folders, so it wasn't due to ports not opened.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
good
I think my link explained of that in detail.