Computing.Net > Forums > Networking > XP Pro & Home with Crossover cable

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

XP Pro & Home with Crossover cable

Reply to Message Icon

Name: Conor Gavin
Date: January 12, 2004 at 12:54:57 Pacific
OS: XP Pro
CPU/Ram: P4 / 512 MB
Comment:

Hi, I would appreciate any help or suggestions on the following:

Ive been trying to network 2 PCs, one with XP Pro and 1 with XP Home, using a crossover cable. One has an on-board Intel Pro/100 VE Network card, the other has a Realtek RTL 8139 Family PCI network card.

Firstly I tried running the setup wizard on both PCs, but that didnt work. It said it was connected, but neither computer could see the other. They couldnt ping each other either.

I then tried setting the IPs manually, to 192.168.0.1 and 192.168.0.2 with subnet 255.255.255.0 on both. Again, neither PC could see or ping the other. I then tried IPs 10.0.0.1 and 10.0.0.2, but no luck.

Ive tried sharing internet conenctions, not sharing them, one IP on automatic and one on manual, Ive uninstalled Zone Alarm on both, reinstalled Windows on both, and yet it still wont work. I borrowed 2 working network cards, installed them, tried again and no luck. I also gave my friend the cable, got him to test it out on his network, and it worked fine.

Im pretty much out of ideas as to whats wrong. All I want to do is share files, and if possible, but not esential, would be to share dialup internet connection or play a game or two.

Any ideas?




Sponsored Link
Ads by Google

Response Number 1
Name: jillpickles
Date: January 12, 2004 at 13:00:14 Pacific
Reply:

well try to get it working without zonealarm first.... zonealarm, unless you change your zone settings will block most everything

are you sure it is a crossover cable?

i wouldnt bother with the wizard...

set the one to 192.168.0.1 and the other to 192.168.0.2 just like you had it and try to ping each other

OHHHH, probably had the xp firewall enabled on the connection? is that possible?


0

Response Number 2
Name: Conor Gavin
Date: January 12, 2004 at 13:17:40 Pacific
Reply:

Zonealarms uninstalled on both PCs now, and the XP firewall is off too. The ping just times out when I try 192.168.0.1 and 192.168.0.2.

Im also sure the cable is a crossover. My friend has 2 Win98 PCs networked by crossover. I got him to try the cable and it works on his system.


0

Response Number 3
Name: jillpickles
Date: January 12, 2004 at 13:24:49 Pacific
Reply:

make sure netmask is set correctly on both.

um....

can they ping themselves?

can they ping 127.0.0.1?



0

Response Number 4
Name: mbrook
Date: January 12, 2004 at 13:31:18 Pacific
Reply:

When you go to Network Connections and look at the adapter under LAN or High Speed Networks is your adapter alive or with a red x through it?

Have you checked the drivers on the cards to make sure they are good or installed correctly. I don't know how old your network cards are, are they compatible with XP?

Look in Device Manager and see if there is anything with a big ? beside it.

One more thing on the Pro box Right click on My Computer and click on Manage. Look in Event Viewer \ Application or System to see if your getting some error messages that would help you find the problem and fix it.


0

Response Number 5
Name: Conor Gavin
Date: January 12, 2004 at 13:32:32 Pacific
Reply:

Yes they can both ping themselves.

Whats netmask? How do I set it and what should it be?


0

Related Posts

See More



Response Number 6
Name: mbrook
Date: January 12, 2004 at 13:38:05 Pacific
Reply:

Subnet Mask. Its right up under your IP address. Use 255.255.255.252 for both computers.


0

Response Number 7
Name: mbrook
Date: January 12, 2004 at 13:47:44 Pacific
Reply:

I just re-read your first post you were using 255.255.255.0 I THINK that is fine also. I'm using WildPackets IP Subnet Calculator to see what Subnet will work and it processed out 255.255.255.252


0

Response Number 8
Name: Conor Gavin
Date: January 12, 2004 at 13:54:00 Pacific
Reply:

I changed the Subnet to 255.255.255.252 and it still wont work. Theres no problems in Device Manager on either PC, and the drivers should be fine. I tried different Network cards at one stage and it still wouldnt work.


0

Response Number 9
Name: Conor Gavin
Date: January 12, 2004 at 13:59:31 Pacific
Reply:

In network connections, theres no red x either. It shows the Local Area Connection as connected, and it notifies me that a cable is unplugged if I turn off one of the PCs. And there doesnt seem to be anything of note in Event Viewer.


0

Response Number 10
Name: mbrook
Date: January 12, 2004 at 14:07:24 Pacific
Reply:

This is what I would do. Step back and start from the beginning and make sure of a couple of things.

Do both computers have different names but are in the same workgroup.

Do both computers have different IP addresses and are in the same subnet.

Don't have on DNS or WINS on.

Make sure that File and Print sharing is on both computers.

Go to Explore \ Tools \ Folder Options \ View and scroll down to the bottom and put a check in "Use simple file sharing"

The user you log in as on both computers put a that user account in the other user account.

Then try to ping both computers. Make sure all firewalls are off. Including the one from XP. Network Connections \ select your adapter \ Properties \ Advanced tab \ and make sure that the XP firewall is unchecked. Once you figure this all out then you can add these back in.


0

Response Number 11
Name: mbrook
Date: January 12, 2004 at 14:11:18 Pacific
Reply:

While making sure no software firewalls start back up reboot. Reboot in windows does wonders.


0

Response Number 12
Name: Conor Gavin
Date: January 12, 2004 at 14:16:50 Pacific
Reply:

Yes, both PCs have different names but same workgroup.

Yes, they have different IPs but same subnet.

DNS and WINS are off.

Cant seem to find any option there for "Use simple file sharing" on the XP Home machine, but it is there and ticked on the XP Pro machine.

Not sure what you mean by the next point. Do you mean have the same username and password on both PCs for the login? If so, thats already the case. Or should they be different?

XP firewall is definately off, and Zonealarm is uninstalled.


0

Response Number 13
Name: jillpickles
Date: January 12, 2004 at 14:19:48 Pacific
Reply:

i would have to question the cable....
but i know you said you are sure so....

check properties of the lan connection and make sure xp firewall is off

check taskmanager and make sure no firewalls are running, i think the name of the zonealarm firewall is vsmon? i THINK...

havent ever installed any other firewall engine have you?

besides that i think you have stumped me

describe the ends of your cable your are using, the colors...

just to satisfy my curiosity
;)


0

Response Number 14
Name: Conor Gavin
Date: January 12, 2004 at 14:23:45 Pacific
Reply:

Ive rebooted many many times...


Not sure if this is related, but anyway, just there for the last while, I tried disabling the XP firewall on my dialup internet connection too. Network still wont work though. However, these messages have been popping up after a few minutes ever since:

"Generic Host Process for Win32 Services has encountered a problem and needs to close. We are sorry for the inconvenience."

Followed by:

"This shutdown was initiated by NT AUTHORITY\SYSTEM

Windows must now restart because the Remote Procedure Call (RPC) service terminated unexpectedly"

At which point the PC promply turns itself off. Is there any connection?


0

Response Number 15
Name: mbrook
Date: January 12, 2004 at 14:25:02 Pacific
Reply:

Yes, thats what I meant. Sorry I didn't really know how to type that out, but you got the point.

Then I'm at a loss. Your sure the cable is a crossover cable and not a patch cable? You sure its not bad. I know you checked that but I would look one more time.

And both cards are a 10/100 cards right?

Like I said before then I'm at a loss. Sorry I wasn't much help. Maybe someone else could jump in.


0

Response Number 16
Name: jillpickles
Date: January 12, 2004 at 14:31:52 Pacific
Reply:

yea you got the welchia/blaster/naichi

rpc exploit

ALWAYS have a firewall between you and the net or ELSE!!! or make sure you have all the updates from MS

and if you have it then chances are any computer you connect with has it as well...

:(


0

Response Number 17
Name: Conor Gavin
Date: January 12, 2004 at 14:32:44 Pacific
Reply:

Okay the cable:


Colours from left to right are:

Orange, blue, green, (nothing), (nothing), brown, (nothing), (nothing).

On the other end of the cable:

(nothing), (nothing), blue, (nothing), (nothing), orange, brown, green.


Is that right? I did give it to a friend to test and he said it worked...


0

Response Number 18
Name: Conor Gavin
Date: January 12, 2004 at 14:34:56 Pacific
Reply:

Yeah, Norton Anti-virus just detected something and deleted it. That would hardly stop the network from being set up, would it?


0

Response Number 19
Name: jillpickles
Date: January 12, 2004 at 14:37:39 Pacific
Reply:

this shoudl be working...

open a command prompt and type

ipconfig

and see what it is telling you the ip address and mask is?

one more thought

set them to "obtain ip address automatically" and reboot with the cable connected....

then open a command prompt on each computer and run the command
ipconfig
see what ip address they have been assigned
and then see if they can at least ping each other..


0

Response Number 20
Name: Marshe
Date: January 12, 2004 at 14:39:55 Pacific
Reply:

Why dont you just get a hub?


0

Response Number 21
Name: jillpickles
Date: January 12, 2004 at 14:45:16 Pacific
Reply:

HOLD UP!!!

is that the wires with the little clip pin facing down?

cant stand when people dont wire it according to standards with all colors...

I may be crazy but off the top of my head that doesnt sound right at all....



0

Response Number 22
Name: jillpickles
Date: January 12, 2004 at 14:48:02 Pacific
Reply:

sorry to run you around but i am worried aboutthe cable

put the ends side by side with the little clip pin facing down on both and describe the colors again please.....

i think we got it

is this a cat5 crossover cable? where did you get it at?



0

Response Number 23
Name: jillpickles
Date: January 12, 2004 at 15:00:06 Pacific
Reply:

if one of those was pinup and one was pindown then that sounds right....

so i am back to

open a command prompt on each and type

ipconfig

and see what it is telling you the ip address and mask is?

one more thought

set them to "obtain ip address automatically" and reboot with the cable connected....

then open a command prompt on each computer and run the command
ipconfig
see what ip address they have been assigned
and then see if they can at least ping each other..

im gone for a while.....
goodluck!


0

Response Number 24
Name: Conor Gavin
Date: January 12, 2004 at 15:00:48 Pacific
Reply:

Okay the cable, ends side by side, clips down:

Orange, blue, green, nothing, nothing, brown, nothing, nothing

Green, brown, orange, nothing, nothing, blue, nothing, nothing.

When I say brown on closer inspection it seems to be almost purple...


I hadjust finished doing that ipconfig, so heres what it said anyway:

When it was set manually first it gave:

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.252
Default Gateway . . . . . . . . . :

PPP adapter UTV:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 195.218.108.50
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 195.218.108.50


After restarting and setting it to automatic:


Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.222.238
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

PPP adapter UTV:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 195.218.107.106
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 195.218.107.106


UTV is my ISP by the way.


0

Response Number 25
Name: mbrook
Date: January 12, 2004 at 15:02:36 Pacific
Reply:

The way a crossover cable should look or make.

To make a "Crossover" cable you change the pinout connections on one end of the cable. If you do it on both ends of the cable you have crossed-over the crossover and now have a straight-through cable.

Pins 1 & 2 from one end are connected to pins 3 & 6 on the other end, and pins 3 & 6 from the first end are connected to pins 1 & 2 on the other end. Pins 4 & 5 and 7 & 8 don't change.

The pinouts looking from the bottom of the cat5 ends (White/Orange starts on the left) are as follows:


Standard End

Pin 1 White/Orange
Pin 2 Orange
Pin 3 White/Green
Pin 4 Blue
Pin 5 White/Blue
Pin 6 Green
Pin 7 White/Brown
Pin 8 Brown

Crossover End

Pin 1 White/Green
Pin 2 Green
Pin 3 White/Orange
Pin 4 Blue
Pin 5 White/Blue
Pin 6 Orange
Pin 7 White/Brown


0

Response Number 26
Name: jillpickles
Date: January 12, 2004 at 15:05:42 Pacific
Reply:

cable is correct...

i only see ifconfig on one computer...

are you just changing one computer?

gotta work on both...

set them both to auto and reboot with them plugged up

then run ifconfig on both and see if computer1 can ping computer2



0

Response Number 27
Name: XpUser
Date: January 12, 2004 at 15:10:55 Pacific
Reply:

Conor Gavin and mbrook,

Forgive my intrusion but I couldn't resist putting in this link http://www.ctron.com/support/techtips/tk0231-9.html

There's an illustration at that page that simplifying the ID


0

Response Number 28
Name: jillpickles
Date: January 12, 2004 at 15:16:09 Pacific
Reply:

ok i am out of here

thought setting to auto would at least let us see if windows could auto some ip address and find out if they were seeing each other and not getting assigned the exact same address on both ends which would imply that they aren't seeing each other at all...

i personally would get another cable but that one is wired the way it should be... sort of anyway...enough to work at least...

take care....



0

Response Number 29
Name: Conor Gavin
Date: January 12, 2004 at 15:26:35 Pacific
Reply:

I'll get a loan of a new cable tomorrow. Hopefully that will sort it all out.


Thanks a million for your help guys, I'll post again tomorrow and let you know.


0

Response Number 30
Name: mbrook
Date: January 12, 2004 at 15:50:24 Pacific
Reply:

XpUser, thanks for the link. I'm gone to, I need a beer after that. Hopefully that will be the problem Conor Gavin.


0

Response Number 31
Name: XpUser
Date: January 12, 2004 at 16:22:45 Pacific
Reply:

mbrook -

No problem. I hope Conor Gavin will mark the crossover cables as CROSSOVER, as I do. You know, straight and crossover cables look alike!

Save that beer :-)


0

Response Number 32
Name: mbrook
Date: January 12, 2004 at 16:31:33 Pacific
Reply:

XpUser, your right I might want to save that beer for tomorrow. Nah, I will go buy more. :)

jillpickles, that was some good advice your were giving....... I didn't think about some of what you were saying and then I went Oh Yeah....I forgot about that. Good job.


0

Response Number 33
Name: buddyg1965
Date: January 12, 2004 at 17:50:50 Pacific
Reply:

Do you have files shared on the computers?


0

Response Number 34
Name: jillpickles
Date: January 12, 2004 at 20:29:17 Pacific
Reply:

yea mbrook but you do a MUCH better job of explaining and hand holding

i am a bit rough and crude........worked with computers way more than people and have found I have about become a computer and feel at home with one but people are a different story.......

:)


0

Response Number 35
Name: JackG
Date: January 12, 2004 at 20:46:30 Pacific
Reply:

It would be a good idea to enable the XP firewall on those machines, connect to the internet and go to the Windows Update site and download all of the security fixes for XP on both of them. Good time to kick back and enjoy while they download.


0

Response Number 36
Name: Lawson
Date: January 16, 2004 at 07:59:25 Pacific
Reply:

Ive read all that was said here and i am encountering the EXACT same problem and believe you me its a pain in the ass!...It just doesnt make sense...Any solutions Conor Gavin, Let me know please!...lawson_182@hotmail.com


0

Response Number 37
Name: vitezalex
Date: January 25, 2004 at 15:55:17 Pacific
Reply:

Hello. This page seem to be quite, but unfortunately I have the same problem as well.

I have two computers: xp home and xp pro. crossover cable, and no success connecting them.

Some extra info: the xp pro is a desktop computer. The xp home is a laptop. I can connect the laptop to a 3rd laptop without any problems. The cable is fine, the laptop setting is fine.
When I try to connect the desktop with any of the laptops, I won't see the other computer. I manually configured the IPs, and the computers can see themselves, but not the other.
The network driver on the desktop computer is the latest, just downloaded.

Another comment that might help: when I connect the cable, both computer recognise the network, and set them to 100 M/s. However, both computer only sends out data, but receives nothing.
The desktop computer got a stage further, because it can recognise my laptop's workgroup, but sees no computer in it.

Any idea?

Would be helpful, cheers.
Alex


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: XP Pro & Home with Crossover cable

XP pro to XP pro with crossover www.computing.net/answers/networking/xp-pro-to-xp-pro-with-crossover/13134.html

connect vista and xp with crossover cable www.computing.net/answers/networking/connect-vista-and-xp-with-crossover-cable/36360.html

playing with crossover cable www.computing.net/answers/networking/playing-with-crossover-cable/14994.html