Re: view workgroup computers--workaround

• Previous message: raymond: "Re: XP SP2: Annoying balloon-help regarding "Wireless is not connected""
• In reply to: Terry B.: "Re: view workgroup computers--workaround"
• Next in thread: Terry B.: "Re: view workgroup computers--workaround"
• Reply: Terry B.: "Re: view workgroup computers--workaround"
• Messages sorted by: [ date ] [ thread ]

Date: 14 Oct 2004 00:21:09 -0500

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.

• Previous message: raymond: "Re: XP SP2: Annoying balloon-help regarding "Wireless is not connected""
• In reply to: Terry B.: "Re: view workgroup computers--workaround"
• Next in thread: Terry B.: "Re: view workgroup computers--workaround"
• Reply: Terry B.: "Re: view workgroup computers--workaround"
• Messages sorted by: [ date ] [ thread ]