LAN problems

May 2, 2009 at 08:59:36
Specs: Windows XP
hi
i have 2 pc connected to each other using
crossover ether cable.
after connecting both shows "connected"
popup .

System Description:
1st system is windows 2003 server.
- IP configured is 192.168.100.1

2nd system is windows Xp pro.
- IP configured is 192.168.100.2

now, when i ping to second system from 1st i
get "Request
Timeout."

and when i ping from 2nd PC to 1st PC i get
Reply from
192.168.100.1

and now, a strange thing is:
when i try to open a shared file in 1st PC i m
able to download and
upload files from 2nd pc to 1st.

but, my 1st pc cannot find my 2nd PC.

can any body solve this problem.

I have changed the NIC card on both pc and
installed the driver
successfully.

what ever changes i do i get same results

1st PC -> ping -> 2nd pc -> output ->
Request Tiemout
2nd PC -> ping -> 1st PC -> output -> Reply
received.


See More: LAN problems

Report •


#1
May 2, 2009 at 20:22:53
I've never used a crossover cable but I would disable the firewalls first.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
May 2, 2009 at 22:07:08
i have disabled the firewall Service on both system

Report •

#3
May 3, 2009 at 05:31:06
Are either of the PCs connected to the internet?

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
May 3, 2009 at 08:44:00
no
none of them if connected to internet
kindly give the suggestion in more than 1 line
i hope we are not chatting
i m looking for good solution


Report •

#5
May 3, 2009 at 08:52:22
Ok, my last suggestion is to create a .local domain on the 2003 server & join the XP box to the domain. That should do it.

How do you know when a politician is lying? His mouth is moving.


Report •

#6
May 3, 2009 at 09:07:25
first thing.

i think you should read my problem again.

when i m not able to do success connection than how can i
create a domain and be connected?


Report •

#7
May 3, 2009 at 19:02:27
I read your post many times already. As I said, I never used a crossover cable but I thought some basic networking techniques might work. Apparently, they didn't. I have no other suggestions unless you want to buy a router.

How do you know when a politician is lying? His mouth is moving.


Report •

#8
May 4, 2009 at 04:41:25
Hi,

perhaps your crossover cable is not ok. But even if it is ok, crossover cables sometimes behave weird. You should definitely spare your time and nerves and buy a switch. 5 port or 8 port switch will most probably solve your problem with connectivity. This switch and two straight-through lan cables and you are good to go. My advice is never to use crossover cables because I had myself a few totally awkward situatiations/problems with them.


Report •

#9
May 4, 2009 at 04:51:24
Thanks Edin
but i tried Switch also and the port you said
but still no success.

i tried one more practical.
i connected my friends laptop to my server PC and it was
working fine. both gave reply.
but when i connected my other pc with that laptop it didn't
give reply.


Report •

#10
May 4, 2009 at 07:19:02
Whenever connecting like devices it's always recommended to use a crossover cable. These days most switches are auto MDIX capable and it's not absolutely necessary (as it was in the old days before auto MDIX) but even if you have auto MDIX capable equipment, it's still a very good idea to use one. At the very least, it's one less thing to troubleshoot if/when something goes wrong.

In this case, we're talking about two computers and I have a sneaking suspicion the built-in NIC on a laptop may very well not be auto MDIX capable so a crossover would be required.

i tried one more practical. i connected my friends laptop to my server PC and it was working fine. both gave reply. but when i connected my other pc with that laptop it didn't give reply.

This tells me the issue is your other PC. Again, double check you have no firewall running and blocking the connection and verify the NIC is working and correctly configured.


Report •


Ask Question