microsoft.public.windowsxp.general,

[harryguy082589]

Hi,

I have a network containing my desktop and laptop- both of which are
running XP pro and a SAMBA based server (I'm 15, and just hosting a
blog- cant afford windows at the moment).

I have my laptop and desktop configured with simple file sharing
disabled. Each computer has a account named "remote" which is given
permission to access the computer from the network, but not given
permission to access locally. Whenever I try to access my desktop share
computer from my laptop, or laptop share from my desktop I get an error
the computer is not accessible because I don't have permission to
access it. When I give admin accounts on both computers permission to
access the computer via the network and while logged on to my admin
account (both computers have an account named "admin" with
administrative permissions and both have the same password) and I try
to access the opposing computer I have no problem.

After searching around the internet for awhile I found a troubleshooter
which suggested trying to access the network share use the command NET
USE from a command line. When I put in NET USE \\computername\share
name username: remote and my password when it asked I had no problem
logging on to the opposing computer and once I was logged if i went to
"my network places" and clicked on the opposing computer it let me
access the computer and its shares.

Now I seem to have hit my problem: the computers don't give me the
opportunity to enter a username or password when clicking on the
opposing computer in "my network places". I don't have that problem
when I try to connect to my server with SAMBA on it, it gives the popup
to enter the username and password and I enter it with no problem. Any
suggestions what to do?

Thanks in advance for the help,

Dan

 

[harryguy082589]

I know that u guys are busy, if thats the reason you passed over this i
understand, but if the reason is becuase i also use linux then well...
grow up

 

[Chuck]

Hi,

I have a network containing my desktop and laptop- both of which are
running XP pro and a SAMBA based server (I'm 15, and just hosting a
blog- cant afford windows at the moment).

I have my laptop and desktop configured with simple file sharing
disabled. Each computer has a account named "remote" which is given
permission to access the computer from the network, but not given
permission to access locally. Whenever I try to access my desktop share
computer from my laptop, or laptop share from my desktop I get an error
the computer is not accessible because I don't have permission to
access it. When I give admin accounts on both computers permission to
access the computer via the network and while logged on to my admin
account (both computers have an account named "admin" with
administrative permissions and both have the same password) and I try
to access the opposing computer I have no problem.

After searching around the internet for awhile I found a troubleshooter
which suggested trying to access the network share use the command NET
USE from a command line. When I put in NET USE \\computername\share
name username: remote and my password when it asked I had no problem
logging on to the opposing computer and once I was logged if i went to
"my network places" and clicked on the opposing computer it let me
access the computer and its shares.

Now I seem to have hit my problem: the computers don't give me the
opportunity to enter a username or password when clicking on the
opposing computer in "my network places". I don't have that problem
when I try to connect to my server with SAMBA on it, it gives the popup
to enter the username and password and I enter it with no problem. Any
suggestions what to do?

Thanks in advance for the help,

Dan

Dan,

How is this "remote" account setup, so it "is given permission to access the
computer from the network, but not given permission to access locally"?

Remember with a workgroup (or do you have a domain?), you may access remotely,
but you're using an account that's on the same computer as the data for
authentication.

To use a network share, you have to setup entries under both Sharing -
Permissions, and under Security, for the account in question.

You might find more help in this Microsoft document:
<http://www.microsoft.com/downloads/...db-aef8-4bef-925e-7ac9be791028&DisplayLang=en>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

 

[Malke]

I know that u guys are busy, if thats the reason you passed over this
i understand, but if the reason is becuase i also use linux then
well... grow up

No, it is *you* who needs to grow up. Your post was lengthy and a bit
confusing. It was difficult to determine exactly where (and what) the
problems were and what behavior you want from the various computers on
your network.

This is a public newsgroup and everyone who helps out is a volunteer. If
no one responded, it was because no one reading the group at that
particular time a) knew the answer; or b) wanted to take the time to
go through your post. Item b) was my case, and if you think it is
because you use Linux, look at my headers and think again.

I'm not going to read through your post again and try and pick out
exactly what problems you are having and whether it is with Linux or
Windows. Please repost clearly and concisely, using bullet-points or
some other way to make it short and sweet including your ultimate goal.
In the meantime, here are some tips to get a mixed-os network working:

Since you have such a small network (only 3 computers total, right?):

1. On each computer make identical user accounts/passwords. You can make
a "user" that covers many people if lots of people use these computers,
like for a school you might want "student" as a user.

2. On any Linux boxen, in *addition* to doing the above, in a console
do:

smbpasswd -a username [enter]
enter user's password [enter]
confirm user's password [enter]
read prompt that user was added

3. Create shares/resources as you wish and set permissions
appropriately.

4. If you want some resources to not be available to all users, create
user groups on the computers where you need them (on the Linux "server"
perhaps), set permissions on those groups, and assign users to those
groups. So if you want a particular folder on the server to be
read-only and only read-only by some users, that is what you do.

Now, think about what you are trying to accomplish and then post back
with a clear goal if you want more help.

Malke

(SuSE 9.3 Pro since your first post was from the web interface and your
second post was from Google Groups and I don't know if you can read
headers from a lame web interface - use a newsreader.)

 

[harryguy082589]

Thanks for the help, just to clarify my problem i am using a worklgroup
and have no problem with the samba server- i just used it as an example
to show that both computers will ask the for a user name when
connecting to the samba server.

Also, i looked both computers they are both setup exactly like the
microsft document suggests, and the shares work, but olny if go to a
command line and type in "NET USE \\computer\share /USERNAME:myname

 

[Chuck]

Thanks for the help, just to clarify my problem i am using a worklgroup
and have no problem with the samba server- i just used it as an example
to show that both computers will ask the for a user name when
connecting to the samba server.

Also, i looked both computers they are both setup exactly like the
microsft document suggests, and the shares work, but olny if go to a
command line and type in "NET USE \\computer\share /USERNAME:myname

Dan,

This sounds like a browser problem
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>

If not a browser problem, start here:
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.