General discussion

Locked

Simple peer-to-peer not working

By gmichaels ·
I have a situation with 2 win95 PCs in a basic peer-to-peer network with hub where both PCs seem to be working on the network but one PC cannot see the other PC. I installed 2 new NIC cards, configured tcp/ip, client for ms networks, file and print sharing. Gave 1 PC an ip 192.100.100.1 subnet mask 255.255.255.0. The other PC ip 192.100.100.2 subnet the same. Both are in the same workgroup with unique PC names. Each PC can ping itself but not the other (time out). Both PCs can bring up network neighborhood and can see themselves in the workgroup. It does appear to search the network (the flashlight icon). But neither can see on another. All luights on the NIC and hub are green. First thought is cables to/from the hub or the hub itself. So,I tested all the cables with a cable tester. All OK. Tried a new hub out of the box. Same results. What is going on here? The old existing hub has a hub/dte switch on the front with 1/6 rje45 on back and 7/8 rje45 on front. Also has 1 bnc connector on back. Not familiar with this type of hub. Can someone explain the hub/dte switch and 7/8 rje45 on the front? The PCs were upgrades to win95 from win3.11. So, there was a bunch of DOS network stuff left in config.sys. But seemd to be all commented out. I suspect a software problem.

This conversation is currently closed to new comments.

17 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Simple peer-to-peer not working

by gmichaels In reply to Simple peer-to-peer not w ...

Must add that file and print sharing is loaded and enabled on bioht PCS. Client for ms networks id primary login and TCP/IP set as default protocol. I think I covered all the bases.

Collapse -

Simple peer-to-peer not working

by Alpha-Male In reply to Simple peer-to-peer not w ...

This may be an extremely simplistic answer and you may have already done this...but have you actually "shared" folders or drives on each machine? I saw you set up file sharing, but you need to actually share something for them to connect in a peer to peer network...

Let me know. If this doesn't help, I'll be glad to try to help further. Good luck!

Collapse -

Simple peer-to-peer not working

by gmichaels In reply to Simple peer-to-peer not w ...

Tried setting up the shares. Same bad results.

Collapse -

Simple peer-to-peer not working

by Walter_Loh In reply to Simple peer-to-peer not w ...

what alpha mention is true and try to re log in after windows start up , i have see this problem too , both pc have to actually share something in order for them to see each other , else get a cross cable and plug in directly nic to nic without going through the hub .

Collapse -

Simple peer-to-peer not working

by gmichaels In reply to Simple peer-to-peer not w ...

Tried setting up the shares. Same bad results.

Collapse -

Simple peer-to-peer not working

by gperrie In reply to Simple peer-to-peer not w ...

When you ping the other PC are you using the IP address or the hostname? If the hostname, remember you need to have the name resolved somewhere, probably a hostfile in this case.

You could also try using another network protocol. NetBEUI shouldbe OK in this situation and its even easier than IP to configure. I've had problems on 95 machines with the IP stack becoming corrupt but no problems with NetBEUI.

Gavin

Collapse -

Simple peer-to-peer not working

by gmichaels In reply to Simple peer-to-peer not w ...

I was pnging IPs. Tried Netbeui and tcp/ip. Same bad results.

Collapse -

Simple peer-to-peer not working

by 7nt In reply to Simple peer-to-peer not w ...

Try using IP 192.168.0.1 on the first machine and 192.168.0.2 on the other. Leave the subnet masks at 255.255.255.0

clover9

Collapse -

Simple peer-to-peer not working

by gmichaels In reply to Simple peer-to-peer not w ...

Treid the IPs. Same bas reslults.

Collapse -

Simple peer-to-peer not working

by Blackcurrant In reply to Simple peer-to-peer not w ...

When you boot the PC, do you see the Microsoft network logon box? If you do then your network should be functioning, if you do not, then you need to completely remove the networking components (TCP/IP etc), but before rebooting, remove the NIC. Reboot, then reboot again, shutdown, reinsert the NIC, reboot, then install the drivers for the NIC. After this has been done, set up the TCP/IP etc again.

I have to do this quite frequently at work, and often find that the first attempt at setting upnetwork connectivity fails. I know the failure has occurred when the network logon box fails to appear. I just sigh dramatically and start again! I often find that removing/uninstalling everything then restarting clears the problem, and I rarely have to reinstall more than once.

Also, you might want to consider doing a clean upgrade from 3.11 to 95, just in case any obsolete protocols, system settings have been retained that are preventing you from connecting.

Other than this, you shouldcheck that the cables and associated hardware are functional.

Hope this helps

Back to Windows Forum
17 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums