James <(E-Mail Removed)> wrote:
> Sorry for being so vague. I'm just not sure what other info would be
> helpful. Maybe this info would help. I can't browse by server name
> but i can browse by server ip address.
> What else should I look for?
>
> Thanks alot,
If I understand what you're saying, you are not actually ableto *browse*.
You are entering \\servername or \\ipaddress and looking for shares. That
doesn't have anything to do with network browsing (e.g., finding all your
computers/servers in Network Neighborhood, etc).
Browsing requires NetBIOS over TCP/IP (NetBT). It isn't routable. If you
need to browse at all across subnets (and frankly, even if it's on a single
subnet) you must use WINS. If you have multiple DCs, you can install it on
each and set up push/pull partnerships - or you can have all clients point
at a single WINS server in your 'main' or HQ subnet. You can hand out the
WINS server IP via DHCP - and make sure to specify 0x8 for the node type.
Also point all servers at the WINS server in their IP configs.
http://www.microsoft.com/technet/net...fund_ch11.mspx
is a big overview....but WINS is really simple to configure.
I also like to stop/disable the computer browser service on all my
workstations (via group policy) as they don't need it if they have a WINS
server to talk to. Cuts down on network traffic a lot, WINS does.
>
>> James <(E-Mail Removed)> wrote:
>>> Hello,
>>>
>>> I am in a mixed 2000 and 2003 domain. I am not able to browse by UNC
>>> from one subnet to any other subnets in my company. I CAN ping all
>>> locations from the subnet I am having a problem with.
>>> There are alot of Event ID 1925, 1865, 1311, and 1566.
>>> I'm not sure how to verify site connectivity or to ensure that there
>>> is connectivity.
>>> Thanks.
>>
>> Hmm - "browse" and "UNC" are usually not related things. Browsing in
>> a straight TCP/IP environment requires NetBIOS over TCP/IP ...and
>> if you use that, you really want WINS. More info from you might help
>> narrow this down.