Re: Filesharing by Windows server 2003 on workgroup

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Another consideration - set the share permissions for everyone full
permissions and then use the Security permissions to define who gets to
access it. This has changed with 2003 and I keep forgetting it - well, I'm
remembering it more now <G>.

Pegasus (MVP) wrote:

Some comments:

- As Brett observed: I wrote
net use Q: \\YourServer\SomeShare whereas you wrote
net use q:\\PCSERV\share
You omitted the space after "Q:"

- Did you define a share called "share" on your server?

- The error message you quote does not exist. Did you translate
it from a non-English language?

- Have you considered moving your workstations in a domain model?

<stephcanada2@xxxxxxxxxxx> wrote in message
news:1164587413.691388.126800@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I wrote exactly what you told me:

net use q:\\PCSERV\share

And receive a french error message meaning : "Error system 67 happened.
Impossible to find the network name.




On Nov 26, 6:58 pm, "Pegasus \(MVP\)" <I...@xxxxxxx> wrote:
I gave you a precise command to try. It was

net use Q: \\YourServer\SomeShare

Please post the exact command you used, and report the
message you see (verbatim, please!). Please do not use
terms such as "I still do not see the server" - they mean
next to nothing.

<stephcana...@xxxxxxxxxxx> wrote in
messagenews:1164584580.403213.250810@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I can ping the server without any problem, and the server can ping the
other PCs too.
I tried to log on under the same account/password from an other PC, but
still do not see the server.
I tried the command net use, but can't find the server neither.

Concerning the installation, I have installed the server with a
workgroup configuration (same as other PCs)

Stéph

On Nov 26, 6:19 pm, "Pegasus \(MVP\)" <I...@xxxxxxx> wrote:>
<stephcana...@xxxxxxxxxxx> wrote
inmessagenews:1164582806.135961.142400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx





Hi,

I work in a small company, and so far our computers (windows XP) were
simply linked together via a simple 4ports router.
To better manage files, we tried to install Windows server 2003 and
link it on the current workgroup, but the server in not visible by
any computers, and reciprocally, the server can't see any computer.

But the server can access internet without any problem via the
router.

Do you have any idea what I have to do to setup Windows server 2003
correctly, and make it accessible to other computers ?

Thanks,
StephI suspect you mix the terms "visible" and "accessible" with each
other.
If your workstations belong to a workgroup and the server does not
then the server shares may be invisible but they would still be
accessible.
Try these tests from a workstation:
- Ping the server. Does it work?
- Log on under an account/password that is identical to a server
account/password. Does it work?
- Type this command from a Command Prompt:
net use Q: \\YourServer\SomeShare
Does it work?- Hide quoted text -- Show quoted text -- Hide quoted
text -- Show quoted text -

--
Brett I. Holcomb
brettholcomb@xxxxxxxxxxxxxxxxx
Remove R777 to email
.

Relevant Pages

  • RE: Reinstall of companyweb
    ... you check the permissions on some related folders and files. ... permissions on the server. ... the default web site and companyweb site. ... You receive a "Service Unavailable" error message when you browse an IIS ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS problem not a problem in Web Matrix Server
    ... >I'm familiar enough with SQL Server to have already ... >>The error message tells you exactly what is wrong. ... >>could not logon. ... Grant this user account permissions to ...
    (microsoft.public.inetserver.iis)
  • Re: Reinstall of companyweb
    ... > after running CHKDSK and get error message "Service Unavailable", ... > you check the permissions on some related folders and files. ... > permissions on the server. ... the default web site and companyweb site. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server Unavailable - ASP.NET 2.0 on Windows XP
    ... Please review the permissions outlined in this article. ... Make sure that the HOME-WKSTATION\ASPNET account has been assigned NTFS ... So I switched to that directory in Command Prompt and tried the following... ... I'm still getting the "Server Unavailable" error... ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Semaphore failure. Rerun as root
    ... Application Server license. ... This error message may be caused by a missing semaphore file in ... The file should have R/W permissions for all, and should be chowned to root. ...
    (comp.lang.cobol)