Home network

Mr_Frugal

davb wrote: »

I have seen this a number of times, and it is usually a fairly simple fix. The problem is with the PC you are trying to connect to (not from), so in this case, your XP pc. It needs a registry tweak, so be careful, back up, use at your own risk, etc, etc.
1. Start regedit.
2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters.
3. Double-click IRPStackSize (or if this registry setting doesn't exist, create it with type DWORD and ensure the case is CoRrEct).
4. Change the base to decimal, set the value to 15, and click OK.
5. Reboot the computer.

Thanks davb.
I did a backup of my registry then did as you describe above. I had to create IRPStackSize (being careful of my CaSe) as it didn't exist.
Having rebooted it still wont give me access.
I 100% agree with you that the problem is on my PC (ie XP version) as it is logical (ie network was working before, I format PC and reinstate and it doesn't work any more, yet made no other changes to laptops).

Should I leave this registry change in place or should I now reverse it ? (Don't know the first thing about registries so I usually leave well alone).

Thanks anyway.

Mr_F.

Mr_Frugal

Paul_R wrote: »

If you put SP3 on an XP pro computer you can't see the other PCs on the same wireless subnet.

The solution is to remove XP SP3 and install XP SP2 and - it works - you can see printers PCs etc. There are a few other things to try first though....

Make sure you have installed the Microsoft TCP/IP version 6 protocol in all computers by clicking install on your LAN properties dialogue window.

You might also need to get this MS program here for your XP machine.

Have fun. I would advise against wireless connections, you'd be better off with a router using wires. Besides, connecting with wires first would be best before going wireless.

If you use a network storage device you will need to manually configure your Vista home machine in the registry to see the device as the security policy does not allow connections as standard to these legacy devices.

When you finally get it all running, go out and buy a USB hard drive and make a backup of your systems, it will make it a lot easier in the long run.

Paul, firstly I would like to install the TCP/IP version 6 on my XP PC (as my laptops have it). When I have tried to install this I get the following error message "Could not add the requested component. The error is: An extended error has occurred."

With regards removing SP3, is there a quick way to roll back to SP2 (ie can I go in to Control Panel and add/remove SP3 ?)
Will this definetly sort out the problem, as the network used to work previously when I had SP3. I think that I probably initially set up the previous network when I was under SP2 and then later upgraded to SP3 (with no detriment to the network).
However in "rebuilding" my PC I ghosted an old image that I had backup up a couple of years ago (with SP2 on it) and started building up from that point. In doing so one of the first jobs I did was to update my Windows (including SP3). I have done all updates that are critical.

Quite prepared to 'roll back' to SP2 if it gets the darn thing working but would I then be able to upgrade back to SP3 again ?

Cheers,

Mr_F.

enigma52

if you refer back to post no. 11 by Davb, if you change the setting from 15 to 24 then do this for each pc on your network, then reboot everything and if the network is up and running you then need to go back into the registry and now change the setting from 24 to 21 again on each machine then reboot again and if everything is still ok then lower once again this time to 18, then reboot etc. If at anytime the network stops working go back to the last setting it worked at, but never lower than 15

davb

Mr_Frugal wrote: »

Thanks davb.
I did a backup of my registry then did as you describe above. I had to create IRPStackSize (being careful of my CaSe) as it didn't exist.
Having rebooted it still wont give me access.
I 100% agree with you that the problem is on my PC (ie XP version) as it is logical (ie network was working before, I format PC and reinstate and it doesn't work any more, yet made no other changes to laptops).

Should I leave this registry change in place or should I now reverse it ? (Don't know the first thing about registries so I usually leave well alone).

Thanks anyway.

Mr_F.

As enigma52 has suggested it is worth trying a few settings of IRPStackSize, as 15 is a good starting point - I have found 20 works ok on systems I have had trouble with - the problem usually stems from Antivirus programs taking resources. If it doesn't clear the problem, then you can either leave the key or delete it, just don't leave it set too high.

I really don't think rolling back to SP2 is going to make a difference, I am sure it can work with SP3.

Mr_Frugal

davb wrote: »

As enigma52 has suggested it is worth trying a few settings of IRPStackSize, as 15 is a good starting point - I have found 20 works ok on systems I have had trouble with - the problem usually stems from Antivirus programs taking resources. If it doesn't clear the problem, then you can either leave the key or delete it, just don't leave it set too high.

I really don't think rolling back to SP2 is going to make a difference, I am sure it can work with SP3.

Great big THANKS to everyone who has helped me with this, especially davb and enigma52 as by following your advice I have now got this working again !!!!
After reading your first post davb I dug around on the subject in Google and had started to gradually up the number by 1 and then reboot and retry. I had got to 20 and noticed that some of my really small folders were now opening remotely but my bigger drives (ie root drives) were not.
Went out to the neighbours for a drink, got back with hope in my heart, got up to 22 but still no joy with the bigger drives.
Checked back here and saw enigma52's post about applying to all PC's on the network.
Did so and hey presto !!!!
Tried reducing from 22 but couldn't get it any lower - still I am WELL happy so thanks again !!!!

Mr_F.