Hi,

I have 2 PC, PC1 & PC2. PC1 has XP Professional installed, PC2 has XP
Home installed. Both PC were assigned fixed IP and were set belonged to
same workgroup named WORKGROUP. The PCs were connected by hubs. All
PCs, hubs & LAN cables had been used in the past for networking with no
problem. But today the PCs couldn't be connected (actually this was not
the first time happening). Below are problem scenario.

1. I logged in PC1 with its admin account & disabled NIS there to ease
troubleshooting.

2. I logged in PC2 with its admin account & disabled Mcafee security
centre to ease troubleshooting.

3. I pinged PC1's IP from PC1, replies returned successfully.

4. I pinged PC2's IP from PC2, replies returned successfully.

5. I pinged PC2's IP from PC1, request timed out.

6. I pinged PC1's IP from PC2, request timed out.

7. I could see PC2's icon from PC1->Network Neighourhood->Microsoft
Windows Network->Workgroup. When I double clicked PC2's icon, it
returned error complaining probably no right to use network resource (I
enabled sharing access & modified on whole HD of PC2 to ease
troubleshooting).

8. At PC2, When I double clicked Network Neighourhood->Microsoft
Windows Network->Workgroup, it returned error complaining couldn't
visit Workgroup probably due to no right to use network resource.

9. I rebooted PC2 and keep on pinging PC2 from PC1. I found that from
when XP Home boot logo appeared till choosed to login PC2's admin
account, pinging returned replies successfully to PC1. However, after
successful login, pinging request timed out again no matter I disabled
Mcafee or not at PC2.

10. I changed IP of PC2 then rebooted it. As 9. pinging from PC1 to PC2
was successful until I logged on PC2 successfully with another account,
called it admin_guest, which was of admin type also.

11. I wanted to follow 8. but found Network Neighbourhood showed empty
content. So I decided to reboot PC2 again and login using admin_guest
again.

12. Observation described 10. repeated. This time Network Neighbourhood
as non-empty but same error returned as described in 8.

Actually, above scenario wasn't appeared the first time. In the past, I
just kept on changing disk sharing & IP settings or keep on pinging
each PC from the other one. The problem could be solved for no reason.
But still I don't know why microsoft networking is so unstable for my
case.

Besides, I wanted to use PCAnyWhere in PC1 to control PC2 remotely.
With such unstable & unknown XP networking connection, I couldn't
achieve my goal.

Could anyone help me to troubleshoot this case ?

Tks!

In article <1134681619.317222.158720@g43g2000cwa.googlegroups .com>,
Emil_Lam@mailcity.com says...
> Hi,
>
> I have 2 PC, PC1 & PC2. PC1 has XP Professional installed, PC2 has XP
> Home installed. Both PC were assigned fixed IP and were set belonged to
> same workgroup named WORKGROUP. The PCs were connected by hubs. All
> PCs, hubs & LAN cables had been used in the past for networking with no
> problem. But today the PCs couldn't be connected (actually this was not
> the first time happening). Below are problem scenario.
>
> 1. I logged in PC1 with its admin account & disabled NIS there to ease
> troubleshooting.
>
> 2. I logged in PC2 with its admin account & disabled Mcafee security
> centre to ease troubleshooting.
>
> 3. I pinged PC1's IP from PC1, replies returned successfully.
>
> 4. I pinged PC2's IP from PC2, replies returned successfully.
>
> 5. I pinged PC2's IP from PC1, request timed out.
>
> 6. I pinged PC1's IP from PC2, request timed out.
>
> 7. I could see PC2's icon from PC1->Network Neighourhood->Microsoft
> Windows Network->Workgroup. When I double clicked PC2's icon, it
> returned error complaining probably no right to use network resource (I
> enabled sharing access & modified on whole HD of PC2 to ease
> troubleshooting).
>
> 8. At PC2, When I double clicked Network Neighourhood->Microsoft
> Windows Network->Workgroup, it returned error complaining couldn't
> visit Workgroup probably due to no right to use network resource.
>
> 9. I rebooted PC2 and keep on pinging PC2 from PC1. I found that from
> when XP Home boot logo appeared till choosed to login PC2's admin
> account, pinging returned replies successfully to PC1. However, after
> successful login, pinging request timed out again no matter I disabled
> Mcafee or not at PC2.
>
> 10. I changed IP of PC2 then rebooted it. As 9. pinging from PC1 to PC2
> was successful until I logged on PC2 successfully with another account,
> called it admin_guest, which was of admin type also.
>
> 11. I wanted to follow 8. but found Network Neighbourhood showed empty
> content. So I decided to reboot PC2 again and login using admin_guest
> again.
>
> 12. Observation described 10. repeated. This time Network Neighbourhood
> as non-empty but same error returned as described in 8.
>
> Actually, above scenario wasn't appeared the first time. In the past, I
> just kept on changing disk sharing & IP settings or keep on pinging
> each PC from the other one. The problem could be solved for no reason.
> But still I don't know why microsoft networking is so unstable for my
> case.
>
> Besides, I wanted to use PCAnyWhere in PC1 to control PC2 remotely.
> With such unstable & unknown XP networking connection, I couldn't
> achieve my goal.
>
> Could anyone help me to troubleshoot this case ?

Lets make life simple:

Assuming that you have some form of NAT router, that it's setup with the
LAN side as 192.168.5.1 / 255.255.255.0 and has PUBLIC DNS 1 & 2

PC1: Workgroup Name = Workgroup
IP Address: 192.168.5.50
Network Mask: 255.255.255.0
Default Gateway: 192.168.5.1
DNS1: Your ISP's DNS1
DNS2: Your ISP's DNS2
Computer Name: MyPC1

PC2: Workgroup Name = Workgroup
IP Address: 192.168.5.51
Network Mask: 255.255.255.0
Default Gateway: 192.168.5.1
DNS1: Your ISP's DNS1
DNS2: Your ISP's DNS2
Computer Name: MyPC2

Reboot, disable NIS, disable Windows Firewall too.

Make sure that you have File/Printer Sharing Enabled on both computers,
make sure that you have NO FIREWALL RUNNING.

Ping PC2 from PC1 - if this fails, stop, you need to resolve this.

Ping PC1 from PC2 - if this fails, stop, you need to resolve this.

From PC1, PING MyPC2 - if this fails, stop - you need to resolve this.
From PC2, PING MyPC1...

If you can't ping by name you have bigger problems.

Also, just because your cables/hub worked before, it doesn't mean that
they still do - I installed a Firewall into a customers office
yesterday, had everything working, left, got a call 10 minutes later,
the 12 port switch they had used for 2 years had died.....



--

spam999free@rrohio.com
remove 999 in order to email me

"Leythos" <void@nowhere.lan> wrote in message
news:zjlof.190986$tD4.143591@tornado.ohiordc.rr.co m...
> In article <1134681619.317222.158720@g43g2000cwa.googlegroups .com>,
> Emil_Lam@mailcity.com says...
>> Hi,
>>
>> I have 2 PC, PC1 & PC2. PC1 has XP Professional installed, PC2 has XP
>> Home installed. Both PC were assigned fixed IP and were set belonged to
>> same workgroup named WORKGROUP. The PCs were connected by hubs. All
>> PCs, hubs & LAN cables had been used in the past for networking with no
>> problem. But today the PCs couldn't be connected (actually this was not
>> the first time happening). Below are problem scenario.
>>
>> 1. I logged in PC1 with its admin account & disabled NIS there to ease
>> troubleshooting.
>>
>> 2. I logged in PC2 with its admin account & disabled Mcafee security
>> centre to ease troubleshooting.
>>
>> 3. I pinged PC1's IP from PC1, replies returned successfully.
>>
>> 4. I pinged PC2's IP from PC2, replies returned successfully.
>>
>> 5. I pinged PC2's IP from PC1, request timed out.
>>
>> 6. I pinged PC1's IP from PC2, request timed out.
>>
>> 7. I could see PC2's icon from PC1->Network Neighourhood->Microsoft
>> Windows Network->Workgroup. When I double clicked PC2's icon, it
>> returned error complaining probably no right to use network resource (I
>> enabled sharing access & modified on whole HD of PC2 to ease
>> troubleshooting).
>>
>> 8. At PC2, When I double clicked Network Neighourhood->Microsoft
>> Windows Network->Workgroup, it returned error complaining couldn't
>> visit Workgroup probably due to no right to use network resource.
>>
>> 9. I rebooted PC2 and keep on pinging PC2 from PC1. I found that from
>> when XP Home boot logo appeared till choosed to login PC2's admin
>> account, pinging returned replies successfully to PC1. However, after
>> successful login, pinging request timed out again no matter I disabled
>> Mcafee or not at PC2.
>>
>> 10. I changed IP of PC2 then rebooted it. As 9. pinging from PC1 to PC2
>> was successful until I logged on PC2 successfully with another account,
>> called it admin_guest, which was of admin type also.
>>
>> 11. I wanted to follow 8. but found Network Neighbourhood showed empty
>> content. So I decided to reboot PC2 again and login using admin_guest
>> again.
>>
>> 12. Observation described 10. repeated. This time Network Neighbourhood
>> as non-empty but same error returned as described in 8.
>>
>> Actually, above scenario wasn't appeared the first time. In the past, I
>> just kept on changing disk sharing & IP settings or keep on pinging
>> each PC from the other one. The problem could be solved for no reason.
>> But still I don't know why microsoft networking is so unstable for my
>> case.
>>
>> Besides, I wanted to use PCAnyWhere in PC1 to control PC2 remotely.
>> With such unstable & unknown XP networking connection, I couldn't
>> achieve my goal.
>>
>> Could anyone help me to troubleshoot this case ?
>
> Lets make life simple:
>
> Assuming that you have some form of NAT router, that it's setup with the
> LAN side as 192.168.5.1 / 255.255.255.0 and has PUBLIC DNS 1 & 2
>
> PC1: Workgroup Name = Workgroup
> IP Address: 192.168.5.50
> Network Mask: 255.255.255.0
> Default Gateway: 192.168.5.1
> DNS1: Your ISP's DNS1
> DNS2: Your ISP's DNS2
> Computer Name: MyPC1
>
> PC2: Workgroup Name = Workgroup
> IP Address: 192.168.5.51
> Network Mask: 255.255.255.0
> Default Gateway: 192.168.5.1
> DNS1: Your ISP's DNS1
> DNS2: Your ISP's DNS2
> Computer Name: MyPC2
>
> Reboot, disable NIS, disable Windows Firewall too.
>
> Make sure that you have File/Printer Sharing Enabled on both computers,
> make sure that you have NO FIREWALL RUNNING.
Doesn't his symptoms indicate that the firewalls were blocking icmp packets?
I had a similar problem which cured itself when I enabled icmp.
By stopping the firewalls, you have removed one possible source of his
problem.
Jim
>
> Ping PC2 from PC1 - if this fails, stop, you need to resolve this.
>
> Ping PC1 from PC2 - if this fails, stop, you need to resolve this.
>
> From PC1, PING MyPC2 - if this fails, stop - you need to resolve this.
> From PC2, PING MyPC1...
>
> If you can't ping by name you have bigger problems.
>
> Also, just because your cables/hub worked before, it doesn't mean that
> they still do - I installed a Firewall into a customers office
> yesterday, had everything working, left, got a call 10 minutes later,
> the 12 port switch they had used for 2 years had died.....
>
>
>
> --
>
> spam999free@rrohio.com
> remove 999 in order to email me

In article <Dnlof.33233$7h7.4513@newssvr21.news.prodigy.com>,
j.n@nospam.com says...
> Doesn't his symptoms indicate that the firewalls were blocking icmp packets?
> I had a similar problem which cured itself when I enabled icmp.
> By stopping the firewalls, you have removed one possible source of his
> problem.

Yes, but he already said he disabled them. If they are really disabled
then it could be any number of other problems.

Since he's had this type of problem before, it could still be any number
of problems.

So, with the firewalls disabled we have to start with a known network
configuration that would work for the same situation anywhere.

--

spam999free@rrohio.com
remove 999 in order to email me

emil_lam wrote:
>
http://www.microsoft.com/windowsxp/homenetworking/
http://compnetworking.about.com/cs/winxpnetworking/
http://support.microsoft.com/?kbid=813936
http://www.onecomputerguy.com/networking/xp_network.htm
http://www.microsoft.com/windowsxp/u...d/default.mspx




--
http://www.bootdisk.com/

On or about 16/12/05, Ah-rud-nefer I
<ah-rud-nefer.i@you.self-important-skinny-gusher.org>, the bald-headed
bummer and windward, flea-bitten undertaker, wrote in
<2cdbf5c5b77a4889b83ec49303be3601@you.self-important-skinny-gusher.org>:


Methylsulfonyl-Dodecyl-Strontium-1-Butanamide

O2-4-Hylphenyl-Pyrazine

Furylcarbonyl-Pyridyloxy-Trimethyloctadecylammonium-Oxy-4-Piperidinoacetonitrile

Ei arci que rexit ruisque fusa miremur rimabar sive en. Nam nos decedat si
tege stipant ah, via pila o. Es hucque veho os, evantes illoc susurro meas
qua.

Cognati livi pacarit ut rari cauato cymba.

Dexteras plus pube ii aspectu iudicas mi alumno, viis ex. Abimus prona deam
me iuris tegmine re.

Auunculo ruiebam, easque mi stultus futura itaque edat vir. Oves pergam
doloque, ne hausere aevo, di malebam errabam, it.

Fetu solida vimen abque venta penitus ui uter acte ui. Ad delecta, eamque id
viisque novo prendit iugo time ob. Ascendebant ore eri araque eis ruamque is
turmae solque si.

{ReplyToNameQuoteHeader}

{ReplyToMailAddressQuoteHeader}

{ReplyToDateQuoteHeader}

{ReplyToMessageIDQuoteHeader}

squinting, pompous scantling

Commissioner Lancelot Sicklelark-Hashkadge, The Royal South Yorkshire
Engineers (GVCO OBI DFC),
<rec.photo.bulging.slop.hole@untidy-mud-flaps.net>, the thundering,
reptilian dodo, and pillow lace maker, decried:

> On or about 16/12/05, Ah-rud-nefer I
> <ah-rud-nefer.i@you.self-important-skinny-gusher.org>, the bald-headed
> bummer and windward, flea-bitten undertaker, wrote in
> <2cdbf5c5b77a4889b83ec49303be3601@you.self-important-skinny-gusher.org>:
>
>
> Methylsulfonyl-Dodecyl-Strontium-1-Butanamide
>
> O2-4-Hylphenyl-Pyrazine
>
Furylcarbonyl-Pyridyloxy-Trimethyloctadecylammonium-Oxy-4-Piperidinoacetonit
rile
>
> Ei arci que rexit ruisque fusa miremur rimabar sive en. Nam nos
> decedat si tege stipant ah, via pila o. Es hucque veho os, evantes
> illoc susurro meas qua.
>
> Cognati livi pacarit ut rari cauato cymba.
>
> Dexteras plus pube ii aspectu iudicas mi alumno, viis ex. Abimus
> prona deam me iuris tegmine re.
>
> Auunculo ruiebam, easque mi stultus futura itaque edat vir. Oves
> pergam doloque, ne hausere aevo, di malebam errabam, it.
>
> Fetu solida vimen abque venta penitus ui uter acte ui. Ad delecta,
> eamque id viisque novo prendit iugo time ob. Ascendebant ore eri
> araque eis ruamque is turmae solque si.
>
> {ReplyToNameQuoteHeader}
>
> {ReplyToMailAddressQuoteHeader}
>
> {ReplyToDateQuoteHeader}
>
> {ReplyToMessageIDQuoteHeader}
>
> squinting, pompous scantling

Wicked! <FBG>

Do I get a copy now, when it's cooked?

Leythos 寫道：

> In article <1134681619.317222.158720@g43g2000cwa.googlegroups .com>,
>
> Lets make life simple:
>
> Assuming that you have some form of NAT router, that it's setup with the
> LAN side as 192.168.5.1 / 255.255.255.0 and has PUBLIC DNS 1 & 2
>
> PC1: Workgroup Name = Workgroup
> IP Address: 192.168.5.50
> Network Mask: 255.255.255.0
> Default Gateway: 192.168.5.1
> DNS1: Your ISP's DNS1
> DNS2: Your ISP's DNS2
> Computer Name: MyPC1
>
> PC2: Workgroup Name = Workgroup
> IP Address: 192.168.5.51
> Network Mask: 255.255.255.0
> Default Gateway: 192.168.5.1
> DNS1: Your ISP's DNS1
> DNS2: Your ISP's DNS2
> Computer Name: MyPC2
>
> Reboot, disable NIS, disable Windows Firewall too.
>
Oops! Sorry I forgot to disable Windows XP Internet connection
firewall. Now problem solved with my local LAN after Windows setting
changed. I could even use PCAnyWhere with both sides PC having NIS &
Mcafee running. Remaining problem being how to use it over internet.

> Make sure that you have File/Printer Sharing Enabled on both computers,
> make sure that you have NO FIREWALL RUNNING.
>
> Ping PC2 from PC1 - if this fails, stop, you need to resolve this.
>
> Ping PC1 from PC2 - if this fails, stop, you need to resolve this.
>
> From PC1, PING MyPC2 - if this fails, stop - you need to resolve this.
> From PC2, PING MyPC1...
>
> If you can't ping by name you have bigger problems.
>
> Also, just because your cables/hub worked before, it doesn't mean that
> they still do - I installed a Firewall into a customers office
> yesterday, had everything working, left, got a call 10 minutes later,
> the 12 port switch they had used for 2 years had died.....
>
>
>
> --
>
> spam999free@rrohio.com
> remove 999 in order to email me