Thread: Lan

**Pedro_The_Swift** · 17th July 2007, 11:22 AM

thought I'd give this another go,,

two XP SP2 PCs
one, extra clean,(GREENY) nothing but XP.

the other (BLUEY, we are not big on numbers here,,,)has a, er few extra things on it,,

greeny has an ASUS A7V333 so no lan chip,, but has a NEW network card installed and after running the wizard tells me there is no incoming connection, also no connection icon in tray.(box is ticked)

bluey has a gigabyte 7vm400am-rz
basicaly, its all "on-board"-- LAN is handled by a "VIA vt6103" chip.

NEW (this morning) network crossover cable.

during the network (BLUEY) wizard it tells me a cable is unplugged(which tells me I've just wasted my money on a new cable

as this is the same message I got last time).

yes I DO have another network card,, two infact,
one is identical and the other is an old D-link.
swapping hasnt helped.

switching firewalls off makes no difference, [it is interesting that windows now acknowledges other
firewalls and virus software

]

I'm getting faster at hitting this particular brick wall

any ideas?

**Pedro_The_Swift** · 17th July 2007, 11:42 AM

hmm,,
could it be??

one end ethernet,,
the other not?

**Captain_Rightfoot** · 17th July 2007, 11:57 AM

When you plug the cable in you should see lights flashing on the card. If not, you have a problem with the cable or the cards.

If you do have flashing lights then it's a software issue.

First thing is look for the lights!

**p38arover** · 17th July 2007, 12:11 PM

I assume you are setting up a peer-to-peer connection.

Does your card support automatic sensing so you don't need a cross-over cable?

Ron

**Pedro_The_Swift** · 17th July 2007, 12:23 PM

yep two green lights,,
now.

but!

I put the second lan card into bluey,,
disabled the on-board lan,

now I get a second network symbol, but it has "limited connectivity"
when I ask it to repair itself
it tells me it cant renew its IP address,,

**Brisruss** · 17th July 2007, 01:18 PM

Did you allocate an IP Address on each? Use something like 192.168.1.1 and 192.168.1.2 and see how they go. You also need to have File and Printer Sharing for Microsoft networks. Make sure the network card speeds and duplex settings match.
Cheers,
Russ

**Pedro_The_Swift** · 17th July 2007, 02:16 PM

yup I had to add it in, in device drivers,
I thought XP auto allocated IP address?

and then tried a "repair" on the connection,,

still needs an ip address

**scrambler** · 17th July 2007, 02:17 PM

Originally Posted by Brisruss

Did you allocate an IP Address on each? Use something like 192.168.1.1 and 192.168.1.2 and see how they go. You also need to have File and Printer Sharing for Microsoft networks. Make sure the network card speeds and duplex settings match.
Cheers,
Russ

I'm not used to doing Perr-to-peer in fancy operating systems. The sure-fire way (but fiddly) is to get into the settings and manually set the addresses to something like the above, and set the subnet mask to 255.255.255.0

What is probably happening is that the subnet masks on the two computers are not in agreement. E.g. one is defaulting to an address of say 10.0.0.1 and the other to 192.168.1.1 but their masks (which will probably be 255.255.0.0) don't allow them to speak to each other. If you manually set the addresses and the subnet mask yo shold get communication.

**scrambler** · 17th July 2007, 02:18 PM

Originally Posted by Pedro_The_Swift

yup I had to add it in, in device drivers,
I thought XP auto allocated IP address?

and then tried a "repair" on the connection,,

still needs an ip address

That could be the problem - they are BOTH allocating the addresses. But more likely the subnet masks and addresses are not in agreement.

**Pedro_The_Swift** · 17th July 2007, 02:21 PM

hmm ok,, and where do I find subnetmasks?

Thread: Lan

Thread Tools

Lan

Bookmarks

Bookmarks

Posting Permissions