[Harry Putnam]

I'm having a problem posted in another thread:
Subject: Home Lan puzzler

About sharing and Network places. Its grown monstorously big and
still no resolution. chuck has been quite helpfull but still we
haven't solved the problem.

I'm wondering if I were to `reinstall' or `repair' that OS with a more
recent version of winxp pro. (the version installed was a pre sp/2
version).

I have a newer version with sp/2 included on disc.

I'm not that familiar with the possibilities from booting the install
disk. Is it possible to perform an update or repair that leave all
installed software in tact?



--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

[Malke]

Harry Putnam wrote:

> I'm having a problem posted in another thread:
> Subject: Home Lan puzzler
>
> About sharing and Network places. Its grown monstorously big and
> still no resolution. chuck has been quite helpfull but still we
> haven't solved the problem.
>
> I'm wondering if I were to `reinstall' or `repair' that OS with a more
> recent version of winxp pro. (the version installed was a pre sp/2
> version).
>
> I have a newer version with sp/2 included on disc.
>
> I'm not that familiar with the possibilities from booting the install
> disk. Is it possible to perform an update or repair that leave all
> installed software in tact?
>
>
>
Hi, Harry. The thread has grown huge and I've been following it. Did you
ever do what I suggested; i.e., unshare eveyrthing, reboot, and then
run the Network Wizard on all the XP boxen, reboot, reshare everything?

Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

[Harry Putnam]

Malke <notreally@invalid.com> writes:

> Hi, Harry. The thread has grown huge and I've been following it. Did you
> ever do what I suggested; i.e., unshare eveyrthing, reboot, and then
> run the Network Wizard on all the XP boxen, reboot, reshare everything?

Malke, I may need to do it over. I just unshared everthing rebooted,
then reshared it back or most of it. Does the wizard do something
special. I have all static ips in 192.168.0.0 network. All use the
same gateway and dns so I didn't redo all that. I usually just do it
by hand.

So I guess I did a half a__ed version of what you suggested. I saw
nothing change when finished.

I'm thinking its something we aren't even thinking of. But what I do
not know.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

[Malke]

Harry Putnam wrote:

> Malke <notreally@invalid.com> writes:
>
>> Hi, Harry. The thread has grown huge and I've been following it. Did
>> you ever do what I suggested; i.e., unshare eveyrthing, reboot, and
>> then run the Network Wizard on all the XP boxen, reboot, reshare
>> everything?
>
> Malke, I may need to do it over. I just unshared everthing rebooted,
> then reshared it back or most of it. Does the wizard do something
> special. I have all static ips in 192.168.0.0 network. All use the
> same gateway and dns so I didn't redo all that. I usually just do it
> by hand.
>
> So I guess I did a half a__ed version of what you suggested. I saw
> nothing change when finished.
>
> I'm thinking its something we aren't even thinking of. But what I do
> not know.

I'm going to suggest you do a "full-a_ed" version of what I suggested. I
don't know what the Wizard does that is different. All I can tell you
is that I, too, always set up my network by hand. After things working
fine for years, I was having trouble with one or more of the Windows
boxen being unseen on the network. I was having trouble with Samba
reporting that there was no Workgroup. Etc. For me, simply turning
every machine on, going through the Network Setup Wizard, then
rebooting amazingly made everything work again. Now the network behaves
itself and I can even use Network Places.

Your problem is slightly different in that you can't see some files on
shares (if I've got that right). So that's why I suggested you in
effect start over. Unshare everything. Reboot. Turn all machines on.
Run the Network Wizard. Fix the Workgroup name and set up the firewall
properly. Create shares. Reboot all Windows machines. Go have a drink.
Come back and see what has happened.

Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

[Harry Putnam]

Malke <notreally@invalid.com> writes:


[...]

>> So I guess I did a half a__ed version of what you suggested. I saw
>> nothing change when finished.

[...]

> I'm going to suggest you do a "full-a_ed" version of what I suggested. I
> don't know what the Wizard does that is different. All I can tell you
> is that I, too, always set up my network by hand. After things working
> fine for years, I was having trouble with one or more of the Windows
> boxen being unseen on the network. I was having trouble with Samba
> reporting that there was no Workgroup. Etc. For me, simply turning
> every machine on, going through the Network Setup Wizard, then
> rebooting amazingly made everything work again. Now the network behaves
> itself and I can even use Network Places.
Malke, in your scheme are you talking about unsharing everything all
around or just the problem machine?

I'm going to try it for good measure but would like to hear some idea
as to why that would have a positive outcome.

Also, I started this thread to try to learn what can be done from winxp
pro cd that may help. That is, can one repair an installation or
refresh or something without trashing installed programs?
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

[Harry Putnam]

Malke <notreally@invalid.com> writes:

[...]


> . . . . [...] . . . . . . . . . For me, simply turning
> every machine on, going through the Network Setup Wizard, then
> rebooting amazingly made everything work again. Now the network behaves
> itself and I can even use Network Places.

So you didn't unshare all machines then? Just wondering where that
comes in.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

[Harry Putnam]

Malke <notreally@invalid.com> writes:

[...]

> . . . [...] . . . . . Fix the Workgroup name and set up the firewall
> properly. Create shares. Reboot all Windows machines. Go have a drink.
> Come back and see what has happened.

Sorry if I seem rather dense but not sure what you mean by
`Fix the Workgroup name'. Can you spell it out a bit please?
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

[Malke]

Harry Putnam wrote:

> Malke <notreally@invalid.com> writes:
>
> [...]
>
>> . . . [...] . . . . . Fix the Workgroup name and set up the firewall
>> properly. Create shares. Reboot all Windows machines. Go have a
>> drink. Come back and see what has happened.
>
> Sorry if I seem rather dense but not sure what you mean by
> `Fix the Workgroup name'. Can you spell it out a bit please?

1. I didn't unshare things on my network because that wasn't my issue.
You are having share issues, so I suggested you basically "start over",
including unsharing all previously made shares on all computers, not
just the troubled one. After all, I can't see your computers from here.
Nothing you've done so far with me or Chuck has helped. There's no way
for me to untangle this long distance, sight unseen. So untangle things
by starting over.

2. As for a Repair Install, here is a link explaining the whole thing:

http://www.michaelstevenstech.com/XPrepairinstall.htm

3. When you run the Network Setup Wizard, it will rename your Workgroup
to the default MSHOME. If you have a differently named Workgroup,
change MSHOME to your preferred name at that stage in the Wizard.

Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

[Harry Putnam]

Here is what I did:
1) Turned Samba off for the duration.

2) Unshared all exported shares on all machines at My
computer/manage/shares
reboot

3) Removed all defined Network Places for remote disks/dir on each
machine

4) Removed network settings (static ip addresses)
reboot

5) Ran network wizard on all machines
reboot

6) defined network paramaters (IP Gateway DNS) on each machine
reboot

The result is that chub still doens't appear in `network places'.
After forcing it to appear by typing \\chub\ I see far less of the
invisible file problem. But it is still there. Still random seeming
except one directory G:\images. Stepping thru that Heirarchy always
stops at \\chub\chub-g\images\HERE.

Like before forcing it by typing in the exact address works

7) created Network places for all chub shares on the other two.
reboot

Result... no change from above.
Further notes.. I see nothing special about G:\images and when I
created the shares I choose to force the top level permissions all the
way down the hierarchy so there are no trick permission in the
heirarchy including at G:\images.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome