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

BITCH:lol::lol::lol:

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

network path not found:(
niether machine will ping

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?

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]

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.

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

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