HELP! Pier to Pier Networking

[[GA] KillmachinE]

I have just brought 2 x 3com network cards, i have connected them straight in using an RJ45 cable, the cards are properly installed and have there drivers installed ok, on both bachines the cards are bound to IPX and seem to be fine, when i open a game though e.g red alert and goto network game i cannot see the other machine, also when i open network neighbourhood i dont see the other machine (both connecting to the same workgroup btw)

Any suggestions or ideas?

Thanks

------------------
[GA] KillmachinE
extreme@barrysworld.com

 

[Durzel]

Pier to Pier Networking is surprisingly easy to configure, once you know the basic settings.

First off you will need to source a rather long Ethernet/RJ45 cable (in excess of 2 kilometres) that is used to span the lake, pond and/or ocean between the originating, and terminating piers.

Locating the relevant ports on the piers can be somewhat difficult, although in most cases simply walking along either side will reveal the location of the ports. If you are using a standard wooden pier you may find yourself having to add a supplementary 'deck' or 'plank' to accomodate the network cable, however, if you have one of the more modern, metal piers - you should find that the port comes ready equipped.

After having set up the physical link between the two piers you will need to setup Windows Networking to use TCP/IP (Transmission aCross Pond) protocol. This is a relatively painless task.

After having done this you should be able to initiate a pier-to-pier connection between both machines (assuming of course the line between the piers hasn't been accidentally severed by a boat or other marine craft).

Hope this has been of some help.

Daz.

 

[[GA] KillmachinE]

Nice one mate!

So i cant use IPX? If i set up TCP/IP will i be able to share files, and will it mess with the internet connections (will i have to give each machine an I.P?)

Thanks anyway, i'll give it a go

------------------
[GA] KillmachinE
extreme@barrysworld.com



[This message has been edited by [GA] KillmachinE (edited 27 May 1999).]

 

[[GA] KillmachinE]

Right, here we go again. My PEER to PEER network is coming along a bit better now, i have both computers set up perfectly (as far as i can see) i can goto network neighborhood and see this machine but not the other, and vice versa with the other machine, its as if the cables weren't plugged in (they are i checked!)

Any ideas as to the cause?

------------------
[GA] KillmachinE
extreme@barrysworld.com

 

[[SMEG]Kryten]

you got file sharing enabled m8??


------------------
[SMEG]Kryten
nickspc@hotmail.com
http://www.bigwig.net/dwarfers

 

[Rup]

Yes. RJ45 is supposed to be connected via a hub.

I've heard that it's possible to get away with a direct-connection if you cross over two wires inside that cable. I've also heard that such leads are available anyway for hub-to-hub patches, although I'm not sure I've seen any advertised and they'd probably only be in short lengths. Wouldn't do any harm to ring someone up and ask about one, though.

However, if you do go for that option, you'd never be able to add any more machines to your network. If you don't mind shelling out another 40 quid or so, you can get a cheap 10Mbps hubs and a short RJ45 lead. OTOH, it might be possible to get a 100MBps connection if you go direct... but I don't know enough about such things. One for Utumno, I'd imagine.

This is, of course, assuming you've got 10/100 cards. If you only have 10MBps cards, you'll probably have BNC connectors too -- then all you need is two terminators and a BNC cable instead (chances are you'll already have T-pieces with the cards). However, most people use RJ45 now... and usually only 10MBps because of the price-hike to 100MBps hubs.

Rup.

 

[[GA] KillmachinE]

Yep, as far as i can see both PC's are set up exactly the same and it should be working

When i brows the network all i see is the machine im on, i see the workgroup too, if i click it i see the computer im on again ! same thing happens on the other machine so i think it may be the cable? (Twisted pair)

What do you think?

------------------
[GA] KillmachinE
extreme@barrysworld.com

 

[[GA] KillmachinE]

Well, i was told by the place that i brought the cable that its whats called a 'fly cable' and is actually meant for connecting two PC's ?!?



------------------
[GA] KillmachinE
extreme@barrysworld.com

 

[Rup]

Oh, ok... soz. A few other pointers, then.

Firstly, don't use network neighbourhood to detect whether the machines can see each other. Microsoft have some system whereby machines periodically announce their presence on the network and elect a "master browser" which keeps track of other machines, workgroups, etc., and network neighbourhood doesn't work properly until this gets sorted. If you really do want to use Microsoft Networking to test things (you don't have TCP/IP set up, for example), it's quicker to go to "Find Computer".

Secondly, IPX... in my experience at small lan parties, Microsoft's "auto" frame type is rubbish. Most people use 802.3; I have a feeling that one of the others is considered technically superior, but 802.3 is the norm. I think it's on the "advanced" tab in IPX settings.

Thirdly, TCP/IP.... each PC must either be assigned a number, or be able to ask another machine on the network what its number is. Since you won't have one of these set up, you'll have to assign your own. There are a few sets of numbers set aside for local lans, including 10.x.x.x and 192.168.x.x. Again, 192.168.0.x seems to be the norm -- so give one 192.168.0.1 and the other 192.168.0.2, for example. Since you won't have a local nameserver, create a "hosts." file in each PC's windows directory along the lines of:

192.168.0.1 killmachine
192.168.0.2 littlebrother

or whatever the machines are called. Then you can use "ping killmachine" and "ping littlebrother" to check the connection, and "connect killmachine", etc. in quake. You could always use "ping 192.168.0.1" anyway, but this is more friendly.

Oh, netmasks... these are used to determine whether a destination address is on the same network as you or it needs to go through a gateway. Since your addresses are the same apart from the last number, you'll need to use 255.255.255.0 (although 255.255.0.0 would also do) -- you just need to tell the PC what range of addresses are available over the network, or your dialup might not work (it'd try to talk to Barrysworld over your LAN not your modem).

You should be able to leave everything else on the TCP/IP properties tabs alone.

Hope this helps!
Rup.

[This message has been edited by Rup (edited 27 May 1999).]

 

[[GA] KillmachinE]

i'm pretty sure i've got it sorted now, thanks for all the help ppl. The problem is my cable, its NOT for back to back connections but as Durzel said before is for use with a hub, i have to either: modify the cable to make an ethernet crossover cable or i can just go BNC, whats the difference?

Also, any help with this crossover cable would be most appreciated

Cheers again guys

------------------
[GA] KillmachinE
extreme@barrysworld.com

 

[Mr B]

I'll get me coat.

/me vows to read the WHOLE thread before making any more inane and thoroughly unsuccessful attempts at humour.

[This message has been edited by Mr B (edited 28 May 1999).]

 

[Tui]

The crossover cable needs to have pairs 1 and 2, 3 and 6 at one end appear as 3 and 6, 1 and 2 at the other.
Regarding IPX, the auto setting needs to see IPX frames to determine what type to use. Since you won't have this, you will need to set the frame type to a particular value, 802.2 is now the norm.

 

[RedVenom]

m8,

I would recommend getting an ickle hub if you can - 4 ports wont cost much, and will be dead handy if ever you want to expand your network... or hold LAN's

But if your only looking for connecting the two machines (and only ever 2 machines), then use the cable... sound advice that

Red

 

[frankie]

urr me is stupid
say i wanted to goto a lan party, all i would need was a standerd 10/100 mbit pci network card right ??
what bout the cable, what kind, and how bout software setup ??
see i dont know anything about networking but i wish to learn from u guys

can u spare some time and reply to this ?
cheers
=di=dr_f
icq 18155776

 

[[GA] KillmachinE]

Thank you Mr B, i thing Durzel gave a fairly pisstaking and amusing first reply to this, have a read

Also, i managed to get the proper RJ45 cable and am not kicking the old mans arse at Q2 (althoigh he rocks on C&C:Red Alert)

Thanks for the halp.

------------------
[GA] KillmachinE
extreme@barrysworld.com

 

[Rumpy]

Glad to hear you have it sorted, I was about to give you the fix when I read you had done so

For those that don't understand why a "standard" drop cable wont work for this it's pretty simple.

RJ45 Ports on any NIC are configured to SEND down 1 pair (inside the cable) and RECEIVE on the other pair, so with a STRAIGHT THROUGH cable like you originally had you were basically connecting send to send and receive to receive. Hence you needed a Twisted cable. The reason that a straight through cable works to a hub is that on a hub the send and receive pairs are a mirror image of the 1's on a Card, this makes cables nice and cheap to buy.
The idea of using BNC cabling is not a bad 1 for VERY small networks , but for it to be efficient you need T pieces, and Terminators too, also the cable is a bit more unwieldy than CAT5 as well as being lower bandwidth

Techy shite over