Peer to Peer network problem pinging  
Author Message
Jupiter





PostPosted: Wed Feb 09 13:44:18 CST 2005 Top

Windows XP Network >> Peer to Peer network problem pinging Hi,
i am in desperate need of help or i will go insane!

I have an XP Home host and a 98se client.

the client can ping 127.0.0.1 and 192.168.10.2 (it's own IP address)

However....the host can ping 127.0.0.1 but when i try to ping 192.168.10.1 i
get the now dreaded "reqyuest timed out".

At the same time my task bar is showing that my LAN is connected and running
at a speed of 100 Mbps.

in desperation i've bought another network card and put it in a spare slot
to se if this will fix the problem, but this just tells me that i have a
cable unplugged and refuses to work........

GRRRRRRRR

Windows XP140  
 
 
Steve





PostPosted: Wed Feb 09 13:44:18 CST 2005 Top

Windows XP Network >> Peer to Peer network problem pinging In article <EMail@HideDomain.com>,
"Nicko" <EMail@HideDomain.com> wrote:
>Hi,
>i am in desperate need of help or i will go insane!
>
>I have an XP Home host and a 98se client.
>
>the client can ping 127.0.0.1 and 192.168.10.2 (it's own IP address)
>
>However....the host can ping 127.0.0.1 but when i try to ping 192.168.10.1 i
>get the now dreaded "reqyuest timed out".
>
>At the same time my task bar is showing that my LAN is connected and running
>at a speed of 100 Mbps.
>
>in desperation i've bought another network card and put it in a spare slot
>to se if this will fix the problem, but this just tells me that i have a
>cable unplugged and refuses to work........
>
>GRRRRRRRR

I assume that "192.168.10.1" is a typo and that you've actually pinged
"192.168.0.1" on the host.

When a computer can't ping its own IP address, the problem is probably
caused by a firewall program.

While troubleshooting, disconnect from the Internet and un-install
(don't just disable) all firewall programs. After un-installing, go
to Start | Run | Msconfig | Startup and disable any remnants of
firewalls. For example, ZoneAlarm sometimes leaves bits of itself
behind.

Don't re-install a firewall until everything is working.
--
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
 
 
Nicko





PostPosted: Wed Feb 09 14:43:01 CST 2005 Top

Windows XP Network >> Peer to Peer network problem pinging hi,

no it's not a typo. when i run "ipconfig /all" that's the ip address i get.
i've also tried taking down the firewall but to no avail. not tried
uninstalling though. i've been told to uninstall tcp/ip but can't see how to
do this, do you think this would help? sorry if i'm slow to respond but it's
8.45pm in the uk!

"Steve Winograd [MVP]" wrote:

> In article <EMail@HideDomain.com>,
> "Nicko" <EMail@HideDomain.com> wrote:
> >Hi,
> >i am in desperate need of help or i will go insane!
> >
> >I have an XP Home host and a 98se client.
> >
> >the client can ping 127.0.0.1 and 192.168.10.2 (it's own IP address)
> >
> >However....the host can ping 127.0.0.1 but when i try to ping 192.168.10.1 i
> >get the now dreaded "reqyuest timed out".
> >
> >At the same time my task bar is showing that my LAN is connected and running
> >at a speed of 100 Mbps.
> >
> >in desperation i've bought another network card and put it in a spare slot
> >to se if this will fix the problem, but this just tells me that i have a
> >cable unplugged and refuses to work........
> >
> >GRRRRRRRR
>
> I assume that "192.168.10.1" is a typo and that you've actually pinged
> "192.168.0.1" on the host.
>
> When a computer can't ping its own IP address, the problem is probably
> caused by a firewall program.
>
> While troubleshooting, disconnect from the Internet and un-install
> (don't just disable) all firewall programs. After un-installing, go
> to Start | Run | Msconfig | Startup and disable any remnants of
> firewalls. For example, ZoneAlarm sometimes leaves bits of itself
> behind.
>
> Don't re-install a firewall until everything is working.
> --
> 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
>
 
 
Steve





PostPosted: Wed Feb 09 15:29:08 CST 2005 Top

Windows XP Network >> Peer to Peer network problem pinging In article <EMail@HideDomain.com>,
"Nicko" <EMail@HideDomain.com> wrote:
>> >I have an XP Home host and a 98se client.
>> >
>> >the client can ping 127.0.0.1 and 192.168.10.2 (it's own IP address)
>> >
>> >However....the host can ping 127.0.0.1 but when i try to ping 192.168.10.1 i
>> >get the now dreaded "reqyuest timed out".
>> >
>> >At the same time my task bar is showing that my LAN is connected and running
>> >at a speed of 100 Mbps.
>> >
>> >in desperation i've bought another network card and put it in a spare slot
>> >to se if this will fix the problem, but this just tells me that i have a
>> >cable unplugged and refuses to work........
>>
>> I assume that "192.168.10.1" is a typo and that you've actually pinged
>> "192.168.0.1" on the host.
>>
>> When a computer can't ping its own IP address, the problem is probably
>> caused by a firewall program.
>>
>> While troubleshooting, disconnect from the Internet and un-install
>> (don't just disable) all firewall programs. After un-installing, go
>> to Start | Run | Msconfig | Startup and disable any remnants of
>> firewalls. For example, ZoneAlarm sometimes leaves bits of itself
>> behind.
>>
>> Don't re-install a firewall until everything is working.
>
>hi,
>
>no it's not a typo. when i run "ipconfig /all" that's the ip address i get.
>i've also tried taking down the firewall but to no avail. not tried
>uninstalling though. i've been told to uninstall tcp/ip but can't see how to
>do this, do you think this would help? sorry if i'm slow to respond but it's
>8.45pm in the uk!

Did you use Internet Connection Sharing to set up client and host
computers? If so, it should assign 192.168.0.1 to the host and
192.168.0.x to the client. If you manually changed the addresses
assigned by ICS, all kinds of strange behavior could result. If
that's the case, disable ICS, re-enable it, configure the client to
obtain an IP address automatically, and don't change any other
settings.

If you've installed a firewall program, un-install it as I described
above while troubleshooting.

If, after trying the other things that I suggested, you think that
TCP/IP might be damaged, try these procedures:

For original Windows XP and Service Pack 1, follow the steps in the
section "How to Recover from Winsock2 corruption" as shown here:

How to determine and recover from Winsock2 corruption
http://support.microsoft.com/kb/811259

For Windows XP Service Pack 2, type this line at a command prompt:

netsh winsock reset catalog
--
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
 
 
Nicko





PostPosted: Wed Feb 09 17:35:01 CST 2005 Top

Windows XP Network >> Peer to Peer network problem pinging can now ping, but not across network?

"Nicko" wrote:

> Hi,
> i am in desperate need of help or i will go insane!
>
> I have an XP Home host and a 98se client.
>
> the client can ping 127.0.0.1 and 192.168.10.2 (it's own IP address)
>
> However....the host can ping 127.0.0.1 but when i try to ping 192.168.10.1 i
> get the now dreaded "reqyuest timed out".
>
> At the same time my task bar is showing that my LAN is connected and running
> at a speed of 100 Mbps.
>
> in desperation i've bought another network card and put it in a spare slot
> to se if this will fix the problem, but this just tells me that i have a
> cable unplugged and refuses to work........
>
> GRRRRRRRR