Thanks in advance for any help,

I set up a wlan with USRobotics accesspoint/router 8054, pci cards and pc
card for laptop. One computer is XP pro sp2, one of the other two computers
is XP home service pack 2 and one is service pack 1. All three can access the
net. All three can ping the access point. The two XP home machines can ping
and access eachother. The XP pro machine can ping the other two machines but
it cant access them on the network, it cant even access the workgroup. The XP
pro also can not ping itself or see itself on the network. All three have the
same workgroup and all have tcp/ip selected. I checked the "guest" thing and
it is on. I did the TCP stack reset and it made lots of changes in the log
but didn't help the situation. I installed the newest driver for the PCI card
on the problem machine and I even tried cabling the machine to the access
point via a nic. Nothing made any difference.

I would really appreciate any advice,

Thanks,
Bob

On Sat, 20 Nov 2004 20:24:58 -0800, "Pacoquinha"
<(E-Mail Removed)> wrote:

>Thanks in advance for any help,
>
>I set up a wlan with USRobotics accesspoint/router 8054, pci cards and pc
>card for laptop. One computer is XP pro sp2, one of the other two computers
>is XP home service pack 2 and one is service pack 1. All three can access the
>net. All three can ping the access point. The two XP home machines can ping
>and access eachother. The XP pro machine can ping the other two machines but
>it cant access them on the network, it cant even access the workgroup. The XP
>pro also can not ping itself or see itself on the network. All three have the
>same workgroup and all have tcp/ip selected. I checked the "guest" thing and
>it is on. I did the TCP stack reset and it made lots of changes in the log
>but didn't help the situation. I installed the newest driver for the PCI card
>on the problem machine and I even tried cabling the machine to the access
>point via a nic. Nothing made any difference.
>
>I would really appreciate any advice,
>
>Thanks,
>Bob

Bob,

To start, 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, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

In article <C8D25725-E81E-4295-A71B-(E-Mail Removed)>,
"Pacoquinha" <(E-Mail Removed)> wrote:
>Thanks in advance for any help,
>
>I set up a wlan with USRobotics accesspoint/router 8054, pci cards and pc
>card for laptop. One computer is XP pro sp2, one of the other two computers
>is XP home service pack 2 and one is service pack 1. All three can access the
>net. All three can ping the access point. The two XP home machines can ping
>and access eachother. The XP pro machine can ping the other two machines but
>it cant access them on the network, it cant even access the workgroup. The XP
>pro also can not ping itself or see itself on the network. All three have the
>same workgroup and all have tcp/ip selected. I checked the "guest" thing and
>it is on. I did the TCP stack reset and it made lots of changes in the log
>but didn't help the situation. I installed the newest driver for the PCI card
>on the problem machine and I even tried cabling the machine to the access
>point via a nic. Nothing made any difference.
>
>I would really appreciate any advice,
>
>Thanks,
>Bob

Failure of a computer to ping itself is usually caused by a firewall
program (ZoneAlarm, Norton Internet Security, etc) that's
misconfigured or improperly un-installed.

If you've un-installed a firewall:

1. Re-install it.

2. Un-install it using the procedure provided by the manufacturer.

3. Go to Start | Run | Msconfig | Startup and disable any firewall
remnants.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Thank you Steve and Chuck,

I uninstalled my Norton and things started working better. Then I
reinstalled Norton and my network is still working pretty well. The only
problem I have now is that on XP pro machine I still "dosn't have access" to
view workgroup computers. Oh wait, I just tried again and I got in this time.
Hmmmmm, I wish I could understand this stuff better.......maybe with time.
Now I guess I should make sure that I dont have Norton set up too loose. I'll
read up on it and work backwards to make it as tight as possible w/o killing
my network.

Just for the fun of it here is the ipconfig log that chuck wanted to see. Do
you guys see anything that I should fix?

Windows IP Configuration Host Name . . . . . . . . . . . . : bob
Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . .
.. : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy
Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :
eatntn01.nj.comcastEthernet adapter Local Area Connection:
Connection-specific DNS Suffix . : eatntn01.nj.comcast Description .
.. . . . . . . . . . : Marvell Yukon Gigabit Ethernet 10/100/1000Base-T
Adapter, Copper RJ-45 Physical Address. . . . . . . . . :
00-0E-A6-A1-E9-FE Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . .
.. . : 192.168.123.103 Subnet Mask . . . . . . . . . . . :
255.255.255.0 Default Gateway . . . . . . . . . : 192.168.123.254
DHCP Server . . . . . . . . . . . : 192.168.123.254 DNS Servers . .
.. . . . . . . . . : 192.168.123.254 Lease Obtained. . . . . . . . . .
: Sunday, November 21, 2004 9:39:08 PM Lease Expires . . . . . . . . .
.. : Sunday, November 28, 2004 9:39:08 PMEthernet adapter Wireless Network
Connection 2: Connection-specific DNS Suffix . : Description
.. . . . . . . . . . . : U.S. Robotics 802.11g Wireless Turbo Adapter
Physical Address. . . . . . . . . : 00-C0-49-EE-CC-2D Dhcp Enabled. .
.. . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.123.101 Subnet Mask . . .
.. . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . :
192.168.123.254 DHCP Server . . . . . . . . . . . : 192.168.123.254
DNS Servers . . . . . . . . . . . : 192.168.123.254 Lease
Obtained. . . . . . . . . . : Sunday, November 21, 2004 9:39:08 PM
Lease Expires . . . . . . . . . . : Sunday, November 28, 2004 9:39:08 PM

Thank you very much,
Bob



"Steve Winograd [MVP]" wrote:

> In article <C8D25725-E81E-4295-A71B-(E-Mail Removed)>,
> "Pacoquinha" <(E-Mail Removed)> wrote:
> >Thanks in advance for any help,
> >
> >I set up a wlan with USRobotics accesspoint/router 8054, pci cards and pc
> >card for laptop. One computer is XP pro sp2, one of the other two computers
> >is XP home service pack 2 and one is service pack 1. All three can access the
> >net. All three can ping the access point. The two XP home machines can ping
> >and access eachother. The XP pro machine can ping the other two machines but
> >it cant access them on the network, it cant even access the workgroup. The XP
> >pro also can not ping itself or see itself on the network. All three have the
> >same workgroup and all have tcp/ip selected. I checked the "guest" thing and
> >it is on. I did the TCP stack reset and it made lots of changes in the log
> >but didn't help the situation. I installed the newest driver for the PCI card
> >on the problem machine and I even tried cabling the machine to the access
> >point via a nic. Nothing made any difference.
> >
> >I would really appreciate any advice,
> >
> >Thanks,
> >Bob
>
> Failure of a computer to ping itself is usually caused by a firewall
> program (ZoneAlarm, Norton Internet Security, etc) that's
> misconfigured or improperly un-installed.
>
> If you've un-installed a firewall:
>
> 1. Re-install it.
>
> 2. Un-install it using the procedure provided by the manufacturer.
>
> 3. Go to Start | Run | Msconfig | Startup and disable any firewall
> remnants.
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>

PS
I only included the ipconfig from the "problem" machine. If the other
machines are still relavent please tell me and I'll get the other ipconfig
files.

Thanks again,
Bob

"Pacoquinha" wrote:

> Thank you Steve and Chuck,
>
> I uninstalled my Norton and things started working better. Then I
> reinstalled Norton and my network is still working pretty well. The only
> problem I have now is that on XP pro machine I still "dosn't have access" to
> view workgroup computers. Oh wait, I just tried again and I got in this time.
> Hmmmmm, I wish I could understand this stuff better.......maybe with time.
> Now I guess I should make sure that I dont have Norton set up too loose. I'll
> read up on it and work backwards to make it as tight as possible w/o killing
> my network.
>
> Just for the fun of it here is the ipconfig log that chuck wanted to see. Do
> you guys see anything that I should fix?
>
> Windows IP Configuration Host Name . . . . . . . . . . . . : bob
> Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . .
> . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy
> Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :
> eatntn01.nj.comcastEthernet adapter Local Area Connection:
> Connection-specific DNS Suffix . : eatntn01.nj.comcast Description .
> . . . . . . . . . . : Marvell Yukon Gigabit Ethernet 10/100/1000Base-T
> Adapter, Copper RJ-45 Physical Address. . . . . . . . . :
> 00-0E-A6-A1-E9-FE Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . .
> . . : 192.168.123.103 Subnet Mask . . . . . . . . . . . :
> 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.123.254
> DHCP Server . . . . . . . . . . . : 192.168.123.254 DNS Servers . .
> . . . . . . . . . : 192.168.123.254 Lease Obtained. . . . . . . . . .
> : Sunday, November 21, 2004 9:39:08 PM Lease Expires . . . . . . . . .
> . : Sunday, November 28, 2004 9:39:08 PMEthernet adapter Wireless Network
> Connection 2: Connection-specific DNS Suffix . : Description
> . . . . . . . . . . . : U.S. Robotics 802.11g Wireless Turbo Adapter
> Physical Address. . . . . . . . . : 00-C0-49-EE-CC-2D Dhcp Enabled. .
> . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.123.101 Subnet Mask . . .
> . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . :
> 192.168.123.254 DHCP Server . . . . . . . . . . . : 192.168.123.254
> DNS Servers . . . . . . . . . . . : 192.168.123.254 Lease
> Obtained. . . . . . . . . . : Sunday, November 21, 2004 9:39:08 PM
> Lease Expires . . . . . . . . . . : Sunday, November 28, 2004 9:39:08 PM
>
> Thank you very much,
> Bob
>
>
>
> "Steve Winograd [MVP]" wrote:
>
> > In article <C8D25725-E81E-4295-A71B-(E-Mail Removed)>,
> > "Pacoquinha" <(E-Mail Removed)> wrote:
> > >Thanks in advance for any help,
> > >
> > >I set up a wlan with USRobotics accesspoint/router 8054, pci cards and pc
> > >card for laptop. One computer is XP pro sp2, one of the other two computers
> > >is XP home service pack 2 and one is service pack 1. All three can access the
> > >net. All three can ping the access point. The two XP home machines can ping
> > >and access eachother. The XP pro machine can ping the other two machines but
> > >it cant access them on the network, it cant even access the workgroup. The XP
> > >pro also can not ping itself or see itself on the network. All three have the
> > >same workgroup and all have tcp/ip selected. I checked the "guest" thing and
> > >it is on. I did the TCP stack reset and it made lots of changes in the log
> > >but didn't help the situation. I installed the newest driver for the PCI card
> > >on the problem machine and I even tried cabling the machine to the access
> > >point via a nic. Nothing made any difference.
> > >
> > >I would really appreciate any advice,
> > >
> > >Thanks,
> > >Bob
> >
> > Failure of a computer to ping itself is usually caused by a firewall
> > program (ZoneAlarm, Norton Internet Security, etc) that's
> > misconfigured or improperly un-installed.
> >
> > If you've un-installed a firewall:
> >
> > 1. Re-install it.
> >
> > 2. Un-install it using the procedure provided by the manufacturer.
> >
> > 3. Go to Start | Run | Msconfig | Startup and disable any firewall
> > remnants.
> > --
> > Best Wishes,
> > Steve Winograd, MS-MVP (Windows Networking)
> >
> > Please post any reply as a follow-up message in the news group
> > for everyone to see. I'm sorry, but I don't answer questions
> > addressed directly to me in E-mail or news groups.
> >
> > Microsoft Most Valuable Professional Program
> > http://mvp.support.microsoft.com
> >

On Mon, 22 Nov 2004 00:35:03 -0800, "Pacoquinha"
<(E-Mail Removed)> wrote:

>PS
>I only included the ipconfig from the "problem" machine. If the other
>machines are still relavent please tell me and I'll get the other ipconfig
>files.
>
>Thanks again,
>Bob
>
>"Pacoquinha" wrote:
>
>> Thank you Steve and Chuck,
>>
>> I uninstalled my Norton and things started working better. Then I
>> reinstalled Norton and my network is still working pretty well. The only
>> problem I have now is that on XP pro machine I still "dosn't have access" to
>> view workgroup computers. Oh wait, I just tried again and I got in this time.
>> Hmmmmm, I wish I could understand this stuff better.......maybe with time.
>> Now I guess I should make sure that I dont have Norton set up too loose. I'll
>> read up on it and work backwards to make it as tight as possible w/o killing
>> my network.
>>
>> Just for the fun of it here is the ipconfig log that chuck wanted to see. Do
>> you guys see anything that I should fix?
>>
>> Windows IP Configuration Host Name . . . . . . . . . . . . : bob
>> Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . .
>> . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy
>> Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :
>> eatntn01.nj.comcastEthernet adapter Local Area Connection:
>> Connection-specific DNS Suffix . : eatntn01.nj.comcast Description .
>> . . . . . . . . . . : Marvell Yukon Gigabit Ethernet 10/100/1000Base-T
>> Adapter, Copper RJ-45 Physical Address. . . . . . . . . :
>> 00-0E-A6-A1-E9-FE Dhcp Enabled. . . . . . . . . . . : Yes
>> Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . .
>> . . : 192.168.123.103 Subnet Mask . . . . . . . . . . . :
>> 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.123.254
>> DHCP Server . . . . . . . . . . . : 192.168.123.254 DNS Servers . .
>> . . . . . . . . . : 192.168.123.254 Lease Obtained. . . . . . . . . .
>> : Sunday, November 21, 2004 9:39:08 PM Lease Expires . . . . . . . . .
>> . : Sunday, November 28, 2004 9:39:08 PMEthernet adapter Wireless Network
>> Connection 2: Connection-specific DNS Suffix . : Description
>> . . . . . . . . . . . : U.S. Robotics 802.11g Wireless Turbo Adapter
>> Physical Address. . . . . . . . . : 00-C0-49-EE-CC-2D Dhcp Enabled. .
>> . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
>> IP Address. . . . . . . . . . . . : 192.168.123.101 Subnet Mask . . .
>> . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . :
>> 192.168.123.254 DHCP Server . . . . . . . . . . . : 192.168.123.254
>> DNS Servers . . . . . . . . . . . : 192.168.123.254 Lease
>> Obtained. . . . . . . . . . : Sunday, November 21, 2004 9:39:08 PM
>> Lease Expires . . . . . . . . . . : Sunday, November 28, 2004 9:39:08 PM
>>
>> Thank you very much,
>> Bob

Bob,

The computer causing a problem is not always the one from which the symptom is
immediately seen.

So please do extract "ipconfig /all" from all computers. The more diagnoses we
can assemble, the better the chance of identifying the problems.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

Hi Chuck,

The network seems to be working OK now however there is still something
going on with the workgroup. Sometimes I dont see all the computers in the
workgroup however I can see all the shared folders on the computers in my
network places. At this point I'm pretty satisfied with how it is working, I
can do everything that I need to.

Here are the three ipconfig files. If you see something wrong please show me
so I can fix it.
Thank you again,
Bob



Windows IP Configuration



Host Name . . . . . . . . . . . . : laptop1

Primary Dns Suffix . . . . . . . :

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

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

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



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : U.S. Robotics 802.11g Wireless
Turbo Adapter

Physical Address. . . . . . . . . : 00-C0-49-E9-44-A5

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.123.102

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

Default Gateway . . . . . . . . . : 192.168.123.254

DHCP Server . . . . . . . . . . . : 192.168.123.254

DNS Servers . . . . . . . . . . . : 192.168.123.254

Lease Obtained. . . . . . . . . . : Tuesday, November 23, 2004
11:12:50 PM

Lease Expires . . . . . . . . . . : Tuesday, November 30, 2004
11:12:50 PM



Ethernet adapter Network Bridge:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : MAC Bridge Miniport

Physical Address. . . . . . . . . : 22-ED-47-E5-C6-37

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.113.254

Subnet Mask . . . . . . . . . . . : 255.255.0.0

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



Windows IP Configuration



Host Name . . . . . . . . . . . . : estela

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

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

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



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : U.S. Robotics 802.11g Wireless
Turbo Adapter

Physical Address. . . . . . . . . : 00-C0-49-EE-CB-F2

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.123.100

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

Default Gateway . . . . . . . . . : 192.168.123.254

DHCP Server . . . . . . . . . . . : 192.168.123.254

DNS Servers . . . . . . . . . . . : 192.168.123.254

Lease Obtained. . . . . . . . . . : Tuesday, November 23, 2004
10:10:42 PM

Lease Expires . . . . . . . . . . : Tuesday, November 30, 2004
10:10:42 PM



PPP adapter {5CDE7ED9-E9BE-4C11-ADDF-CD0979BB7CC7}:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

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

IP Address. . . . . . . . . . . . : 172.134.225.254

Subnet Mask . . . . . . . . . . . : 255.255.255.255

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

DNS Servers . . . . . . . . . . . : 205.188.146.146

NetBIOS over Tcpip. . . . . . . . : Disabled




Windows IP Configuration



Host Name . . . . . . . . . . . . : bob

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

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

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

DNS Suffix Search List. . . . . . : eatntn01.nj.comcast



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : eatntn01.nj.comcast

Description . . . . . . . . . . . : Marvell Yukon Gigabit Ethernet
10/100/1000Base-T Adapter, Copper RJ-45

Physical Address. . . . . . . . . : 00-0E-A6-A1-E9-FE

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.123.103

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

Default Gateway . . . . . . . . . : 192.168.123.254

DHCP Server . . . . . . . . . . . : 192.168.123.254

DNS Servers . . . . . . . . . . . : 192.168.123.254

Lease Obtained. . . . . . . . . . : Sunday, November 21, 2004
9:39:08 PM

Lease Expires . . . . . . . . . . : Sunday, November 28, 2004
9:39:08 PM



Ethernet adapter Wireless Network Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : U.S. Robotics 802.11g Wireless
Turbo Adapter

Physical Address. . . . . . . . . : 00-C0-49-EE-CC-2D

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.123.101

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

Default Gateway . . . . . . . . . : 192.168.123.254

DHCP Server . . . . . . . . . . . : 192.168.123.254

DNS Servers . . . . . . . . . . . : 192.168.123.254

Lease Obtained. . . . . . . . . . : Sunday, November 21, 2004
9:39:08 PM

Lease Expires . . . . . . . . . . : Sunday, November 28, 2004
9:39:08 PM



"Chuck" wrote:

> On Mon, 22 Nov 2004 00:35:03 -0800, "Pacoquinha"
> <(E-Mail Removed)> wrote:
>
> >PS
> >I only included the ipconfig from the "problem" machine. If the other
> >machines are still relavent please tell me and I'll get the other ipconfig
> >files.
> >
> >Thanks again,
> >Bob
> >
> >"Pacoquinha" wrote:
> >
> >> Thank you Steve and Chuck,
> >>
> >> I uninstalled my Norton and things started working better. Then I
> >> reinstalled Norton and my network is still working pretty well. The only
> >> problem I have now is that on XP pro machine I still "dosn't have access" to
> >> view workgroup computers. Oh wait, I just tried again and I got in this time.
> >> Hmmmmm, I wish I could understand this stuff better.......maybe with time.
> >> Now I guess I should make sure that I dont have Norton set up too loose. I'll
> >> read up on it and work backwards to make it as tight as possible w/o killing
> >> my network.
> >>
> >> Just for the fun of it here is the ipconfig log that chuck wanted to see. Do
> >> you guys see anything that I should fix?
> >>
> >> Windows IP Configuration Host Name . . . . . . . . . . . . : bob
> >> Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . .
> >> . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy
> >> Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :
> >> eatntn01.nj.comcastEthernet adapter Local Area Connection:
> >> Connection-specific DNS Suffix . : eatntn01.nj.comcast Description .
> >> . . . . . . . . . . : Marvell Yukon Gigabit Ethernet 10/100/1000Base-T
> >> Adapter, Copper RJ-45 Physical Address. . . . . . . . . :
> >> 00-0E-A6-A1-E9-FE Dhcp Enabled. . . . . . . . . . . : Yes
> >> Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . .
> >> . . : 192.168.123.103 Subnet Mask . . . . . . . . . . . :
> >> 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.123.254
> >> DHCP Server . . . . . . . . . . . : 192.168.123.254 DNS Servers . .
> >> . . . . . . . . . : 192.168.123.254 Lease Obtained. . . . . . . . . .
> >> : Sunday, November 21, 2004 9:39:08 PM Lease Expires . . . . . . . . .
> >> . : Sunday, November 28, 2004 9:39:08 PMEthernet adapter Wireless Network
> >> Connection 2: Connection-specific DNS Suffix . : Description
> >> . . . . . . . . . . . : U.S. Robotics 802.11g Wireless Turbo Adapter
> >> Physical Address. . . . . . . . . : 00-C0-49-EE-CC-2D Dhcp Enabled. .
> >> . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
> >> IP Address. . . . . . . . . . . . : 192.168.123.101 Subnet Mask . . .
> >> . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . :
> >> 192.168.123.254 DHCP Server . . . . . . . . . . . : 192.168.123.254
> >> DNS Servers . . . . . . . . . . . : 192.168.123.254 Lease
> >> Obtained. . . . . . . . . . : Sunday, November 21, 2004 9:39:08 PM
> >> Lease Expires . . . . . . . . . . : Sunday, November 28, 2004 9:39:08 PM
> >>
> >> Thank you very much,
> >> Bob
>
> Bob,
>
> The computer causing a problem is not always the one from which the symptom is
> immediately seen.
>
> So please do extract "ipconfig /all" from all computers. The more diagnoses we
> can assemble, the better the chance of identifying the problems.
>
> --
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>

On Tue, 23 Nov 2004 20:43:03 -0800, "Pacoquinha"
<(E-Mail Removed)> wrote:

>Hi Chuck,
>
>The network seems to be working OK now however there is still something
>going on with the workgroup. Sometimes I dont see all the computers in the
>workgroup however I can see all the shared folders on the computers in my
>network places. At this point I'm pretty satisfied with how it is working, I
>can do everything that I need to.
>
>Here are the three ipconfig files. If you see something wrong please show me
>so I can fix it.
>Thank you again,
>Bob

<SNIP>

Bob,

First, let's address the browser (no, I'm not talking about Internet Explorer
here) issue on your LAN. The browser is the little known component of the
operating system that makes it possible for each computer on the LAN to know
what shared data is available on the LAN (which for Windows XP, determines what
computers can be seen in Network Neighborhood).

Identify which TWO computers of your LAN should be online the most frequently
and consistently. The computer online the most should be the master browser,
and the computer online less than the master but more than the third, will be
the backup browser.

Make sure the browser service is running on both the master and backup browser
computers. Control Panel - Administrative Tools - Services. Verify that the
Computer Browser, and the TCP/IP NetBIOS Helper, services both show with Status
= Started. Disable the browser on the third computer.

Power OFF all three computers. Power on the master browser computer, and bring
it online. Then do the same for the backup browser computer, and finally the
third computer.

Then see what the browser situation is, on all 3 computers.

The Microsoft Browstat program will show us what browsers you have in your
domain / workgroup, at any time.
http://support.microsoft.com/?id=188305

You can download Browstat from either:
<http://www.dynawell.com/reskit/microsoft/win2000/browstat.zip>
<http://rescomp.stanford.edu/staff/manual/rcc/tools/browstat.zip>

Browstat is very small (40K), and needs no install. Just unzip the downloaded
file, copy browstat.exe to any folder in the Path, and run it from a command
window, by "browstat status". Make sure all computers give the same result,
when all computers are online.

For more information about the browser subsystem (very intricate), see:
http://support.microsoft.com/?id=188001
http://support.microsoft.com/?id=188305
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

Please provide browstat information for each computer, when all computers are
online. Start - Run - "cmd". Type "browstat status >c:\browstat.txt" into the
command window - Open c:\browstat.txt in Notepad, make sure that Format - Word
Wrap is NOT checked!, copy and paste into your next post. Identify each
computer by name and operating system.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.