Re: view workgroup computers--workaround

From: Terry B. (riprap1951_at_comcast.net)
Date: 10/14/04


Date: 14 Oct 2004 16:59:17 -0700

Chuck <none@example.net> wrote in message news:<q32sm0dektpsogkm4popdlc3lvuq3u8pnb@4ax.com>...
> On 13 Oct 2004 21:29:43 -0700, riprap1951@comcast.net (Terry B.) wrote:
>
> >"Cheer" <Cheer@discussions.microsoft.com> wrote in message news:<99A30343-FC74-4F51-8B79-A95341AFBAD8@microsoft.com>...
> >> do you have norton internet security installed on your computer? cause if you
> >> do, norton is preventing your computer to communicate with other computer.
> >> configure the personal firewall of norton then go to network tab, it will
> >> tell you everything. you have to put your ip ad in the trusted zone. then you
> >> can go from there.
> >> very easy ... that is if you have anorton security installed.
> >
> >TO CHEER:
> > No, there's no Norton products installed. There is Sygate Personal
> >Firewall, but it's configured to accept a network neighborhood, plus
> >I've tried a bunch of times to View Workgroup Computers (from the
> >laptop) w/ the Sygate turned off; no joy.
> >
> >TO CHUCK:
> > I got browstat running. Here's the readout frm the cmd: "browstat
> >status <workgroupname>":
> >
> > Status for domain disgusted on transport
> >\Device\NetBT_Tcpip_{0F5B0BBB-99BB-4A1E-A25D-22718665A05C}
> > Browsing is NOT active on domain.
> > Master name cannot be determined from GetAdapterStatus.
> >
> > (Does that help?)
> >
> > Also, Chuck, I apologize for not noticing this before, but the
> >whole problem w/ not being able to View Workgroup Computers and the
> >application hang seems to be limited to just one of 2 laptops on
> >WLAN--a Dell Inspiron. (There's an Averatec which is sharing just
> >fine.) Also, I've tried 2 different pc cards on the dell; doesn't seem
> >to make any difference. And I've also uninstalled-&-reinstalled the
> >cd-based software that came w/ the cards. No joy.
> >
> > (Does any of this help w/ diagnostics?)
> >
> >Thanks much for your time [:-))
> >
> >Terry B.
>
> Terry,
>
> That's a good start. But just that. If browsing is NOT active on the domain,
> you certainly shouldn't expect to see stuff in Network Neighborhood.
>
> And, if you browse some of my previous posts where a personal firewall is
> involved, you'll notice that, not infrequently, problems ARE NOT resolved by
> turning the damn things off. You have to either properly configure them, or un
> install each completely.
>
> With a problem like yours, we can poke around all month. Or we can get
> organised, carefully define the scope of the problem, and maybe fix it this
> week.
>
> First, we need to know what computers you have on the LAN, with computer name,
> and with OS name, version, and SP level. And which computers have, or had,
> personal firewalls of any brand.
>
> Then run diagnoses on each computer. Starting here.
>
> Please provide ipconfig information for each computer.
> Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
> window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
> Identify operating system (by name and version) with each ipconfig listing. And
> identify any firewalls, both presently active, and previously active.
>
> Provide adhoc browser view for each computer.
> Start - Run - "cmd". Type "net view >c:\netview.txt" into the command window -
> Open c:\netview.txt in Notepad, copy and paste into your next post.
>
> Provide browstat information for each computer.
> Start - Run - "cmd". Type "browstat status >c:\browstat.txt" into the command
> window - Open c:\browstat.txt in Notepad, copy and paste into your next post.
> Identify each computer by name and operating system.
>
> From each computer, test connectivity and name resolution:
> 1) Ping itself by name.
> 2) Ping itself by ip address.
> 3) Ping the other two by name.
> 4) Ping the other by two ip address.
> 5) Ping 127.0.0.1.
> 6) Ping the router.
> Report success / exact error displayed in each test (24 tests total).
>
> This is a start. Once we have a start, we will know what to look at next.
>
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.

TO CHUCK::Here's the data you asked for:

 (3) Computers on the LAN

1.) desktop/host. type = hp 513c
                name = "powertool" .
                   OS name = WinXP Pro v.2002
                SP level = SP2
                Firewalls: At present has Sygate 'personal' installed;
                Windows Firewall/Internet Connection service DISABLED
                

2.) laptop #1: type = dell inspiron 1150
                name = "multitool1"
                OS name = WinXP Pro v.2002
                SP level = SP2
                Firewalls: Had Sygate, but uninstalled;
                Windows Firewall/Internet Connection service DISABLED

3.) laptop #2: type = averatec 3220H1
                name = "veridisk"
                OS name = WinXP Pro v.2002
                SP level = SP2
                Firewalls: None. Windows DISABLED.

1a.) "powertool" ipconfig data:
          Windows IP Configuration

        Host Name . . . . . . . . . . . . : powertool

        Primary Dns Suffix . . . . . . . :

        Node Type . . . . . . . . . . . . : Hybrid

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 6:

        Connection-specific DNS Suffix . :

        Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
Fast Ethernet NIC #2

        Physical Address. . . . . . . . . : 00-40-05-35-E0-8D

        Dhcp Enabled. . . . . . . . . . . : No

        IP Address. . . . . . . . . . . . : 192.168.1.8

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.1.1

        DNS Servers . . . . . . . . . . . : 216.148.227.68

                                            204.127.202.4

                2a.) "multitool1" ipconfig data:
           Windows IP Configuration

        Host Name . . . . . . . . . . . . : multitool1

        Primary Dns Suffix . . . . . . . :

        Node Type . . . . . . . . . . . . : Hybrid

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected

        Description . . . . . . . . . . . : Broadcom 440x 10/100
Integrated Controller

        Physical Address. . . . . . . . . : 00-0F-1F-0D-7D-63

Ethernet adapter Wireless Network Connection 14:

        Connection-specific DNS Suffix . :

        Description . . . . . . . . . . . : Wireless-G Notebook
Adapter v.2.0

        Physical Address. . . . . . . . . : 00-0F-66-A2-45-23

        Dhcp Enabled. . . . . . . . . . . : No

        IP Address. . . . . . . . . . . . : 192.168.1.15

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.1.1

        DNS Servers . . . . . . . . . . . : 216.148.227.168

                                            204.127.202.4

                3a.) "veridisk" ipconfig data":
         Windows IP Configuration

        Host Name . . . . . . . . . . . . : veridisk

        Primary Dns Suffix . . . . . . . :

        Node Type . . . . . . . . . . . . : Hybrid

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Broadcom builtin:

        Connection-specific DNS Suffix . :

        Description . . . . . . . . . . . : Broadcom 802.11g Network
Adapter

        Physical Address. . . . . . . . . : 00-90-4B-6B-7A-31

        Dhcp Enabled. . . . . . . . . . . : No

        IP Address. . . . . . . . . . . . : 192.168.1.13

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.1.1

        DNS Servers . . . . . . . . . . . : 216.148.227.68

                                            204.127.202.4
                
1b.) "powertool" browser view:
                Server Name Remark

-------------------------------------------------------------------------------
\\MULTITOOL1
\\POWERTOOL
\\VERIDISK
The command completed successfully.

2b.) "multitool1" browser view:
                Server Name Remark

-------------------------------------------------------------------------------
\\MULTITOOL1
\\POWERTOOL
\\VERIDISK
The command completed successfully.

3b.) "veridisk" browser view:
                Server Name Remark

-------------------------------------------------------------------------------
\\MULTITOOL1
\\POWERTOOL
\\VERIDISK
The command completed successfully.

1c.) "powertool" browstat status:
                Status for domain DISGUSTED on transport
\Device\NetBT_Tcpip_{49EB0BD6-0334-48D9-A6D8-3818B8BD6858}
    Browsing is active on domain.
    Master browser name is: VERIDISK
        Master browser is running build 2600
    1 backup servers retrieved from master VERIDISK
        \\VERIDISK
    There are 3 servers in domain DISGUSTED on transport
\Device\NetBT_Tcpip_{49EB0BD6-0334-48D9-A6D8-3818B8BD6858}
    There are 1 domains in domain DISGUSTED on transport
\Device\NetBT_Tcpip_{49EB0BD6-0334-48D9-A6D8-3818B8BD6858}

2c.) "multitool" browstat status:
                Status for domain DISGUSTED on transport
\Device\NetBT_Tcpip_{0F5B0BBB-99BB-4A1E-A25D-22718665A05C}
    Browsing is active on domain.
    Master browser name is: VERIDISK
        Master browser is running build 2600
    1 backup servers retrieved from master VERIDISK
        \\VERIDISK
    There are 3 servers in domain DISGUSTED on transport
\Device\NetBT_Tcpip_{0F5B0BBB-99BB-4A1E-A25D-22718665A05C}
    There are 1 domains in domain DISGUSTED on transport
\Device\NetBT_Tcpip_{0F5B0BBB-99BB-4A1E-A25D-22718665A05C}

3c.) "veridisk" browstat status:
                Status for domain DISGUSTED on transport
\Device\NetBT_Tcpip_{35A2B29B-F6FA-437D-88FE-B1CF4522AC30}
    Browsing is active on domain.
    Master browser name is: VERIDISK
        Master browser is running build 2600
    1 backup servers retrieved from master VERIDISK
        \\VERIDISK
    There are 3 servers in domain DISGUSTED on transport
\Device\NetBT_Tcpip_{35A2B29B-F6FA-437D-88FE-B1CF4522AC30}
    There are 1 domains in domain DISGUSTED on transport
\Device\NetBT_Tcpip_{35A2B29B-F6FA-437D-88FE-B1CF4522AC30}

                
As far as the ping tests: All 3 units can pass all 6 of the tests
mentioned.

Does all this information paint a helpful picture, Chuck? PLEASE NOTE
that "multitool1" is the laptop that's been hanging up when asked to
"View Workgroup Computers"; "veridisk" works w/out a hitch....
   Is it a telltale sign that, although "powertool" is the host
computer, for some reason "browstat status" on all 3 machines list
"veridisk" as the master browser?????

I'm looking forward to your next post, Chuck [:-))

Terry B.



Relevant Pages

  • Re: W2K Domain-Connected Laptop -> XP Workgroup Desktop via Crossover
    ... Status for domain NA on transport ... Master name cannot be determined from GetAdapterStatus. ... Status for domain WORKGROUP on transport ...
    (microsoft.public.windowsxp.network_web)
  • Re: W2K Domain-Connected Laptop -> XP Workgroup Desktop via Crossover
    ... Status for domain NA on transport ... Master name cannot be determined from GetAdapterStatus. ... Status for domain WORKGROUP on transport ...
    (microsoft.public.windowsxp.network_web)
  • Re: slow access to networked computer
    ... Master browser name is: PRINTER-CONNECT ... of browser master: 53 ... backup servers retrieved from master PRINTER-CONNECT ... There are 2 servers in domain FAMILY on transport \Device\NwlnkNb ...
    (microsoft.public.windowsxp.network_web)
  • Re: PCs not seeing each other
    ... MARK-X60S can ping MARK but MARK can not ping MARK-X60S ... Net config server ... Master browser name is: MARK-X60S ... There are 1 servers in domain ANY on transport ...
    (microsoft.public.windowsxp.network_web)
  • Re: Need help interpretting browstat output
    ... >> Master name cannot be determined from GetAdapterStatus. ... >>Status for domain WORKGROUP on transport \Device\Nbf_NdisWanNbfIn ...
    (microsoft.public.windowsxp.network_web)