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 |
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