Sharing oddity

  • Thread starter Thread starter Dr Bob in Dallas
  • Start date Start date
D

Dr Bob in Dallas

I know...not another question on sharing over a peer-to-peer LAN. But
this one stumps we.
But I have a win98SE system talking to a win2000 system over a local
LAN. Mostly it works fine. I can set up and share folders
(logical drives) on the win2000 system, except for one. Sharing of a
specific logical drive (G:) appears to be set up as it should be and as
are all the other logicals, but it won't show up on the LAN. The system
and the other loigcal show up but no that one drive. On the other hand
it does show up locally, when at the win2000 end but the other win98se
computer just cannot seem to see it.

The win98SE computer can talk to the other three drives that
are set up for sharing. But not to that one blasted logical.
I tried setting up sharing via Sharing under Properties, via Sharing
directly, and even via Administrator Tools. Tried removing sharing via
Administrator and then resharing. Rebooted time and time again. No luck.

Any suggestions on the way out of this puzzle?

Thanks.. Bob
 
Dr Bob in Dallas said:
I know...not another question on sharing over a peer-to-peer LAN. But
this one stumps we.
But I have a win98SE system talking to a win2000 system over a local
LAN. Mostly it works fine. I can set up and share folders
(logical drives) on the win2000 system, except for one. Sharing of a
specific logical drive (G:) appears to be set up as it should be and as
are all the other logicals, but it won't show up on the LAN. The system
and the other loigcal show up but no that one drive. On the other hand
it does show up locally, when at the win2000 end but the other win98se
computer just cannot seem to see it.

The win98SE computer can talk to the other three drives that
are set up for sharing. But not to that one blasted logical.
I tried setting up sharing via Sharing under Properties, via Sharing
directly, and even via Administrator Tools. Tried removing sharing via
Administrator and then resharing. Rebooted time and time again. No luck.

Any suggestions on the way out of this puzzle?

Thanks.. Bob

Time to get down to command line commands so that you
can see what's going on, and quote appropriate error messages.

From your description I assume that you have created a
share on your Win2000 PC, and that this share is invisible
to the Win98 PC. Please try this:

- On the Win2000 PC:
* Start a Command Prompt
* Type this: net share
Can you see the problem share?
* Type this: net share \\%ComputerName%\xxx
(where "xxx" is the name of the problem share).
Does the command work?

- On the Win98 PC:
* Start an MS DOS Prompt
* Type this: ping yyy
(where "yyy" is the NetBIOS name of the Win2000 PC)
Does the command work?
* Type this: net use z: \\yyy\xxx
What do you see?
 
hank you very much - here are the results
At the Win2000::
I can see the problem share
net share yields : share name p32G_GRAPHICS ,
path G:\, Remark (nil), Max Users 10, User (nil),
....all of which are correct

At the WIn98::
ping command works

net use z: \\p32sys\p32G_GRAPHICS responds "complete successfully"

net use responds: withe three lines

Z: \\p32sys\p32G_GRAPHICS
\\p32sys\IPC$
\\p32sys\p32G_GRAPHICS

So, it would seem that my win98 system is seeing the problem drive on
the peer win2000. G:\ is just not showing up when I look at Network
Neighborhood in the win98 explorer.

What do you think?
Thanks again........Bob L
 
Dr said:
hank you very much - here are the results
At the Win2000::
I can see the problem share
net share yields : share name p32G_GRAPHICS ,
path G:\, Remark (nil), Max Users 10, User (nil),
...all of which are correct

At the WIn98::
ping command works

net use z: \\p32sys\p32G_GRAPHICS responds "complete successfully"

net use responds: withe three lines

Z: \\p32sys\p32G_GRAPHICS
\\p32sys\IPC$
\\p32sys\p32G_GRAPHICS

So, it would seem that my win98 system is seeing the problem drive on
the peer win2000. G:\ is just not showing up when I look at Network
Neighborhood in the win98 explorer.

What do you think?
Thanks again........Bob L
 
When network resources are not displayed in "Explorer" then
this is usually caused by the machines having dissimilar
workgroup names. Make name all the same!
 
Yes, thank you. But of course both work groups have the same name. This
is required to get the two systems to link up at all.
Also, that both are in the same workgroup is verified by Win98 Explorer
being able to see 3 of the desired drives on the remote Win2000 site. It
just refuses to "see the" fourth drive, even though this troublesome
logical shows up under "Net Use" on the Win98.

I don't see that there is any way that one logical on a system could be
in a different workgroup than the others on that same system - only one
partition and one OS on each of the two systems. Or is there???

Anything else come to mind?

Thanks again.......Bob L
 
See below.

Dr Bob in Dallas said:
Yes, thank you. But of course both work groups have the same name. This
is required to get the two systems to link up at all.

This is not correct. Systems with different workgroup names can
easily be linked - it's just that they won't show up automatically
in places such as "Network Neighbourhood".
Also, that both are in the same workgroup is verified by Win98 Explorer
being able to see 3 of the desired drives on the remote Win2000 site. It
just refuses to "see the" fourth drive, even though this troublesome
logical shows up under "Net Use" on the Win98.

Perhaps something went wrong when creating the problem share.
I would now do this on the host for this share:
- Start a Command Prompt
- Type these commands:
net share ProblemShare /del
net share ProblemShare="d:\Some Folder"

I would furthmore use the same method to create other shares
to see if there is any rhyme or reason for the phenomenon you
observe.
 
Hi Pagasus -
Once again you have been most helpful. I will try what you suggest
on Monday. I do need to look into what you note in your first paragraph
of response. After having such a b.... of time getting the win98SE
system to link to ANYTHING on the win2000 (apparrntly this is a common
problem) I may have in the process created extraneous entities that are
fouling me up. From all I can see each drive on the problem end has the
"x$" and "share_name" shares presently designated and available as I
wish...... some just won't show up whereas others will and I cannot find
anything different among them that would account for the difference.

May I ask one more question: why would I get a net use response that
indicates a "\\p32sys\IPC$" path? I thought IPC$ was another name for
the "p32sys" itself?

Anyway, more to do tomorrow for sure.

Thanks Pegasus........... Bob L.
 
IPC stands for "Inter-Process Communication" and is, as you
suspect, another name for your PC. Windows uses it to set up
your credentials when accessing a shared resource on some
other machine. These links might clarify the issue somewhat:
http://www.techiwarehouse.com/cms/articles.php?cat=44
http://lists.sans.org/pipermail/list/2002-January/051428.html

Getting a Win98 PC to connect to a Win2000 would be child's
play if only people realised that Win2000 is a (reasonably)
secure operating system that requires proper authentication
before granting access to shared resources. You could compare
Win98 to a tent and Win2000 to a house with locks. Anyone
can walk into your tent but people won't get inside your house
unless they have the correct key. It's as simple as this.
 
Then that suggests that my problem maybe that there is something
incorrect, that I cannot easily see, in my "permissions" setting for the
drives that I am not able to share. Under "Permissions" the (in this
instance) G$ share properties are for "administrative use and cannot be
changed". But the share name "Graphics" for the same logical seems to be
set up for Everyone, as it should.

Is there a register key that could be overriding this latter setting?

Is there a register key where I can examine the permissions and such for
the problem (unshared) logical versus the other, available shares?

Thanks.......... Bob L
 
Back
Top