by stonefisk <juicy@[EMAIL PROTECTED]
>
Nov 30, 2003 at 10:34 AM
Have not used that tool for a long time.
Seems to me that error would occur if nbname was trying to bind to your
loc=
al
****t 137, which I guess would be it's default.
You will get this error until you bind it to your local IP and assign any
free ****t to it using the switches:
/localip 94.28.80.234 /****t 24=20
Also search this newsgroup as I remember "the pull" doing a write up on
it.
Try something like......
C:\nbname /localip 172.30.1.69 /****t 666 /astat 172.30.1.70 /conflict
Replace "666" with any free ****t on your machine, and "172.30.1.69" with
yo=
ur
IP.
SF<><
"Nguyen Nam" <ntnam01@[EMAIL PROTECTED]
> wrote in message
news:537152e8.0311272322.36ff8e3f@[EMAIL PROTECTED]
> Plese show me how to run it when i receive this error :
> C:\nbname /astat 172.30.1.70 /conflict
> NBName v1.9 - Decodes and displays NetBIOS Name traffic (UDP 137), with
options
> ...
> WinSock v2.0 (v2.2) WinSock 2.0
> WinSock status: Running
> Error 10013 binding to ****t 137 at address 172.30.1.69
>=20
> Thanks !
