Home network not working

[mnovak5]

Hi!
We've connected our PC's with a friend of mine in order to make a small home peer-to-peer network. We've used the same network cards and a 17m long cable.
My friend (he is the "administrator in charge" - but I am the one who can ask more easily) set it all up (all the clients, protocols, dialogs, IP addresses, sharing, etc.). The problem is that the computers can't see each other (the see only themselves each). Ping doesn't work.
We use TCP/IP protocol (NETBeUI didn't solve the problem, but we've tried) and we have assigned IP addresses and unique names to the comuters. One uses Win 95, the other one Win98.
All the drivers have been installed correctly. Reinstallation of drivers or systems doesn't work. There are no conflicts or IRQ problems.
Where can the problem be? Sorry that the question is so general and that I am not very specific but we think that the problem must be that we missed a stupid little detail that is obvious. We just can't see it.
Thanks,
Michael

[POBrien]

Your detailed posting reads like you aren't using a hub, only a cable to connect directly to both nic cards. Is the cable a crossover cable? If it isn't, it needs to be.

Can you post the ip addresses and subnet masks from both PC? (These should be the only entries. there should be no gateway, DNS etc.. only the ip and mask on each pc). Also, make sure both machines have the "default protocol" checked in the network properties. It shoud match on both Pc's. Make either tcpip or netbeui the default.
Is the Workgroup name the same on both PC's?

[Basemodel]

POBrien is right, your problem is that you are using a straight-thru cable, when you should be using a crossover. You can identify a crossover cable easily by the wire schemes. Look at the cable you are using now. If you line up both RJ-45 connectors next to each other, flat side top, clip on bottom, you will see that the first wire on one side mathes the color of the first wire on the other end. So, wire 1-1, 2-2, 3-3, 4-4..etc..
Crossover cables will be represented by the following cable scheme: 1-3, 2-6, etc.. meaning the first wire on one side matches the color of the third wire on the other. You do *not* need to set default protocols or use Netbeui/IPX/spx. Tcp/ip is the only protocol you need (most likely, unless you play oldskool networking games, Doom2, wc2). Hope this isnt way too confusing.

[BertImmenschuh]

There is some very good stuff here:

http://www.linksys.com/faqs/default.asp?fqid=18

http://www.linksys.com/faqs/default.asp?fqid=20

[mnovak5]

The nice thing is that the cable IS a crossover one. As for the IP addresses - sorry, I don't have them with me but they are from the intervals reserved to home networks.
No gateway in use, nothing.
Still nothing helps.

At the moment we've decided to make sure the cable itself is OK and not e.g. broken. I'll let you know.

[Heathman]

Make sure the two following things. A. You're in the same workgroup (network identity) and B. You're actually logging in. If you don't get a logon menu when you start your computer, go to logoff, which will bring up a logon on box... After you've ensured both, next try to see if this is a connection error, or sharing error. Go to the "run" command under start, type "command" which will bring up a dos box. Type "Ping **.*.* whatever the other computers ip address is. Next, if that doesn't work, ping each computer individually (i.e. if you're 90.0.0.1, type ping 90.0.0.1 and then go to the other computer and type ping 90.0.0.2 ...whatever your ip address is. Please reply to this post for further questions or comments so I know you've responded to me directly. thanks

[Heathman]

no offense...but are you certain in "network" you've both loaded AND enabled file and print sharing, as well as your card drivers and tcp/ip follow up drivers? You will also need client for microsoft networks.

[giorgio]

File and printer sharing has nothing to do with this problem. :-)
1. You must be sure the hardware is working. If cable is crossover and ok, try to test your network cards. Installation usually includes testing program.
2. Both PCs have to use at least one common protocol. If it's TCP/IP the network mask must be the same (255.255.255.0 - example)
3. Then try ping localhost. If it's working on both PCs, you should be able to ping friends' PC too. If you couldn't ping localhost you have incorrectly configured your network card. Use configuring program (don't run it in Win - plug'n play could cause problems)
4. Doesn't matter if you can see other PC in your Network, you should be able to map networked PC by ip address. However, if you're using correct drivers and have configured cards correctly, it shouldn't happen.

[mnovak5]

When I ping the PC's they can see (ping) only themselves but not each other.

[mnovak5]

Finally!
We solved the problem yesterday!!! We tried anything from the most impossible to stupid but it was almost beyond our imagination. The cards used IRQ 9 which made problems at one of the computers. Naturally, no problem for Windows (it didn't show any conflicts or anything) but a great trouble for us.
So finally we could celebrate the transmission of the first byte!
Michael

[giorgio]

As I wrote - windows with plug'n play doesn't use hw as it needs to be used.
Congratulations!

[AndrewBlake]

Hello everyone!

I have been following this thread with particular interest as I have a very similar problem. The symptoms are intermittent inability of my two networked PCs (both running Windows ME) to see each other. Sometimes the system works, sometimes not! (Both access the net -via AOL- separately.)

Investigation shows the network card on one machine shares the same IRQ9 as another device. However when I try to change it to IRQ11 (which is apparently free) I get a message saying the value cannot be modified.

Any ideas on how to proceed? Does it mean having to switch card positions? I am relucatnt to do this as it seemed to make matters worse when I tried it before.

[giorgio]

IRQ sharing might not be a problem. It's wrong when you see "IRQ conflict".
If your network sometimes "goes" sometimes doesn't, as first try to upgrade your driver.
Another problem might be PCI (ISA?) bus. Try to upgrade drivers for your motherboard.
Next check your net protocols. Are they using the same protocol? Don't you use any "needless" protocol (ipx/xps in tcp/ip network...), dial-up adapter when you haven't got one, ...

[AndrewBlake]

Thanks for the advice re updating the motherboard drivers. Problem is that I don't know how to find out what make & model it is & I don't have any manual.

System information isn't very helpful!

Any ideas how to proceed?

[Smitty]

AndrewBlake

Try one of these files....
I use AIDA32...
<a target="_blank" href=http://www.voodoofiles.com/4997>Worldwide Sysinfo Tool</a>


<font color=red>Xmas</font color=red> <font color=green>Greetings</font color=green>

Smitty