Browsing domain net view

[tjbradford]

Hi all,

I have got an issue with a switch on a stick that is not able to browse the whole list of domain PC's only the ones in its own local subnet , other subnets are not affected. the subnet has a mixture of 2k xp 2k3 but all devices are only able to browse there segment.

i suspect it to be the switch config which is as follows


version 12.2
no service pad
service timestamps debug uptime
service timestamps log datetime localtime
service password-encryption
!
hostname sw
!

!

!
aaa session-id common
switch 1 provision ws-c3750-48ts
ip subnet-zero
ip routing
ip domain-name domain

!
!
!
!
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
!
interface FastEthernet1/0/1
switchport access vlan 202
switchport mode access


!
interface FastEthernet1/0/48
switchport access vlan 202
switchport mode access
!
interface GigabitEthernet1/0/1
no switchport
ip address *.*.*.*
!
interface Vlan1
no ip address
!
interface Vlan202
ip address *.*.*.* *.*.*.*
ip helper-address "server-dhcp"
!
router eigrp 1
network *.*.*.*
auto-summary
eigrp stub connected
!
ip classless
ip http server
!
!

!
control-plane
!
!
line con 0
line vty 0 4
password
line vty 5 15
!
ntp clock-period 36029133

!
end


does this config look good or is it missing a command to allow wins lookups?

 

[ADB100]

You need WINS configured on a Windows 2000/2003 server and you clients configured to register with it. Each network/subnet will elect a master browser that should maintain the browse list. This is why you have the behaviour you have at the moment. You need to add WINS and get it working for browsing across routers to work.

http://technet.microsoft.com/en-us/library/bb727015.aspx

Personally I prefer to disable NetBIOS and use AD to publish shares & printers. With NetBIOS disabled there is no browse list at all, however you can still look what shares are available on machines by typing the UNC directly - i.e. \\server10\

Andy

 

[VinceWhirlwind]

The switch is responsible for Layer-2 & Layer-3 connectivity only.

So providing devices can ping each other from one subnet to another, the switch is doing its job - WINS is not in the switch's job description.

 

[ADB100]

- WINS is not in the switch's job description.

I didn't say it was. I said WINS needs configuring on a Windows 2000/2003 Server and clients need to be configured to work with it. The switch is indeed doing its job.

Andy

 

[VinceWhirlwind]

I didn't say you did say it was.

The OP definitely seemed to think there was a connection though, which is where understanding the OSI model could help him.

I get this all the time - applications fail and people say "it's the switch" because they think what goes on below the application layer is all just some sort of black magic.

 

[burtsbees]

You have just defined the difference between a hardware tech and a software/admin (especially Microsoft...lol)...

Burt

 

[VinceWhirlwind]

I did it without being rude, either, pretty good eh?