can't access new install xp pro sp2

[jan tanjo]

Hi guys.

Thought it was safe to upgrade to SP2 and everything does work nice.... except accessing from other machines on the network. Everyone can see the new xp box but no one can access anything.

"Might not have permission" and "Network path not found" are the 2 main messages I get. Very, VERY fustrating 2 weeks trying to figure this out.

[FastLearner]

Please let us know your hardware and Operating System setup. Is this a domain or a workgroup we are talking about here? If a workgroup, are the workgroup names spelled exactly the same? Have you shared the drive(s) in question from its properties menu? Have you rebooted since the new install? Are all computers in the same subnet? If not, how is your router/switch set up?

You can Ping the new machine from all others? Can you ping all the others from the new XP machine?

Also, do you have the Windows firewall on the new XP install turned on?

Two weeks is way too long. Let's get you up and running...:)

[Erik]

My bet would be that the new SP2 Windows firewall is blocking everything. I think it is pretty worthless so I disable the service and install a proper software firewall. I have had it just stratup on its own, and forget the settings allowing my network PCs to communicate. Very irritating when it happens, especially on a server that is being used. Thus I now disable it on all PCs I keep in my network, and use a firewall that won't spontaneously change settings on me.

[jan tanjo]

Hi FastLearner

It's happening on 3 machine and the only thing that's common is that it is XP Pro on a P3 Dell, P3 IBM, P4 Advantech. I'm hubbing through a 16 port netgear 10/100.

Can't ping any of them, it's like they are "Blocked", so I think Erik is right that it is Windows firewall not playing nice.

I think what I really need is the registry location for firewall so I can just delete that branch, seems extreme but hitting that delete button would feel great.

But before I do that I'm going to try reinstalling using Netfw.inf method.

[FastLearner]

I had also mentioned firewall as a possible culprit in my first post, since all the symptoms are there. Now with the info you just gave, it is almost certainly a firewall blockage of some sort. Why are you wanting to change your registry to stop the firewall? Is there any reason you can't just use Start -> Control Panel -> Windows Security Center and deactivate the firewall this way?

[Erik]

You can also disable the firewall by just going into Start...Run... type services.msc and hit enter. Scroll down to Windows firewall, and hit disable. Hacking the registry seems a bit extreme for something that is so easy to do right through built in utilies.

[jan tanjo]

Hi FastLearner

As much as I like Windows and I understand what Gates is trying to do for the average computer user, but for crying out loud, don't cram it down my Harddrive, I realise that there are built in utilies, but for some reason they're not working properly, I've started looking at my bios setting and hardware :confused: so, like I said, It would feel great to just delete the whole thing.

[FastLearner]

Hi Jan,

please let us know what we can do to help you. Have you tried to turn off the firewall by using the built-in utilities? What happened? What do you mean by this statement:

I realise that there are built in utilies, but for some reason they're not working properly

Your answer to this question may help us find the source of your problems.

Truthfully, I am a little confused at the motives of your last post...

I would like to clarify that I and everyone else here are willing to help out where we can...

[Paul Komski]

If its only WinXP Pro boxes then I bet its to do with simple file sharing. My suggestion is to first unshare any shared folders. Then go to Folder Options and change whatever setting is there for Simple File Sharing. Enable it if disabled and disable it of enabled. Go back and setup you shared folders from scratch.

If still not accessed on the network then repeat the above procedure but so that the Simple File sharing setting is reversed.

I know this has usually sorted out WinXP Pro for me a few times in the past and when many networking gurus (which I am not) were poo poohing it or coming up with many other complicated fixes. The inability to ping the box from the network is my only worry that it could be something different.

[Erik]

Simple File Sharing miht have something to do with it, but that would be down the line if ping isn't even working. You need to be able to ping the PC before you can access any files on it, regardless of what permissions you have.

As for the firewall issue, just do what I said and disable it in services.msc. This has always worked just fine for me, and I have never had it pop back on after that. Alternatively you could also just configure it properly to allow file and printer sharing on the local network. The Windows Firewall isn't actually that bad, if you configure it for use on your network how you want it. If you don't want to use it, there are much better alternatives available which is why I don't use it, then the best bet is to disable it. Windows likes to turn the firewall back on automatically, even if you opt to just turn it off, to help protect your computer.

If you have already disbaled all of the Windows Firewalls and are still having problems then post back with the new issues and we can try and help you get up and running. Hacking the registry won't do anything more helpful than just disabling the firewall in services.

[Paul Komski]

Everyone can see the new xp box but no one can access anything.
I would just add that "seeing" the box from pcs on the network is one thing and this is just the problem I had last week, when I'm pretty sure that the other PCs on the LAN (WinXP Home and Win98se) knew the WinXP Pro box was there but couldn't access it. I think that they were also unable to ping it (with no firewalls running at the time) - presumably because the ping must get through before it can be "echoed". I repeat that I am not an expert in this area.

[jan tanjo]

Wow guys, thanks for all the support.

All right, Here is a summary of all the things I've done:

I slipstreamed SP2 to XP Pro SP1 and installed with everything default. and once eveything had settled down network abilities are no where to be seen. No biggie, used the wizards and blah blah blah got it going.

Used the windows provided drivers and installed and worked like a charm . . . except the traffic was only one way, (out) I used the firmware info and downloaded drivers from intel instead of getting them from IBM (which is this particular machine), still the same problem.

Allowed file and printer sharing,
Gave full control to the shared folder in Permissions,
Disabled simple file sharing,
Disable power management,
Tried Winsock repair,
Deleted the registry entries for Firewall,
Delete Firewall as a service from the registry,
Deleted all files for Firewall and Security Centre,
Used netfw.inf to disable Firewall during the install process, (a reinstall) and I still had the same problem.

So based on this experince I felt that Firewall had nothing to do with what was happening.

I made a custom install disc that did not have Firewall, Security Centre, ICS, and for good measure used netfw.inf.

Then did another install (Networking installed perfect and ready to use, except it's oneway,) Installed Intels NIC drivers. deleted Firewall entries from the Registry and still have the same problem.

If you Google "Network path not found" and "You might not have permission." there are about 8 remedies and fixes for this problem but none have worked for me.

As I said before, this is happening on 3 machines but everything you have just read I did to only one. If it doesn't work on one it probably won't work on the other 2.

SP1 worked fine, even with using all the drivers that came with it. I am really at my wits end here, I don't know networking very well and I'm ready to start doing the absurd to fix this. :eek:

Somewhere in the bowels of Windows there is a tiny setting that I have not yet tried, now how do I find it?

What things can affect network traffic flow?

[Paul Komski]

I have always found the following site good for setting up a LAN and Network shares:
http://www.performit.co.uk/network/software_setup.htm

I note the following which hasnt been mentioned to date.

In order for people on the other operating systems to view files on your computer you will need to enable the 'guest' account on your computer. This is disabled by default for security reasons. To enable it go to:

Start | Settings | Control Panel | Administrative Tools | Computer Management | Local Users and Groups | Users

Double click on Guest and then un-tick the 'Account is Disabled' checkbox.

[FastLearner]

Hi Paul,

I am curious about your post there, since at work we ALWAYS disable the Guest account and file sharing is enabled. Perhaps this is only in a Workgroup setting vs. domain (just guessing here).

Jan, have you tried looking in the Windows Components area to make sure Simple TCP/IP is activated? Normally it should be, but it's worth a check.

Go into Start | Control Panel | Add/Remove Programs. On the left side of the screen there will be a button called Add/Remove Windows Components. Click on this box. A window will come up, from which you will highlight Network Services and click on Details. Check and see that Simple TCP/IP is checked. If not, check it and Click OK and restart. You may be prompted to insert your Windows CD briefly at this point.

[Erik]

Hi Paul,

I am curious about your post there, since at work we ALWAYS disable the Guest account and file sharing is enabled. Perhaps this is only in a Workgroup setting vs. domain (just guessing here).


The Guest account is needed for simple file sharing. This is how it gets around the need for specific permissions on each file and folder. Also in a domain simple file sharing is impossible due to the way a domain operates, and in my opinion the Guest account should be disabled for security. It just makes it too easy for someone to gain access to your systems.

It is worth checking into I suppose, but if you are still not able to ping a PC then it probably has nothing to do with permissions but is some network level problem.

[jan tanjo]

No to guest account
No to Simple TCP/IP (none of my other machine have this enabld/installed (SP1)

Going to have a look at Paul Komski suggested site

Please kind in mine that the only thing that has changed is the addition of SP2 and as easy as it would be just to go back to SP1, I have software that needs SP2 on 3 other machines, (6 in total).

There are a lot of terms in the advanced tab of NIC properties that I don't know, but I think that might be where my problem is. But it would have to be something that is the same between 3 completely different machine, firmware wise???? I don't know.

[Erik]

Are you able to ping the machines by using machine names or IP address? If yes then it is a problem with file permissions. If no then it is something at a lower level causing you an issue. So which is it?

[jan tanjo]

Hi Erik

Ping times out using IP address, Folder permission is set to full control for Everyone. I've given static IP address, disabled LM look up and changed the netBIOS setting to "Enable netBIOS over TCP/IP", from the default setting (which to me seems to be the same thing.) Disabled TCP/IP filtering on TCP ports, UDPports, IP protocol and set them to "Permit all"

hmmm, anything else? Oh yeah, pulled the rest of my hair out

[FastLearner]

The Guest account is needed for simple file sharing.

Wow, I stand corrected. Paul was right on the money (as usual). The Guest account is necessary for file sharing, even though you may be logged in as another user. That's what I get for getting spoiled in my 'NT Domain'at work :)

http://support.microsoft.com/?kbid=300489

Jan, you said "No to guest account". Does this mean that you do not have the guest account enabled?

Also, we have not seen any IP addressing information. Perhaps you might want to let us know your IP addressing scheme of all computers, to include IP address, gateway address and subnet mask?

Please correct me if I am wrong:

-You have disabled the Windows firewall.

-You have enabled Simple File Sharing (in which case your Guest account needs to be active).

- Device Manager shows no problems with the NIC

Is all of this correct?

If so, then I can certainly understand your frustration... :confused:

[jan tanjo]

Hi FastLearner

I'm going to need a little bit of time the follow through on your MS kb link, the little that I did read it seems that there has been a change in the function of the guest account, I don't have it enabled on any of the other machines with SP1.

If after giving it a good try and it still doesn't work, I'll see if I can post some screen shots of my network setup.

I had network problems a while ago with one of my other machines and found that if I assigned an IP address (Static IP Address) it fixed my problem. So I just assigned an address all the machines.

IP address are 169.254.xxx.xxx
submask is 255.255.0.0
No highspeed yet so, no gateway address. (Gateway will be on a linux machine)

[Paul Komski]

I assigned an IP address (Static IP Address) it fixed my problem. I think I found this helpful as well until I realised that I couldnt then share my internet (dialup) connection.

[FastLearner]

Yes, absolutely. The 169.254.x.x/16 address range indicates that no DHCP server is being found. Try assigning all addresses statically and your problem should (hopefully) be fixed.

Try something like 192.168.2.(2-254) with a subnet mask of 255.255.255.0 for each node. Remember to restart your computer after changing the TCP/IP settings, as sometimes they don't seem to take effect until you do. Not totally necessary, but a good practice nonetheless.

[Erik]

Also I had been under the impression you were using a router or some other device here. What is your exact network configuration? A switch connecting all PCs? A Hub? No DHCP server available?

Also it would be helpful if you could post with the output from an ipconfig on all machine here. This way we can tell if all of the machines are in the same subnet.

[jan tanjo]

Hi FastLearner

I read your MS kb link, I had some success (was able to get rid of the limited connectivety) but I don't know if it was the SNMP or the Guest account. So I am doing a fresh install to try each to see which.

I read another MS kb that said the SNMP had added function in SP2, one stupid dll file to cause this much headache.

How do you activate the guest account without it showing on the welcome screen, the kb seemed a little vague to me

I'll change the IP address on all my machines if you think it's better, is there a reason you suggested 192.168.2.xxx

Erik, I apologize for any misunderstanding or confusion, I did mention, though probably not clearly, that I was hubbing through a 16 port netgear, I hadn't bothered putting anything else into the mix, my plan was to use a linux box as a router/switcher/firewall/antivirus/gateway.

It's just peer-to-peer network through a hub with a linux box as a file server/backup/app distributor

[Erik]

If you are/were getting limitied or no connectivity that is an indication of a problem at a very fundamental level on the network. Put everything to use an address in 192.168.1.x with a subnet mask of 255.255.255.0. You might want to use a switch in place of that hub, it just makes for a better network in general.

Before worrying about be able to share any files you need to make sure that each PC is able to ping every other PC by IP address, and by hostname. Without that ability you will never be able to share files anyway, so it is a waste of time trying to set permissions and guest accounts, etc.

[Paul Komski]

A long-shot seeing it unlikely there was a name change during the migration to SP2 but for completEness let it be said that:

"Computer Name—Identifies the PC on the network for other users. This entry must be a unique name of 15 characters or fewer, containing no spaces".

[FastLearner]

I'll change the IP address on all my machines if you think it's better, is there a reason you suggested 192.168.2.xxx

The 2 was just a number off the top of my head. If you have a 192.168.yyy.xxx/24 network, the 24 means that you are using exatly 24 bits of the 32-bit address for the network ID, and the remaining 8 bits for the node ID. A more common way of seeing this is that the subnet mask is 255.255.255.0 .This means that you will be able to add up to 256 nodes (-2) to your network, which allows for more than enough growth potential.

Using an address in private network space (192.168.x.x or 10.10.x.x) is only a good idea because you may plan on one day attaching your network to the outside (Internet). Otherwise, you could theoretically use any legal IP address you wanted.

So as long as you are using that subnet mask (255.255.255.0), you can use whatever you want for the last octet (between 1 and 254), but the 1st, second, and third octet have to match on all the nodes in the network or they will not be able to "see" or communicate with each other.

Just as an example, a home could have the following typical setup:

1) 1 Home Router w/NAT capability to connect the network to the Internet with only one external IP address. Most home routers also have a built-in switch, which means they can help you set up your LAN, too - all with only one device. When you have a router (which should be set up to be your Standard Gateway on all PCs in your network), it will have an internal LAN address, such as 192.168.1.1.

2) PC1: IP Address 192.168.1.2, connected directly to the switch (router in this case). Subnet Mask 255.255.255.0 . Standard Gateway address: 192.168.1.1

3) PC2: IP Address 192.168.1.3, connected directly to the switch (router in this case). Subnet Mask 255.255.255.0 . Standard Gateway address: 192.168.1.1

4) Laptop1: IP Address 192.168.1.4, connected directly to the switch (router in this case). Subnet Mask 255.255.255.0 . Standard Gateway address: 192.168.1.1

5) Laptop2 w/wireless adapter: IP Address 192.168.1.5, connected via its wireless adapter to the switch (router in this case) - this only works if your router has a built in wireless access point, which again most home routers do. Subnet Mask 255.255.255.0 . Standard Gateway address: 192.168.1.1

Most routers also have a setting where you can enable DHCP. This just means that all of your PCs and laptops will get a different address each time they connect to the network, but the 192.168.1 part will stay the same - always. And the router address will never change either.

Your 169 range address is an automatic address programmed by Microsoft that your computer receives if it attemts to get an address via DHCP but there is no DHCP server available (or DHCP is in the router disabled). If you are not using a DHCP server of some sort, then you will need to assign the addresses all manually.

To do this, go into Start | Control Panel | Network Settings, then highlight your LAN connection, right click and choose Properties. In the dialog box that opens, first highlight TCP/IP and then click on Properties (in that order). Now you can uncheck the two boxes that say "obtain address automatically" and enter your static IP addresses, subnet masks, and standard gateway. Click OK and restart your computer. Do this process on all computers in your home network. Then once all the machines have restarted, connect them to the LAN and try to ping every other machine by their address in this fashion:

ping 192.168.1.2 <enter>

Report the results. Either the process wil time out (not good) or your packets will be received.

Also I know Jan that most of this was probably a repeat, but I tried to keep it as simple as possible in case someone else comes to this thread with the same type of problem.

[jan tanjo]

Hi FastLearner,

With the amount of information on the internet, and my limited grey matter, it's so hard to know what is relevent to any given situation and it can sometimes be nuts-in-the-stomach scary to try things, especially on a work machine. Your explaination has given me a starting point at which I can start understanding this netwroking behemoth.

I changed the IP address like you suggested and lost the limited connectivity.

Now it's a long weekend with my beloved family.

[Paul Komski]

FWIW - I came across the following in my travels. Just an example of network access that looked like it was caused by SP2 not being due to SP2. ;)
It wasn't the upgrade to SP2 afterall, it was the immediate installation of
Sunbelt's CounterSpy right after the SP2 install.

There are security optimizations which the anti-spyware program performs -
one of which closes a potential hole of "Restrict Anonymous Access". That
registry entry has been subsequently restored - and now I have access to my
other computers.

from http://www.mcse.ms/archive70-2005-7-1741668.html

[FastLearner]

I changed the IP address like you suggested and lost the limited connectivity.

Hi Jan, does this mean you lost all connectivity, or are you saying that you now have improved the situation by changing the IP addresses?

Sorry, I haven't had my coffee yet today so please forgive me for my inability to understand your post... ;)

[jan tanjo]

OK, Update. (beloved family understands)

I found the problem, Microsoft Data Access Components (MDAC) was disabled/not installed, which Active Directory service is dependant on, which enables Local user and Groups, which is the ONLY!!!! way to enable Guest account. (Believe me, I looked).

So, in order to share a folder you need MDAC installed/enabled > Active Directory Service > Local User and Groups > Activate Guest account > back to Windows Explorer > share the folder (right click, sharing and security) > Share the folder > permission > Everyone full control > Ok > Security tab > add "Everyone" > give full control > Restart.

This needs to be done on all the machines that you what access to. Kinda incompatible with SP1 but I'm sure there are work arounds which I'm not going to bother with.

This is my setup to do what I need, there are variation to the process that are quite easy to see along the way.

Also changing IP address to 192.168.xxx.xxx, sub mask 255.255.255.0 I was able to get FULL connectivity, (sorry FastLearner for my double negative.) I didn't install/enable SNMP, from what I understand it's to get control on the remote resource. Am I wrong??

Damn, I feel smart now. . . aaw crap, is that toilet paper stuck to my shoe?

[Erik]

Wait, Active Directory? You are running a domain? That was never mentioned before, and makes file sharing very different, as does the troubleshooting process. Your DNS server should be the IP of the PC performing AD and acting as a PDC. Also simple file sharing won't work on a domain.

As far as I know AD shouldn't even be an option without a domain controller.

[jan tanjo]

No, I'm setting up a workgroup, I'm not even going to venture into Domaindom.

Active directory, for me, was needed just to activate Guest account, nothing else. I'm going to test to see if you can delete Active directory (MDAC) after activating Guest account.

My understanding of active directory is where the domain has one virual place for everyone to share their files spread over many physical places. So you have local shared folder, where you invite poeple in, and a global shared folder where everyone can share files.

Would be a little over kill on a domain with less then 20 members, but highly efficent if you have thousands of members on a national domain.

Anyway, I degress.