Discussion Locked

P2P Network Partially Connects

0 helpful
56 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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.

56 replies

by bhunsinger

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

by casemaker

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.

by douglasb

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?

by casemaker

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.

by dmiles

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.

by casemaker

dmiles when you say "it will go far better if you know your network defaults and enter them what are you referring to?

by cp7212

Wow, this Q looks like a good candidate for a MCP cert. test. I only have a couple of recommendations and hopefully some of the others will comment on it.

I agree with one of the other posts, go with TCP/IP. It is the most common and probably easier protocol.

Even though 169.x.x.x is an internal address, it is still a Class B address and the subnet mask should be 255.255.0.0. This stands to what you have provided. You still may want to ipconfig /all your workstations to make sure of this. Check your default gateway and DHCP, also.

Even though the 169.254.x.x is relative, I would statically assign the IP addresses if you're only running three workstations on this node. You can always narrow it down to another octet, like 169.254.100.x, for ease of use.

Every time I worked on P2P, all of the O/S were the same, so I don't have a comment about that.

I was browsing through MS Technet's site and came across a transcript that may help you. The link is: http://www.microsoft.com/windowsxp/expertzone/chats/transcripts/03aug19.mspx

Good luck.

by curacao_dejavu

here's is a link with details instructions on how to set it up.
http://tinyurl.com/uh1j
http://tinyurl.com/5nnxa

further a couple of explinations.
pc 1 is xp home, there you can not run dhcp services on it , it simply does not have that built in. You need a server (w2k, w2k3) for that functionality.

also it's best to start with manual ip adressing instead of dhcp in order to be able to troubleshoot.
running the network wizard or ics wizard on pc 1 will provide automatically the adress of 192.168.0.1 255.255.255.0.
if it's not their yet enter this information.

all other pc's should be in the same range in order to access pc 1 and internet.
Hence:
ip 192.168.0.x
subnet 255.255.255.0
gateway 192.168.0.1
dns 1 192.168.0.1 dns 2 empty or your isp's dns.

with this configuration you can ping all pc's and vice versa too.

password issues.
since it is in a workgroup you need to create indentical accounts on all pc's.
on a win98, go to logoff and verify the username and password and make sure it's the same on the xp. if you want to delete the password in the win98 go to the dos prompt c:\windows and delete *.pwl (password files) and login again in the win98.

protocols
delete all protols that are not being used.
ipx/spx, netbeui, and the ms family logon network.

I think I have covered all.
Leopold

by hal 9000

OK I know this sounds stupid but have you unplugged the hub let the capacitors discharge and the re-powered it. Some times the hub gets a spirituous signal over the mains line and throws the whole thing out of whack.

It was a very common problem at one place where I used to do some work apparently they had some heavy industry up line on the mains and every time they switched on {It was a news paper so they drew a lot of current} it threw the hub for a loop. Of course it didn't help that this particular hub was nearly at the end of that mains line and every little bit of interference made it play up. Eventually I had to put it on a UPS to keep it running.

Col

by maniskid

Has any of these services failed or stopped.
Workstation
Server
Network Connections

Also, although you have installed the ipx/spx and netbeui protocols have you enabled the netbios over tcp setting in the advanced button in tcp properties.

by eddie.limoncelli

i have had the same trouble with w98/wxp p2p connections. in my experience it has been spyware on the xp machine preventing the w98 machine(s) from connecting. install Ad-aware SE and Spybot S&D (free downloads), update each program, then boot into safe mode to run eazch programs' scans. scanning in safe mode is the best way to remove spyware.
even better, download the WinXP SP2 exe file from microsoft, run the scans as above, then boot into normal windows and install SP2. i've had a lot of success keeping spyware out this way.

by willcomp

For an OS that supposedly makes it simple to set up a P2P network, XP certainly has its quirks. I've seen 2 small XP P2P networks that did exactly what you describe. Worked yesterday, but not today.

There is no need for ipx/spx, but shouldn't affect anything. I would remove it just to be safe.

For XP PCs, assume that NetBIOS over TCP/IP is enabled but NetBEUI is not installed. NetBIOS over TCP/IP is necessary.

See if any network connections are bridged. Have seen that cause problems.

Ensure that SP1 or SP2 (preferable) is installed on XP PCs.

If TCP/IP is not really required, you may want to use NetBEUI as protocol. See link below for info on how to install in XP.

http://support.microsoft.com/default.aspx?scid=kb;en-us;301041&sd=tech

Some more light reading that may help:

http://www.microsoft.com/downloads/details.aspx?FamilyId=E88CC382-8CE6-4739-97C0-1A52A6F005E4&displaylang=en

Oh, of the 2 I referred to earlier, got one to work by completely removing and resetting network settings manually. Other one had one rouge XP PC that just wouldn't see shared resources on other PCs. Reinstalled XP and cured problem. Still don't know what caused it.

Dalton

by darrynmarr1979

tricky this one, ive had some of the errors you've mentioned a few times, here's a few solutions if you havnt alread tried them

1st release and renew ip address for each machine, making sure that DHCP is NOT enabled on either xp machine

2nd check wins configuration in your tcp/ip seetings make sure nothings there

3rd in p2p passworded access to a shared file or folder across xp isnt needed, unless your connecting to a drive or folder with a $ at the end, so try mapping the drive or folder instead of going thru network neighbourhood

4th the network setup wizard assumes a lot of things, so i wouldnt use it myself but thats just me, instead configure your network manually, that way although it takes a bit of time

only advise i have, as ive said ive had the same error as you have"not accessible you might not have permission" and simply set up the network again on all the machines, worked after that,

by casemaker

THANK YOU to everyone participating with me on this.
I have been back on site and got further than I had previously. I manually set IP addresses to the range of 192.168.1.10 - 192.168.1.12 with Sub Net 255.255.255.0 . I deleted all protocols except TCP/IP. checked and added user names where appropriate. I changed the name of the troubled computer and changed the workgroup on all computers. The computer running XP home is the one I changed the name, it shows in N Neighborhood with new name. I went into safe mode and gave everyone full permissions.
After all this, all computers could communicate with each other except to the server/XP Home machine. TheXP Pro could see the 98 and vice versa, the XP Home could see the 98 and XP Pro. But neither the 98 or XP Pro could connect to the XP Home/Server. The error you dont have permission to view this resource shows from the XP pro and the 98 machine asks for password. The client said that they never had a password before.

by asokany

if you want to access from windows 98 to windows xp then do the following

when you boot the windows 98 system, it will ask for the password there you give that windows xp user id and password. now you can access the windows xp system resources.

is it clear or you can mail me asokany@yahoo.com

by m.bety

This is a simple issue
the hub does not have a DHCP server built in,
since you only have 3 pc's , you don't need to bouther about it.
Just set a different ip on all pc's (ex:192.168.1.10) and put 255.255.255.0 as you subnet mask.
now xp home is server of what ?
you might need to put the ip address of xp home as your gateway.
Now make sure, that <> is not activated.
Also make sure that in the properties of your NIC, file sharing and printer sharing is enabled.
also on the security of the folder you want to share, you hve everyone listed there, with the appropriate rights.

Now With all this done, you should not have any other issue.

just a sugestion, why are you using xp home as your server instead of xp pro, you would have more functionnality with xp pro

by compvar58

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 3 machines have to be on the same network in order to "talk" to each other. Use the rule of thumb for most personal networks of 192.168.1.1 to 192.168.1.254 and be sure all machines have the subnet at 255.255.255.0 The XP machines IP address should be used as the Gateway on the other to workstations. be sure to also set the machines to a common workgroup or Domain as this may affect the PC's being able to communicate. if you still have questions, reply back.

by zaferus

Hmmm, is it possible that a user account was created one the "server" to match the usernames/passwords on the other machines then the password was changed on one side or the other? This is common with this type of network setup for share "security".

Maybe modify the passwords on all systems to be the same for the same user accounts and give this a try?

LMK

Zaf

by izz

In windows XP there is a feature for NIC called (Authentication) there you have options like (Enable IEEE 802.1X) plus two more checkboxes...

Disabling them will help you communicates with other windows (98, 95)

Try it and tell me please

Hope this helps

by pulemet_maxim

Tell your client to spend 70-80 bucks on a router, something like Linksys or D-Link. That would make everyone's life easier.

This discussion is closed to new replies.