Shares with SP2

[Interrogative]

I had shares for certain parts of HDs on 2 different XPSP1 machines set so
that I could easily access the desktop of each from the other and other
progs as well. All went well in that regard when SP2 was installed on both,
too.

Then, I updated a prog to the latest version to find the brand new and
differently named exe didn't access the other machine at all. So, I decided
to go in and manually tell it where to look. It would look there but
wouldn't access the data. So, I went and checked the sharing of that folder
on the other machine and it was still in place. In any case, I decided to
remove a tick and immediately put it back and hit APPLY. Once I did that,
all the graphics that happen when you share a new folder to the network
happened. Immediately that it was finished, the prog on the other machine
started easily accessing the data from the original machine with nothing
else changed.

All this had lead me to believe that shares in place under SP1 and working
may be corrupted under SP2 and need to be redone even though they say they
are working *IF* you update progs etc.

Why the heck did this sort of thing happen?

[Ken Wickes [MSFT]]

My guess is that redoing the share caused the firewall to open the necessary
ports. You probably could have just gone to the firewall directly.

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


"Interrogative" > wrote in message
...
>I had shares for certain parts of HDs on 2 different XPSP1 machines set so
>that I could easily access the desktop of each from the other and other
>progs as well. All went well in that regard when SP2 was installed on both,
>too.
>
> Then, I updated a prog to the latest version to find the brand new and
> differently named exe didn't access the other machine at all. So, I
> decided to go in and manually tell it where to look. It would look there
> but wouldn't access the data. So, I went and checked the sharing of that
> folder on the other machine and it was still in place. In any case, I
> decided to remove a tick and immediately put it back and hit APPLY. Once I
> did that, all the graphics that happen when you share a new folder to the
> network happened. Immediately that it was finished, the prog on the other
> machine started easily accessing the data from the original machine with
> nothing else changed.
>
> All this had lead me to believe that shares in place under SP1 and working
> may be corrupted under SP2 and need to be redone even though they say they
> are working *IF* you update progs etc.
>
> Why the heck did this sort of thing happen?
>
>

[Paul]

I had a similar problem. I had one machine with XP on the LAN and several
shared folders. I had four Windows 2003 Servers backing up nightly to it
using Powerquest's V2i Protector. Each had their own username and their own
share. Everything was great until I upgraded the XP machine to SP2. All
sorts of weird problems -- one machine could still connect and was ok,
another I deleted the share it connected to and recreated, and it worked.
Another machine would *never* connect again to that machine no matter what I
did (deleted user, recreated user, removed share, moved share to different
drive, etc) When I pointed that machine to an XP SP1 machine with a share,
it was ok. Very strange.

I never used the SP2 firewall on this machine, it was definitely disabled.

Ultimately I just gave up on the XP SP2 machine and did a clean install of
Windows 2003 Server on that machine and all is well now.


-- Paul



"Interrogative" > wrote in message
...
>I had shares for certain parts of HDs on 2 different XPSP1 machines set so
>that I could easily access the desktop of each from the other and other
>progs as well. All went well in that regard when SP2 was installed on both,
>too.
>
> Then, I updated a prog to the latest version to find the brand new and
> differently named exe didn't access the other machine at all. So, I
> decided to go in and manually tell it where to look. It would look there
> but wouldn't access the data. So, I went and checked the sharing of that
> folder on the other machine and it was still in place. In any case, I
> decided to remove a tick and immediately put it back and hit APPLY. Once I
> did that, all the graphics that happen when you share a new folder to the
> network happened. Immediately that it was finished, the prog on the other
> machine started easily accessing the data from the original machine with
> nothing else changed.
>
> All this had lead me to believe that shares in place under SP1 and working
> may be corrupted under SP2 and need to be redone even though they say they
> are working *IF* you update progs etc.
>
> Why the heck did this sort of thing happen?
>
>

[Interrogative]

"Ken Wickes [MSFT]" > wrote in message
...
> My guess is that redoing the share caused the firewall to open the
> necessary ports. You probably could have just gone to the firewall
> directly.
>

If you are referring to Windows firewall, there was no popup to say a thing.
In any case, I thought the firewalls may have been interfering at first so
had them both off on both machines. Made no difference until I SHARED the
folder that was already marked as shared and had previously been OK. The
only difference I can think of is that the port number the old prog used was
different to the one the new prog used but that shouldn't have made a
difference in reality. It should just have worked even with the firewall on.
It didn't, on or off until that sharing was redone as I explained before.
Still got me bamboozled.