Ducati Sporting Club UK

Ducati Sporting Club UK (/msgboard.php)
-   Idle Chat (/forumdisplay.php?f=102)
-   -   network o/t (/showthread.php?t=11552)

Glyn 05-Nov-2004 19:46

network o/t
 
i was told that i can set up a network between two puters without using a hub. if i used a special cable called a cross over cable(xover)
have purchesed said item pluged it in to both machines(one is on xp one on 98)and i have run new network wizard thing on both but i dont seem to be getting any where.
any ideas peeps

TopiToo 05-Nov-2004 23:30

Hello

I dont claim to know anything about PC, But I connect a PC to a Mac using ethernet, and as long as you have the means for ethernet (normally an ethernet card - I think quite cheap now, installed in both computers - then it all comes down to speed of transfer you need.)

Its a basic network, saying that I would still recommend a HUB to connect to the internet as your main computer needs protection accessing the net, last thing you need is a virus on the slave computer.


regards

TopiToo

PS don't quote me I only know my system and it works for me.

PPS as your location states " lost in space" see you there:burn:

[Edited on 15-07-1968 by TopiToo]

Eamonn 05-Nov-2004 23:55

Glyn, you're correct -an ethernet cross-over cable is all that's required from the hardware side.
Now you need to set up the two machines to communicate to each other - easier said than done!

Points to check:
1) Make sure both systems are using the same workgroup name - on XP go to control panel, system and then click the 'computer name' tab - check the workgroup name here. It's usually either WORKGROUP or MSHOME unless you've changed it.
2) go to Network Connections from the control panel and click on the 'Network connections' option. Find your 'Local Area Connection' and right click then choose 'Properties' Highligh the 'Internet protcol' and click 'Properies' button. Click the option 'Use the following IP address' and in the IP address box below enter the number 192.168.0.1, in the Subnet mask enter 255.255.255.0 - leave all other boxes blank. Click OK on any open windows to close them all off applying the updates as you go.

Now on the Windows98 system you need to do the same things (but they're is slightly different places).

3) Right click 'My computer' icon on the desktop and choose Properties. Go to the 'Network Identification' tab and check the Workgroup name is tha same as in step 1 above. If not you need to change the Workgroup name to match - I can't remember which button it is to do this, but it should be (reasonably) obvious!

4) Do the same thing as step 2 above, but change the IP number to 192.168.0.2.

You may need to reboot the W98 machine to get the new settings to work, the XP doesn't normally need rebooting.

Following that you should be able to see the opposite machine via your 'network neighbourhood' option - however you will need to create a 'share' option on the hard disks to be able to read/change files on one machine from the other.

I think that covers it, but it's a very difficult process to describe partly from memory and not having the system in front of you at the time. If anyone else can add further to this or correct me if necessary, be my guest!

fatduke11111 06-Nov-2004 09:32

Also, make sure the MS Firewall is off on the connection and that you have no other firewall apps running.

You can always put it back on later once you've determined if it works of not.

Glyn 06-Nov-2004 18:39

cheers chaps
have now tried every damn thing i can think of
must be doin summit wrong but dont know what

rockhopper 06-Nov-2004 18:47

You havent plugged your network cable into the phone line socket have you??

(we di the same thing but the other way around!!!)

Glyn 06-Nov-2004 19:16

err no!

rockhopper 06-Nov-2004 20:58

only took me three hours to fix that one!! Well they are very similar looking sockets!

Glyn 07-Nov-2004 09:17

cheers
since i last posted i have upgraded 2nd machine to xp
i now do have some sort of connection as if i turn one machine off the other reports loss of connection
though i still cant do ought

weeksy have tried this and recieved no reply from either

[Edited on 7-11-2004 by Glyn]

Fordie 07-Nov-2004 10:27

Quicker to get your self a "Homing pidgeon" and feed it on bytes, bl00dy computers:lol:they drive you mad, MAD I say. 4D

Glyn 07-Nov-2004 10:49

fordie clear off i don't need a bloomin plumers opinion:frog:

Fordie 07-Nov-2004 11:30

BITCH:lol::lol::lol:

Glyn 07-Nov-2004 13:22

on the main machine ive got the tcp/ip set at 192.168.0.1 255.255.255.0
and on the 2nd machine 192.168.0.2 255.255.255.0
i cant find a box marked ICS to turn off
both machines are using the same workgroup name. and have been assigned names off there own
on the main machine in my network places i can see an icon of my kids machine(the one im trying to network to)but when i click on this icon i get a error saying "\\kids is not accesible you might not have permission to use this network resource. the network path was not found"

on the client machine there is no such icon to show any conectivity at all

Glyn 07-Nov-2004 13:56

network path not found:(
niether machine will ping

Jools 08-Nov-2004 12:22

I used to be a systems engineer, and even taught some network courses one time. Of course that was before I became a manager and had the compulsory management lobotomy.

But from what I can remember, if the hardware is all functioning it should ping. So it looks like either one or both of your ethernet cards is faulty or the crossover cable is duff.

So, can you connect anything else to the ethernet card on each computer (cable modem or whatever) and does it work using that? I remember using diagnostic loopback connectors so that a machine could ping itself, maybe you could try one of these.

My bet is that the crossover cable is defective or simply not a crossover cable, where did you get it from and are you sure it crosses the transmit and recieve?

TP 08-Nov-2004 13:07

Lets try pinging 127.0.0.1 first to see if the IP protocol stack is installed correctly.

If you can ping that (on both machines) and you have both IP's in the same subnet range (if configured above using 192.168.0.1 and .2 using 255.255.255.0 then you have) then try pinging each other, which doesn't appear to be working.

Go to Start - Run and type eventvwr and the event viewer will pop up. Have a look in the system log to see if there are any errors pertaining to the network card or TCP/IP installation. If you can ping 127.0.0.1 and you can't ping the address in the same range then it is highly likely you are experiencing some hardware issues.

[Edited on 8-11-2004 by tp-996]

marko 08-Nov-2004 19:10

I tried just it and i got the same results as you glyn,as a last ditch attempt
I had a go with some old BNC connections and bingo it worked.Glyn just go out and buy a network hub and i'm sure it will work,I don't think the crossover cable is as straight foward as it should be.

Glyn 08-Nov-2004 19:39

cheers
i was all ready to give up on this one
was starting to suspect the hardware myself
the cable has got "xover writen on it and at both ends on the connecters
as for the card i suspected it might be sus so borrowed one from work that was lying around, checked with our it bod first, that it was a working one(though he is clueless)


bearing in mind that im in well over my head here goes
right then when i ping 127.0.0.1 i do get replys on both machines
had a look at eventvwr and there is a regular error called mrxsmb that states
the master browser has recieved a server announcment from the computer KIDS that believes that it is the master browser for the domain on transport NETBT-TCPIP
the master browser is stoping or an election is being forced

hope that means summit to you:puzzled:

TP 08-Nov-2004 19:50

Quote:

Originally posted by Glyn
cheers
i was all ready to give up on this one
was starting to suspect the hardware myself
the cable has got "xover writen on it and at both ends on the connecters
as for the card i suspected it might be sus so borrowed one from work that was lying around, checked with our it bod first, that it was a working one(though he is clueless)


bearing in mind that im in well over my head here goes
right then when i ping 127.0.0.1 i do get replys on both machines
had a look at eventvwr and there is a regular error called mrxsmb that states
the master browser has recieved a server announcment from the computer KIDS that believes that it is the master browser for the domain on transport NETBT-TCPIP
the master browser is stoping or an election is being forced

hope that means summit to you:puzzled:

I wouldn't worry about that mrxsmb error just now - it is just windows way of sorting out which machine owns the list of NetBIOS names on a given network.

If you can ping your 'localhost' address then you are looking at an issue with either the card or your cable.

As you are running Xp I suggest you go to the My Computer icon on your desktop, right-click on it and select Manage. The Computer Management snap-in will pop up, click on Device Manager in the left hand window pane and you should see a list of hardware in the RHS - any yellow question marks? If not, go to Network Adaptors and find your adaptor. Right click on your adaptor and select Properties. A dialog box should open and there will be a section saying Device Status. If this status is saying ok you are starting to look more at the cable and less at the card having a fault **CAVEAT** unless the incorrect driver for the card is installed in which case it could still say it was ok but in reality be completely sh*te!

If I was a betting man I'd be putting money on the cable being duff - they go all the time.

But run through the above and let me know how you get on.

TP

Glyn 08-Nov-2004 19:59

have already looked at device manager for that sort of thing irq conflicts ect

and as i say i have tried a different card and that has made no odds
so it looks like the cable then
i'll get a new cable next w/e and have another go
i wouldn't want to do this for a living
cheers for your time

TP 08-Nov-2004 20:03

Quote:

Originally posted by Glyn
i wouldn't want to do this for a living


:lol: neither would I!!!!

Gissa job?

748mart 08-Nov-2004 21:34

I have found connecting devices via crossover cables can cause problems due to LAN speeds not being negotiated correctly. I would try setting the LAN cards on both machines to say 10mb/s half duplex or get hold of a cheap hub. A cheap hub should cost less than PC world charge for xover cable, 15quid ish.

The cable must be working in one direction as your are picking up packets from 'kids pc' on your PC. If you reverse the cable & same happens then cable should be OK & probably a duff LAN card.

Glyn 08-Nov-2004 21:48

:bouncy::bouncy::bouncy::bouncy::bouncy::bouncy::b ouncy::bouncy::bouncy:

have just installed a new protocol called netbuei or summit like that and instantly have a home network:eureka:

Glyn 08-Nov-2004 23:53

i found a page on the web that told me netbui is often beter for cross over n/work than tcp/ip on its own also that netbui is no longer installed as standard under xp and that you have to copy the files manually into the right folders on your puter

748mart 09-Nov-2004 00:06

Just curious, can the machines now ping each other?

Murray Mint 09-Nov-2004 13:54

You cant ping another machine if your only using NETBUI as the only network protocol, ping is only for IP.

One thing to remember is that you wont be able to use internet conection sharing if you only use NetBUI.

Murray Mint

Glyn 09-Nov-2004 20:58

i can ping
have still got tcp/ip ticked though
and have just tried unticking the netbui protocol and connection is still good?
so maybe it wern't that after all
god knows.
but its all happy at moment, and when my lad gets home from twi kon do were going to have a bit of a death match:saint:

TP 09-Nov-2004 21:08

so you added netbui and now IP works ...

And to think my career is based on this technology !!!! Sheesh!

Someone get me out of this industry!!!


All times are GMT +1. The time now is 00:11.

Powered by vBulletin 3.5.4 - Copyright © 2000 - 2025, Jelsoft Enterprises Ltd.
© Ducati Sporting Club UK