:P Lan-ning

Jeez I had replied to this thread,where did my reply go?

Anyways can you give us a few details regarding the TCP/IP settings,workgroup name & firewalls present if any?That should get us started to troubleshooting.

I assume all the physical connections[crimping & the network cards] are working fine.
 
Yea sme posts got deleted......
Had replied to u tht time....

Here it is again,

1.there r no firewalls...network cards working fine
2.Group is Worlgroup for all.........IP address r 192.168.0.1(being myself)....the rest .2, .3 .....

3.evry PC can ping itself , but not ny1 else.....

Lemme know if u want ny othr info :huh:
 
What is the result that you get when you ping some other host on the LAN?

On top of my head I believe its a physical connection issue.Have you checked continuity between the two end of the crimped CAT5 cable?

Check it with a Multi-meter & fix the cable if required i.e re- crimp it.
 
Okey....

whn i ping sme1 i usually get the message .......request timed out..
okey my friend had used a multimeter to check the connectivity ....it was fine..

How to use a multimeter btw to check continuity?? ;)
also now 1 person whose at a distance of 65 meters is connected at 10mbps....but at 100mbps, he gets request timed out...also still cannot share files thou....

btw now i hav a 65mtr wire lying at my place.....got a frnds pc, he too got connected at 10mbps...v played sme games nd shared sme files......
now whn i laid his wire ....it gives request timed out smetmes??

help appreciated soooo much Digen:hap2:
 
I would suggest getting another pc at your premises & pulling that same wire & connecting both machines through a hub/switch or whatever you have been using.

Then look at the ping output & report back here.

On top of my head I hope there arent any strong bends or cuts on the wire which could cause signal distortion & thereby resulting in lost network connectivity.

Oh one more thing carry out the below commands at both the computer nodes & post the result here.

1.start>run>cmd>ping 127.0.0.1

2.start>run>cmd>ping "IP address assigned to the NIC[Network Interface Card]"

If you have a DHCP server,then temproraily assign a static IP & check the result with the above command.
 
okey here goes...

1.pinging 127.0.0.1 ,

reply frm 127.0.0.1 ...bytes 32 time<1ms ttl = 128 ...4 times...:clap:

2. pinging self ...192.168.0.5

reply frm 192.168.0.5 ...bytes 32 time<1ms ttl = 128 ...4 times...:clap:
now whn pinging 192.168.0.1

request timed out ........4 times :rofl:
digen said:
If you have a DHCP server,then temproraily assign a static IP & check the result with the above command
Click to expand...

bout a pc at my place still same prob......will check for cuts again, but thr arent ny:cool2:
 
digen said:
I would suggest getting another pc at your premises & pulling that same wire & connecting both machines through a hub/switch or whatever you have been using.
Then look at the ping output & report back here.
Click to expand...
You didnt mention anything about this? :)
 
Did tht with 1 PC today...didnt work, it self pings but gives request timed out whn pinging sme1 else........

BTW today whn i was using a lan chat system, i asked 1 of my friends to start the chat.....nd keep sending msgs......i did the same on my side, so frm those 1 person whose bout 100mtrs away cud send msgs...ie ....v were getting his msgs ,but cudnt send him thru the messenger :huh:
 
Back
Top