Home > Windows Server > Windows 2003 Server Cannot Access Shares

Windows 2003 Server Cannot Access Shares

Contents

I really do not have anything else to add to this thread, but would be interested in seeing the resulting fix, if you discover the problem... 0 LVL 12 Overall: then tried to connect from the DC with windows explorer and receive this msg \\server is not accessable. Always good to rule out DNS problems first. If issue still exists, try perform a SFC: 1. this contact form

But the sharing is much more important than the browsing, so ignore it for now. I feel like it's either a Computer Browser service problem or that it's somehow DNS-related, but I'm kinda baffled... Also remember that share permissions are not backed up with resource, so all backed up files are vulnerable as well, without any permissions protecting them. 0 LVL 1 Overall: Level Find a mistake in the following bogus proof Does Intel sell CPUs in ribbons?

Windows Server 2003 Shared Folder Not Accessible

Clock skew can cause a lot of headaches. –charlesbridge Sep 4 '09 at 18:58 1 Upvote, nice one mate, good list to start troubleshooting with.. –Greg Meehan Sep 4 '09 If that's the case, then name resolution is working and so it's not a DNS problem. Report • #9 Curt R September 26, 2012 at 07:31:01 That's a very unusual error....and fix. Contact the administrator of this server to find out if you have permission" When I try \\server\test I receive the following "no network provider accepted the given network path".

windows-server-2003 file-sharing print-server share|improve this question asked Sep 4 '09 at 17:12 colemanm 3395623 can you ping anything inside the network? What are your results?It matters not how straight the gate,How charged with punishments the scroll,I am the master of my fate;I am the captain of my soul.***William Henley*** Report • #2 I do not feel confident enough that we are ready to host our DNS completely from the in-house Win2K3 machine. Windows Server 2003 Shared Folder Permissions Check your SRV records in DNS, and/or on the local node check what the machine/logon sees as the DC. (You can do that by opening a command prompt, typing "set" and

There are many indications of the trojan horse and certainty is high. Windows Server 2003 Cannot Access Shared Folder Find the rate of change at a point on a polynomial Should I allow my child to make an alternate meal if they do not like anything served at mealtime? The master browser is probably the domain controller, and since its not accessible the browsing doesn't work. Any ideas you have either about how to get the AD running while maintaining the ISP DNS OR about how to just simple filesharing running would be EXTREMELY appreciated.

However, it is very difficult to get rid of. No Network Provider Accepted The Given Network Path Another would not allow for a device to view the shares if the device was using a DHCP address. All XP clients can access all shares on 2000 and 2003 servers. One would remove the Administrative and Domain shares on the server.

Windows Server 2003 Cannot Access Shared Folder

If so, please type the error exactly in reply. Even the DC cannot access the file server. Windows Server 2003 Shared Folder Not Accessible The 2000 servers were able to access these files on the 2nd server just fine. 4) I ran spybot on all machines; ran all Windows updates, ran anit-virus. Windows Server 2003 Network Share Not Accessible share|improve this answer answered Sep 4 '09 at 18:41 Jessica McKinnon 1,31769 1 And check the time on the server.

How to handle a common misconception when writing a Master's thesis? http://macinstruct.net/windows-server/windows-2003-server-cannot-access-internet.html What episode of Star Trek is this creature on? This can be beneficial to other community members reading the thread. I have tried following from Web1 over RDP connection: - pinging web2 or serverA - works fine - telnet web2 80 - doesn't want to connect. Windows 7 Can't Access Shared Folder On Windows Server 2003

Even with the Everyone object having permissions, you still need the usernames defined locally on the server.I personally think that you should go back to AD, but it may be a FE 0 LVL 15 Overall: Level 15 Windows Networking 13 MS Server OS 1 Message Expert Comment by:adamdrayer2008-02-04 Comment Utility Permalink(# a20818077) Hey FE =) Didn't realize it was you Promoted by Neal Stanborough Are you going to an event? navigate here However, I can't just type the IP and it'll find it.

At this point I am looking at everything twice. Thanks for the input Wednesday, November 10, 2010 7:25 PM Reply | Quote 0 Sign in to vote Hi, Please try to share a folder to Everyone and see whether you Always good to rule out DNS problems first.

Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the

Thanks for your help! There is a "permissions" button. 0 LVL 1 Overall: Level 1 Message Author Comment by:mjburgard2008-02-04 Comment Utility Permalink(# a20818885) More Info: 1) Only one Windows 2003 server does not We have given Full Control to everyone. Join & Ask a Question Need Help in Real-Time?

The sharing is. What is a satisfactory result of penetration testing assessment? Do the metadata dump and see what happens.I de-enabled WINS since IP sharing seemed to stop after I enabled it. his comment is here I have started to rebuild the user names, and at your suggestion, I just added my client machine login as a user on the server.

and you can ping the #2 from the 2K server.. Setting up a new domain is relatively straight forward in 2003 with all the wizards. Computing.Net and Purch hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy. After lots of reading, I decided I ought to just uninstall AD and DNS and focus on other day-to-day issues since school started today.

can he see shares on the xp clients? So make it easy on yourself and don't do it.You were correct in defining DNS Forwarders in your first attempt, but missed a couple of other steps which we can talk For some reason the W7 machine cannot connect to the User shares on our DC.