[c-nsp] find window's machine from Cisco Router

John P. Schneider johnps at IowaTelecom.com
Fri Feb 5 09:36:27 EST 2010


Maybe I'm over simplifying this but can't you just compare the MAC addresses? If you only have 7 machines it would not take very long. 


Thank You,
John Schneider

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of vijay gore
Sent: Friday, February 05, 2010 4:39 AM
To: Brian Turnbow
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] find window's machine from Cisco Router

No sir.

it's not working,

 actually sir, in this router there are 7 PC's connected, some PC having Linux OS & some PC's having Windows OS, now i want to know which machine having Linux OS & which machine having Windows OS.

please help me out this sir
On Fri, Feb 5, 2010 at 3:57 PM, Brian Turnbow <b.turnbow at twt.it> wrote:

>  it looks like you have loggin enabled for warings only
>
> try
> logging buffered debugging
>
>
> another alternative if the first does not log, is to do a debug ip 
> packet using an access list that matches only netbios.
> this could be more processor intensive.....
> first create
> access-list 102 permit udp any any range 137 138 then debug ip packet 
> 102 when done don't forget undebug all
>
>
>
>
> Brian
>
> ------------------------------
>  *From:* vijay gore [mailto:vijaygore27 at gmail.com]
> *Sent:* venerdì 5 febbraio 2010 10.57
> *To:* Brian Turnbow
>
> *Cc:* cisco-nsp at puck.nether.net
> *Subject:* Re: [c-nsp] find window's machine from Cisco Router
>
>    Dear Sir,
>
>
>
> it's giving me below output, it's not showing net bios packet users,
>
> Router#sho log
> Syslog logging: enabled (1 messages dropped, 0 messages rate-limited,
>                 0 flushes, 0 overruns, xml disabled, filtering disabled)
> No Active Message Discriminator.
>
> No Inactive Message Discriminator.
>
>     Console logging: level debugging, 40 messages logged, xml disabled,
>                      filtering disabled
>     Monitor logging: level debugging, 0 messages logged, xml disabled,
>                      filtering disabled
>     Buffer logging:  level warnings, 10 messages logged, xml disabled,
>                      filtering disabled
>     Logging Exception size (4096 bytes)
>     Count and timestamp logging messages: disabled
>     Persistent logging: disabled
> No active filter modules.
> ESM: 0 messages dropped
>     Trap logging: level informational, 43 message lines logged
> Log Buffer (51200 bytes):
> *Oct  1 15:38:06.639: %LINK-3-UPDOWN: Interface FastEthernet0, changed
> state to
> up
> *Oct  1 15:38:06.639: %LINK-3-UPDOWN: Interface FastEthernet1, changed
> state to
> up
> *Oct  1 15:38:12.823: %LINK-3-UPDOWN: Interface FastEthernet9, changed
> state to
> up
> *Oct  1 15:38:12.827: %LINK-3-UPDOWN: Interface FastEthernet8, changed
> state to
> up
> *Oct  1 15:38:12.827: %LINK-3-UPDOWN: Interface FastEthernet7, changed
> state to
> up
> *Oct  1 15:38:12.827: %LINK-3-UPDOWN: Interface FastEthernet6, changed
> state to
> up
> *Oct  1 15:38:12.831: %LINK-3-UPDOWN: Interface FastEthernet5, changed
> state to
> up
> *Oct  1 15:38:12.831: %LINK-3-UPDOWN: Interface FastEthernet4, changed
> state to
> up
> *Oct  1 15:38:12.831: %LINK-3-UPDOWN: Interface FastEthernet3, changed
> state to
> up
> *Oct  1 15:38:12.831: %LINK-3-UPDOWN: Interface FastEthernet2, changed
> state to
> up
>
>
>
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


More information about the cisco-nsp mailing list