General discussion

Locked

P2P Network Partially Connects

By Casemaker ·
Hi,
Difficult to keep simple. I was onsite networking. The client said that the network was able to communicate with each other and then all of a sudden it stopped. There are 3 pc?s on P2P through Linksys hub model EFAH08W, PC1 acts as Server has WXP home ip address of 169.254.18.110 HDD is shared. PC 2 is W98SE ip address of 169.254.113.220 HDD is shared. PC3 is WXP Pro, ip address is 169.254.225.164 HDD is shared. All three pc have Client for MS Networks, File and print share enabled, ipx/spx, netbeui, TCP/IP. There are no firewalls activated or any other software that would lock out other pc?s. I can ping from all pc to the other pc?s. The client said that he never needed a password to access any of the other computers. The computer names do not conflict and the workgroup names are all the same. All computers can see the others through network neighborhoods and places. Customer said that after the network stopped working he tried to run the network wizard and he ended up with even less connectivity. I have shut down all pc?s and hub and reset, still not working. This is what happens when I try to connect. PC1 to PC3 connects, PC3 to PC1 not accessible you might not have permission. PC1 to PC2 connects, PC2 to PC1 not accessible you might not have permission. PC3 to PC2 connects, PC2 to PC3 device does not exist. It also asks for a password to access. I created accounts on the xp home machine and that did not work.
thank You for taking the time to review my problem.

This conversation is currently closed to new comments.

56 total posts (Page 1 of 6)   01 | 02 | 03 | 04 | 05   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by BHunsinger In reply to P2P Network Partially Con ...

check teh admin on the linksys to see if settings have been corrupted or if DHCP is messed up. Alos, did they machines just have SP2 installed, check and see if the Microsoft firewall is activated

Collapse -

by Casemaker In reply to

Poster rated this answer.

Collapse -

by Casemaker In reply to

Poster rated this answer.

Collapse -

by Casemaker In reply to P2P Network Partially Con ...

The hub is a Linksys EFAH08W and to my knowledge there is no admin or setup page to access and verify DHCP. There are no firewall activated to cause any problems and to my knowledge SP2 is not installed.

Collapse -

by DouglasB In reply to P2P Network Partially Con ...

Since PC1 is acting as your server, are you having it use DHCP to assign IP addresses to the other two computers? I might be wrong, but from the IP addresses you supplied above it does not look like all three computers are "on the same page." Are you assigning the IP address for each computer?

Collapse -

by Casemaker In reply to

Poster rated this answer.

Collapse -

by Casemaker In reply to

Poster rated this answer.

Collapse -

by Casemaker In reply to P2P Network Partially Con ...

I assumed the Linksys hub would be assigning the ip. I have mostly worked with Linksys router that had built in DHCP and thought that the Linksys EFAH08W would do the dhcp also. I was not sure if the ip numbering scheme needed to be the same range for the first three parts and then another to id the node on the network.

Collapse -

by dmiles In reply to P2P Network Partially Con ...

XP's peer-to-peer problems
XP Home will work in P2P networking with older versions of Windows, but it has significant problems even there. For starters, XP Home will work only with a maximum of five P2P servers; it simply won't work with more than that. XP Professional, on the other hand, will work with up to 10 P2P servers. If you have more than that, you need to rethink your network design.

Another problem with Home on an existing P2P network is that if you run the Network Setup Wizard (NSW) on other machines?which the program will probably ask you to do?it will attempt to make the network confirm to XP's defaults, such as the workgroup name MSHOME, rather than use the existing network defaults. You should also forget about using NetBEUI. Though that protocol is in Home, Microsoft won't support it. TCP/IP is the only real way to go.

As for the rest of the setup, it will go far better if you know your network defaults and enter them into XP's Network Setup rather than let the wizard attempt to smooth your path for you. Of course, if you're starting a small P2P network from scratch, NSW will actually make the setup run much more smoothly.

Collapse -

by Casemaker In reply to

Poster rated this answer.

Back to Desktop Forum
56 total posts (Page 1 of 6)   01 | 02 | 03 | 04 | 05   Next

Related Discussions

Related Forums