• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1736
  • Last Modified:

Cannot browse computers on different subnets?

Hello,

I have been setting up a lab where I am experimenting with a WINS server.  Please see diagram below.  My goal is to beable to click on network neighborhood and see all workstations in Subnets A and B
Subnet A Description
Windows 2000 Server   Netbios Name:  Intel01
IP:    192.168.0.2
SNM: 255.255.255.0
DNS: 4.x.x.x
WINS Server: 192.168.5.2  
Workgroup Name: IT


Workstation A
Netbios Name: michaelsroom
IP:    192.168.0.10
SNM: 255.255.255.0
DNS: 4.x.x.x
WINS Server: 192.168.5.2
Workgroup Name: IT

From  Workstation A
I can do the following.  I can browse machines via UNC and via IP on subnets A and B.  

From Workstation A. I cannot browse network neighborhood and see other computers on Subnet B.

My WINS server is located on subnet B

Subnet B Description
Windows 2000 Server   Netbios Name:  IT01
IP:    192.168.5.2
SNM: 255.255.255.0
DNS: 4.x.x.x
WINS Server: 192.168.5.2  
Workgroup Name: IT01

On my Wins server I can see registractions for workstation A and the 2000 server on subnet A.

I have been up here on google for the last 5 hours reading all about browser masters and netbios.  I understand that each workgroup or domain needs to have a master browser.  I believe that the server on subnet A is a browser Master because it is running the Computer Browser Service.  The Wins server is a Master Browser because it says so right in the WINS dialog box  ___MSBROWSE___01H Other.

Also I am running one more server on Subnet A called server2000 wihich is running active directory and the Domain it lives in is called server2000.local.  Does this server cause any issues possibly.  

please let me know if i am missing anything.  Thank you very much for your patience and efforts.
0
stressedout2004
Asked:
stressedout2004
  • 3
  • 2
2 Solutions
 
markgrinceriCommented:
Hi

What are you using to route between the subnets?

The problem you experiencing is due to netbois boadcast not been sent between the subnets, because a router will never send boardcasts unless you tell it to

0
 
Fatal_ExceptionCommented:
Yea..  it appears that you are running 3 different subnets here...  What is your DNS server doing in subnet 4.x.x.x?  And where does your server2000.local lie?  You really need to place everything in the same subnet;  at the very minimum, all the servers:  WINS | DNS | and the DC..  To authenticate between subnets, you must have a DHCP Relay Agent setup..  Only the high end routers will allow you to do this without extra hardware on the subnet..  

FE
0
 
stressedout2004Author Commented:
Im currently using Cisco 2600 Routers  the 4.x.x.x dns points to an external dns server that is private.  I could point dns to my ISP or I can even point all computers dns to the DC in my internal network on subnet B and have the DC do a zone transfer to my ISPs DNS servers.  But right now i dont not have active directory or DNS installed on the 2000 server in Subnet B.  I i only have two subnets whcih are the 192.168.0.0 and 192.168.5.0 networks.

markgrinceri I agree but!!!!
Cisco does make a workaround for admins to forward broadcast traffic between subnets, however I do not want to have broacast traffic being transmitted between subnets.  If we enable broadcast traffic then we dont need a WINS server.

I really do not think that DNS is an issue.  server2000.local lies on subnet A  IP addr.  192.168.0.5
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
markgrinceriCommented:
I agree DNS is not an issue in is problem I feel but that if you don't forward netbios boardcast you wont fix the problem. I can configure the cisco 26xx router using:

conf# interterface ethernet 0
conf-if# ip helper-address x.x.x.x

You need to specify this command on the interfaces which are connected on different segments. the address is the address of the machine you want the boardcast to be sent. By default it forwards 8 different types of boardcast which are:

UDP Port          Name
69                   TFTP
67                   BOOTP Client
68                   BOOTP Server
37                   Time Protocol
49                   TACACS
53                   DNS
137                 NetBios
138                 NetBios Datagram

So if you want to stop the forward of everything except Netbios then issue the command in global config:

conf# no ip forward-protocol udp 69
conf# no ip forward-protocol udp 67
conf# no ip forward-protocol udp 68
conf# no ip forward-protocol udp 37
conf# no ip forward-protocol udp 49
conf# no ip forward-protocol udp 53 <---- I would probably leave this one

This is the only way your problem.
0
 
Fatal_ExceptionCommented:
Yes, I agree!  I came across this article a while back, and liked it so much I bookmarked it!  although it deals primarily with DHCP, with the help of Mark's post, you will get the idea!

Trinity Explains The IP Helper-Address Command

http://www.routergod.com/trinity/

FE
0
 
Fatal_ExceptionCommented:
Thanks..

FE
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now