Users Can't Access Documents on Server
Lee Schaeffer
access the server through their "My Documents", or by browsing the network
through "My Network Neighborhood", it asks for a user name and password.
Even if you supply a correct username and password it continues to ask and
doesn't log you in.
Exchange and internet seems to be still working fine for each user.
I'm getting 1030 and 1058 messages on the clients even viewer, but not on
the server.
We had tried the steps Microsoft said to do for "Connecting Macintosh OS X
10.3 and Higher Clients to a Windows Small Business Server 2003 Network"
and I'm wondering if that messed something up. These instructions did not
work with our Mac.
Thanks for any help in working me through this problem.
Jenny wu [MSFT]
Thanks for using the SBS newsgroup.
From your description, I understand the issue to be:
1. Windows XP clients can not access the documents on the server box and
received error event 1030 and 1058.
2. The Mac clients can not communicate with the server box.
If I am off base, please don't hesitate to let me know.
Microsoft engineers can only focus on one issue per thread. To ensure your
question is responded timely and efficiently, you can create a new thread
to post the second question. This way can make sure that the responders can
better track the problem Thank you for your understanding.
Let us focus the first problem first.
=============================
As well as we know, if a workstation would not access network shares, then
UserENV error 1030 and 1058 will be logged because domain group policies
are unable to apply. Please double check the following settings to see if
the issue be fixed:
I. Examine the DNS settings and network properties on the servers and
client computers.
1. Leave the Default Gateway of the internal NIC blank of the server box.
2. Configure the internal client computer's NIC and the internal NIC of the
server box to use the internal DNS Service (the internal NIC IP) as the DNS
Server. And there is only the DNS server be configured on client computers.
After verified them and then try to logon to domain, how about the result?
II. Make sure that the TCP/IP NetBIOS Helper service, the Net Logon
service, and the Remote Procedure Call (RPC) service are started on all
computers.
I''d like to recommend that you turn off and then turn on NetBIOS over
TCP/IP to see if we can eliminate this problem.
1. Click Start, click Control Panel, and then click "Network and Internet
Connections".
2. Click Network Connections.
3. Right-click Local Area Connection, and then click Properties.
4. Click Internet Protocol (TCP/IP), and then click Properties.
5. Click the General tab, and then click Advanced.
6. Click the WINS tab.
7. Under "NetBIOS setting", click "Disable NetBIOS over TCP/IP", and then
click OK two times.
8. Click Close to close the "Local Area Connection Properties" dialog box.
9. Close the Network Connections window and reboot the computer.
10. Repeat the steps above but select "Enable NetBIOS over TCP/IP" this
time.
And then please try to logon domain again, how about the result?
III. Make sure that Distributed File System (DFS) is NOT disabled on the
SBS server box and all computers.
You can refer to the following steps to turn DFS clients:
1. Click Start, and then click Run.
2. In the Open box, type regedt32, and then click OK.
3. In the Registry Editor window, locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup
4. In the right details pane, double-click DisableDFS.
The DFS client is turned off if the value in the Value data box is 1.
The DFS client is turned on if the value in the Value data box is 0.
5. In the Edit DWORD Value dialog box that appears, type 0 in the Value
data box, and then click OK.
6. On the File menu, click Exit to quit Registry Editor.
And then test, how about the result?
IV. If the issue persists, Please temporarily disable all the firewalls
(personal firewall and Internet Connection Firewall) on workstations and
server box. And then test and tell me the result.
And also please take a look at the following article to see if the hotfix
can fix your problem.
Error Messages When You Open or Copy Network Files on Windows XP SP1
Clients That Require SMB Signing
http://support.microsoft.com/?id=810907
If the issue persists, please kindly help me collect some information to
isolate the issue:
1. When client computers logon domain, what error message they got? Please
tell me the exact error message.
2. Please try to access the shared resources on the server with domain
admin user account from client computers, what is the result?
3. Please try to ping the SBS server box from client computer, and paste
the output in the newsgroup.
4. If the SBS server is reachable, use the "nltest /dsgetdc:<domainname>"
command to verify that a domain controller can be located from workstation.
The NLTest tool is installed with the
Windows XP support tools.
For information about how to install these tools, refer to the following
article in the Microsoft Knowledge Base:
306794 How to Install the Support Tools from the Windows XP CD-ROM
http://support.microsoft.com/?id=306794
What is more, I would like to introduce some documents and links regarding
to connect MAC Clients to SBS 2003, hope it helps-)!
You may encounter problems in connecting MAC Clients to SBS 2003 and if so
you need to download the latest version of UAM from the following page and
install it on the MAC clients:
http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=windows200
0sfm
834498 Macintosh client cannot connect to Services for Mac on Windows Server
http://support.microsoft.com/?id=834498
836413 You receive an "unexpected error occurred" error message when you
try to
http://support.microsoft.com/?id=836413
And the following article should be useful to you to setup Macintosh
clients in SBS network:
http://pentechcom.com/sbsdocblog/sbs_mac_beta.doc
Windows Server 2003 Server and Macintosh
http://www.macwindows.com/Win2003.html
Hope above information helps! I am happy to be assistance of you and look
forward to your reply!
Have a nice day!
Sincerely,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Lee Schaeffer" <l...@infinityconcepts.net>
>Subject: Users Can't Access Documents on Server
>Date: Wed, 25 Jan 2006 14:07:15 -0500
>Lines: 20
>Organization: infinityconcepts.net
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Message-ID: <ei2gPKe...@tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: 67.141.199.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:239325
>X-Tomcat-NG: microsoft.public.windows.server.sbs
Lanwench [MVP - Exchange]
In news:ei2gPKe...@tk2msftngp13.phx.gbl,
Lee Schaeffer <l...@infinityconcepts.net> typed:
> Our Windows XP users can't access documents on the server. If you
> try to access the server through their "My Documents", or by browsing
> the network through "My Network Neighborhood", it asks for a user
> name and password. Even if you supply a correct username and password
> it continues to ask and doesn't log you in.
Are these users logging into the domain, or local workstation accounts?
What are the share permissions on the folders in question? And the NTFS
permissions?
Lee Schaeffer
I'll work on trying out each of the steps you mentioned. In the meantime, I
took my PC, restored it to the point right before I first added it to the
domain and re-did the Connect to Network Wizard.
Everything seems to be working correctly now.
One weird thing in that process though, is that I had to remove and then add
my computer to the network on the server. When I went through the
Connection Wizard none of the computers were listed. Is that because the
server knew they were already added?
Does any of that help pin point what the problem maybe? Hopefully there is
a simplier solution then what I did to correct the problem.
-Lee
""Jenny wu [MSFT]"" <v-ya...@online.microsoft.com> wrote in message
news:V3ZI7BjI...@TK2MSFTNGXA02.phx.gbl...
Lanwench [MVP - Exchange]
In news:uG5nlqoI...@TK2MSFTNGP09.phx.gbl,
Lee Schaeffer <l...@infinityconcepts.net> typed:
> Jenny,
>
> I'll work on trying out each of the steps you mentioned. In the
> meantime, I took my PC, restored it to the point right before I first
> added it to the domain and re-did the Connect to Network Wizard.
>
> Everything seems to be working correctly now.
>
> One weird thing in that process though, is that I had to remove and
> then add my computer to the network on the server. When I went
> through the Connection Wizard none of the computers were listed. Is
> that because the server knew they were already added?
Did you not see the computers in the Server Management taskpad section?
How did you add the computers to the domain in the first place?
Lee Schaeffer
> client computers.
>
Still didn't work
> II. Make sure that the TCP/IP NetBIOS Helper service, the Net Logon
> service, and the Remote Procedure Call (RPC) service are started on all
> computers.
>
> I''d like to recommend that you turn off and then turn on NetBIOS over
> TCP/IP to see if we can eliminate this problem.
Still didn't work
> III. Make sure that Distributed File System (DFS) is NOT disabled on the
> SBS server box and all computers.
> 4. In the right details pane, double-click DisableDFS.
I did not see the option for DisableDFS on either the server, my PC or
another PC that still has the problem.
> IV. If the issue persists, Please temporarily disable all the firewalls
> (personal firewall and Internet Connection Firewall) on workstations and
> server box. And then test and tell me the result.
I was unable to disable the windows firewall on the PC.
> And also please take a look at the following article to see if the hotfix
> can fix your problem.
>
> Error Messages When You Open or Copy Network Files on Windows XP SP1
> Clients That Require SMB Signing
> http://support.microsoft.com/?id=810907
I'm not getting any of the symptoms mentioned with that hotfix.
> If the issue persists, please kindly help me collect some information to
> isolate the issue:
>
> 1. When client computers logon domain, what error message they got? Please
> tell me the exact error message.
When you first login to Windows, it appears that it's logging you on to the
computer as if you were offline.
If you try to access "My Documents", it asks you for a user name and
password to connect to the server. It never gives an error message. It just
keeps asking for a usernname and password no matter what you used. The only
thing it does do is afer your first attempt it changes the username to
domain/username.
> 2. Please try to access the shared resources on the server with domain
> admin user account from client computers, what is the result?
Does not work. Acts the same as above.
> 3. Please try to ping the SBS server box from client computer, and paste
> the output in the newsgroup.
Pinging 192.168.16.2 with 32 bytes of data:
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.16.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
> 4. If the SBS server is reachable, use the "nltest /dsgetdc:<domainname>"
> command to verify that a domain controller can be located from
> workstation.
DC: \\ic.Infinity.office
Address: \\192.168.16.2
Dom Guid: 77fd8315-49f7-4523-b65e-416b8137793d
Dom Name: Infinity.office
Forest Name: Infinity.office
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST
CLOSE_SITE
The command completed successfully
Lee Schaeffer
I see all the computers I originally added in the Server Management, but
didn't see them on the client when I was going through the wizard. I removed
the computer on the server, added the computer on the server, ran the wizard
on the client again and saw the computer I added.
> How did you add the computers to the domain in the first place?
Same way. Through the "add user computers" in the Server Managment.
Jenny wu [MSFT]
Thanks for your information.
>>One weird thing in that process though, is that I had to remove and then
add my computer to the network on the server. When I went through the
Connection Wizard none of the computers were listed. Is that because the
server knew they were already added?
If we want to re-join workstations to domain, we need to remove the
computer object from network and re-join it to "workgroup", then add it
using Setup Client Computers wizard (server management console -> client
computers -> Setup Client Computers) to add the computer to domain and run
add computer wizard (connectcomputer) to re-join it to domain. You can
refer to the following steps:
1. Quit the workstation from the domain. To do so, see:
Locate in Client Computers in Server Management console and choose the
computer the customer has in right panel. Click Remove from network link to
delete the computer from domain.
2). Setup the client computer by running Setup Client Computer wizard to
setup computer account.
3). Join the workstation to workgroup (My computers -> Computer name ->
Change -> Member of -> Workgroup).
3). Log off and then re-logon the workstation with administrator user
account, try to join it to domain by running
http://servername/connectcomputer. And assign appropriate user accounts to
the computer.
Note: Please ensure you have added the SBS Site (http://FQDN/*) in trusted
site in IE of the laptop. You can refer to the following steps:
a. Start Internet Explorer.
b. On the Tools menu, click Internet Options.
c. On the Security tab, click Local intranet zone, and then click Sites.
d. Click Advanced.
e. In the Add this Web site to the zone box, type the ConnectComputer
server's IP address or the ConnectComputer server's FQDN, and then click
Add.
Then please test the issue again, what is the result?
Please let me know if you have any further question on the issue, we are
glad to help.
Additionally I will be out of office from 28th Jan to 5th Feb with limited
internet access. The email response will be delayed. For Microsoft
newsgroup user, please do not hesitate to contact my backup engineer, Cliff
Zhang at jun...@microsoft.com, and he will be glad to be of assistance. I
am sorry for bring you inconvenience.
Have a nice day!
Sincerely,
>References: <ei2gPKe...@tk2msftngp13.phx.gbl>
<V3ZI7BjI...@TK2MSFTNGXA02.phx.gbl>
<uG5nlqoI...@TK2MSFTNGP09.phx.gbl>
<OKGK6Qp...@TK2MSFTNGP14.phx.gbl>
>Subject: Re: Users Can't Access Documents on Server
>Date: Thu, 26 Jan 2006 11:25:20 -0500
>Lines: 12
>Organization: Infinity Concepts.net
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>X-RFC2646: Format=Flowed; Response
>Message-ID: <u5wyZUp...@TK2MSFTNGP11.phx.gbl>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: 67.141.199.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:239538
>X-Tomcat-NG: microsoft.public.windows.server.sbs
Jenny wu [MSFT]
Thanks for your update. I am sorry for the delayed response due to weekend
and my leave. Please understand that the newsgroups are staffed weekdays by
Microsoft Support professionals to answer your systems and applications
questions. Your understanding is greatly appreciated!
I am glad to know that things are getting fine now. I appreciate your time
and effort to the issue and get this resolved.
Please feel free to post back when you need further assistance on this
issue and you are always welcome-)!
Have a nice day!
Sincerely,
The customer mail content:
======================
Bill,
I got the issue resolved by doing a system restore to a date before the
problem occurred, removing the client from the domain and running the
connect to network wizard again.
Thanks for checking up on us and our problem. We have another issue that I
posted today, but we are up and running without too many problems. :)
-Lee
======================
--------------------
>X-Tomcat-ID: 166598382
>References: <ei2gPKe...@tk2msftngp13.phx.gbl>
<V3ZI7BjI...@TK2MSFTNGXA02.phx.gbl>
<uG5nlqoI...@TK2MSFTNGP09.phx.gbl>
<OKGK6Qp...@TK2MSFTNGP14.phx.gbl>
<u5wyZUp...@TK2MSFTNGP11.phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain
>Content-Transfer-Encoding: 7bit
>From: v-ya...@online.microsoft.com ("Jenny wu [MSFT]")
>Organization: Microsoft
>Date: Fri, 27 Jan 2006 08:01:01 GMT
>Subject: Re: Users Can't Access Documents on Server
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>Message-ID: <78GGWfxI...@TK2MSFTNGXA02.phx.gbl>
>Newsgroups: microsoft.public.windows.server.sbs
>Lines: 132
>Path: TK2MSFTNGXA02.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:239708
>NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122