Does Ping(ICMP) use both TX and RX?

[evik]

Just want to isolate my network problem, could be firewall, could be
hardware, could anything..especially when I don't know that much about
network.

Problem: Unable to ping its own IP address(tried both DHCP and static
assignment), comes back Request Time out.

Situation: New computer directly connected to an old laptop running
Win98, using a crossover cable.

Things I have tried:
1, Able to Ping the laptop/notebook from my new computer no problems.
2, Able to ping my laptop from my new computer using HOSTNAME.
3, Laptop is unable to ping the new computer.
4, Laptop is unable to ping the new computer using HOSTNAME but is able
to resolve the HOSTNAME into the correctly assigned ip address.
5, Plugged my laptop into another desktop running XP using DHCP and
connects thru fine using the same crossover cable, both machine can
talk to each other no problems and file sharing is working sweet.

Haven't try connection the two desktops using the crossover cable,
can't be bother to move them. But I'm trying to determine from the fact
that the ICMP ECHO request from my new desktop is successfully
requesting and receiving a response to my laptop, should mean that
there is physically nothing wrong with my hardware (ie. my onboard
network is fine)?? is this correct? or does the ICMP not use TX or RX
but one of the other diagnostic wire?

 

[evik]

Replying to myself....Obviously I haven't spend much time resolving
this problem, a quick search on the internet shows that ICMP Echo
request and reply does make use of the TX and RX...so it seems unlikely
that I have a physical hardware problem.

Will look into it some more tonight but I did turn off Firewall on my
XP desktop...

 

[evik]

Had time to look at it again. Just for those ppl who had similiar
problems, this particular issue was due to Norton Anti-virus program. I
don't know the proper settings to have everything coexisting in harmony
but at least I got it working by turned the firewall settings off for
my connecting Laptop IP address.

NOTE: previously I tried turning the firewall off in XP but still need
to do so in security softwares running on your machine. Obivously I
didn't install or knew that Norton Anti-virus was installed on my new
PC.

 

[q_q_anonymous]

Had time to look at it again. Just for those ppl who had similiar
problems, this particular issue was due to Norton Anti-virus program. I
don't know the proper settings to have everything coexisting in harmony
but at least I got it working by turned the firewall settings off for
my connecting Laptop IP address.

NOTE: previously I tried turning the firewall off in XP but still need
to do so in security softwares running on your machine. Obivously I
didn't install or knew that Norton Anti-virus was installed on my new
PC.

yep. there are no diagnostic wires.
typical 'ethernet' cables (cat5/cat5e i guess) have 8 wires. 4 twisted
pairs. 1 pair for TX, 1 pair for RX. and the other 2 pairs don't do
anything. They're for the future (or present - Gigabit ethernet).
perhaps nobody responded before 'cos they didn't see the connection
you were making. As you can see, the connection you made was way off!!!

a little knowledge can be dangerous

 

[evik]

Thanks for taking the time to post your ...comment(I guess)

But I disagree with the reason for lack of response...After solving the
problem myself, I feel that the problem description I stated in my
first posting should of prompted any experienced XP user to the answer
straight off. It seems pretty straight forward to me, once I was able
to not worry about the issue being a hardware problem.

And what's all that about "...a little knowledge can be dangerous"
so what if it has taken me a 5 second search on google, if you don't
question and try things out yourself, you will never really learn.

 

[q_q_anonymous]

Thanks for taking the time to post your ...comment(I guess)

But I disagree with the reason for lack of response...After solving the
problem myself, I feel that the problem description I stated in my
first posting should of prompted any experienced XP user to the answer
straight off. It seems pretty straight forward to me, once I was able
to not worry about the issue being a hardware problem.

And what's all that about "...a little knowledge can be dangerous"
so what if it has taken me a 5 second search on google, if you don't
question and try things out yourself, you will never really learn.

if you had just said you can't ping then it'd have been fine.

Once you added all that stuff about DHCP , people couldn't see the
relevance, it started to look more complicated than it actually was.
People didn't understand it anymore.

You were talking about technologies and people probably thought you
know more than them plus they didn't udnerstand why you were saying
what you were syaing and they couldn't help you.

The whole DHCP thing was irrelevant, because that's just how the comp
gets the IP. I hadn't heard of "static assignment" , it's to do with
DHCP and had nothing to do with your problem.

To answer your post, somebody would need enough knowledge to see
through all the junk you wrote.

Then going into crossover cables and TX and RX. What's the point if
you don't know what it's all about. You had no idea how to narrow down
the problem. Let by adding all that stuff, you confused people into not
seeing the problem, and perhaps that
a) you knew what you were doing and they can't tell you anything you
don't already know.
b) they couldn't unravel the mess you created, didn't have the
knowledge. The stuff you were talking about was not windows xp at all.
You were talking about the wiring of cat5[e] UTP cables and tcp/ip
protocols and DHCP servers. Networking is a big subject. Your question
contained too many distractions on too many different areas.

You gave ithe impression that if somebody asked
"did you turn the firewalls off" or "are you running any software with
a firewall"
that you'd say
"of course , I did, but the TX wire is transmitting ICMP at 10Mbps so
it can't be...."


So, without good knowledge of all that stuff, it looks difficult to
reason with you.

It wasn't clear that all of that was absolutely irrelevant. What kind
of person would talk about all that when they haven't turned their
firewall off.

A typical experienced XP users's eyes would have glazed over.
Networking is a huge subject