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

network listing

Dear Sirs

We have a windows 2003 domain with around 40 client pcs,   The domain controller and the other servers are in one vlan and the client computers are in a seperate vlan, Now my problem is that when i browse through my network places from server vlan i am only able to view the servers,  no clients are listed there , but in client vlan am able to view all machines including servers.. ..how to solve this problem. ..coz i want to see the clients from server vlan to install some softwares..pls help

thnks
0
silvershare
Asked:
silvershare
  • 5
  • 3
  • 2
  • +1
1 Solution
 
f_umarCommented:
can u ping a client computer?
did you try to search it using search in windows 2003, open search click on other search options then select printers and computers then a computer on the network.

setup a vlan which includes all ports.
0
 
silvershareAuthor Commented:
yeah i can ping..and i can search..but when i browse thru my network places..its not listing..so i am not able to manage these clients from some softwares..
0
 
f_umarCommented:
check these settings
Control Panel / [Network and Internet Connections] / Network Connections.

02. Right-click Local Area Connection and press Properties.

03. Select Internet Protocol (TCP/IP) and press Properties.

04. On the General tab, press Advanced.

05. On the WINS tab, check Enable NetBIOS over TCP/IP and press OK.

06. Press OK and Close.

07. Right-click My Computer and press Manage.

08. Expand Services and Applications.

09. If the Computer Browser service is NOT started, right-click Computer Browser and press Start. Right-click Computer Browser and press Properties. Set Startup type to Automatic and press Apply and OK.

0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
silvershareAuthor Commented:
i have already did this....
0
 
f_umarCommented:
can u configure a vlan which actually contains your existing vlans. or is there some configuration which blocks netbios packets.
0
 
silvershareAuthor Commented:
This is the problem with me now..the network guys telling me that there is nothing fishy on th vlan.its u r microsoft problem..and i am not able to prove them..as i dont know about vlans
0
 
f_umarCommented:
A VLAN is a group of devices on one or more LANs that are configured to communicate as if they were attached to the same wire, when in fact they are located on a number of different LAN segments. Because VLANs are based on logical instead of physical connections, they are extremely flexible. Multiple VLAN's can reside on a single piece of Ethernet cable. This allows for multiple networks to coexist with minimal infrastructure.

VLANs define broadcast domains in a Layer 2 network. Traffic cannot pass directly to another VLAN within the switch or between two switches. To interconnect two different VLANs, you must use routers or Layer 3 switches.

i suggest u to configure the VLAN which includes clients and server ports

see the following for VLAN
http://www.cse.wustl.edu/~jain/cis788-97/ftp/virtual_lans/index.htm
0
 
MitchV85Commented:
If you want to get around the restrictions of broadcast domain boundries (seperate VLANs) limiting your NetBIOS browsing traffic install WINS on each subnet and let it replicatie all of the WINS records of the hosts on each network. This will solve your problem.

Mitch
0
 
adamdrayerCommented:
Browsing across subnets used to require WINS...  not to plug my own stuff, but if you would like to read a semi-technical description of how it all comes together, you can read http://65.24.134.81/KipSolutions/NetBios/netbios.htm which is a syndicated version of an article that appeared in the EE newsletter and is hosted by a friend of mine, Fatal Exception.  The rest of his site is awesome too.

But, back to the question.  I believe that you should be able to browse an active directory domain without WINS or NetBIOS because Active Directory should publish all the computers on the domain.  Are you going through "my Network Places" -> "Entire Network" -> "Domain Name" ?
0
 
adamdrayerCommented:
Nope.  It seems you still need netBIOS and WINS.  MitchV85 is correct.  Although you only need to install WINS on one server (preferrably the PDC) and point only the master browser to it.  Since the master browsers may change, its a good idea to point all the computer on all subnets to the same WINS server.
0
 
f_umarCommented:
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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