Home > Server 2003 > Server 2003 Cannot Access Domain

Server 2003 Cannot Access Domain


could this be a firewall issue? –cop1152 Sep 4 '09 at 18:28 add a comment| 8 Answers 8 active oldest votes up vote 6 down vote accepted Check the event logs! Ask a question, help others, and get answers from the community Discussions Start a thread and discuss today's topics with top experts Blogs Read the latest tech blogs written by experienced There was an error processing your information. Now that I'm working at a small public charter school in a slightly smaller east coast city, it's the opposite scenario: On-call tech support is lacking/limited since we have limited funding, weblink

You don't know how much I appreciate it, really. Is the Čech cohomology of an orbifold isomorphic to its singular cohomology? file-sharing windows-server-2008-r2 computer-name share|improve this question asked Feb 6 '11 at 0:34 Justin Love 68621731 How is your DNS, DHCP and NetBIOS set? What happens when a wizard tries to cast a cone of cold through a wall of fire? my company

Windows Server 2003 Shared Folder Not Accessible

if yes, can you head to the place and are you able to see the files? Do the event logs report something? –Tom Wijsman Feb 6 '11 at 0:54 Both machines in question are statically assigned and Domain Controllers (hence DNS servers) I enabled NETBIOS Should I report it? asked 6 years ago viewed 631 times active 6 years ago Related 0Windows Cannot View Domain Location0Can't add client machine to windows server 2008 domain controller0Cannot connect Windows 7 machine to

Using the logs from the client, try to establish a timeframe of when the underlying problem first surfaced. I enabled WINS because it seemed to be the way to get some desktop clients to connect, and now IP sharing is no longer working. Basically, same procedure as above, but if you feel you don't remember the exact steps please read my Joining a Domain in Windows XP Pro and/or Joining a Domain in Windows Basic Geometric intuition, context is undergraduate mathematics During the untap step, can I copy a vehicle with Felhide Spiritbinder's Inspired trigger?

Asked: July 21, 20107:42 PM Last updated: September 15, 20114:10 PM Related Questions Windows 2003 file server cluster and exchange 2007 CCR Windows 7 Access 2007 SBS 2003 Problem Answer a Windows Server 2003 Cannot Access Network Shares You at least know your DNS server is setup correctly.Is it only steve-pc1 or all including the server?If just pc1 have it join a workgroup, delete the AD machine account and DNS = common problems with RPC, resolving, etc. click site Select Computer Name tab, click Change button.

can he see shares on the xp clients? Done gathering initial info. So are you telling us that you've removed the DC role from the server, and have placed the server back into a WORKGROUP, using the same workgroup name as the clients. What is a satisfactory result of penetration testing assessment?

Windows Server 2003 Cannot Access Network Shares

The Windows-based domain member thinks that its machine account password is something X, while the domain controller believes it to be something Y. By submitting you agree to receive email from TechTarget and its partners. Windows Server 2003 Shared Folder Not Accessible No matter what you do, you will not be able to log on to the computer by using a domain account. Windows Server 2003 Cannot Access Shared Folder grep with special expressions Help understanding these cake puns from a CNN Student News video Can Trump undo the UN climate change agreement?

Non-Repetitive Quine Does Intel sell CPUs in ribbons? http://stevemattley.com/server-2003/server-2003-r2-cannot-access.html You'll get a confirmation message. 6. Privacy Reply Processing your reply... I would have the servers IP addresses be private IP's and use NAT on your firewall to forward traffic from your webservers public IP to it's internal Private IP. Not Able To Access Shared Folder In Windows Server 2008 R2

Your answer currently does not seem to provide a workable solution to the question. We've got two Server 2003 servers, and only one of them is inaccessible via file sharing (browsing to \\machinename), the clients can all see the other server as well as each When I try to "Add A Network Place" from a client, I receive the message "The folder you entered does appear to be valid. check over here Connect with Daniel Petri Like on Facebook Follow on Twitter Circle on Google+ Subscribe via RSS Sponsors Join the Petri Insider Subscribe to the Petri Insider email newsletter to stay up

The only possible solution for logging on could be to use a local user account. had the same issue and I solved by doing that share|improve this answer answered May 24 '12 at 16:58 sean 111 add a comment| up vote 0 down vote I think If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.

I also created a generic user on the server and tried to map a directory and log on as this user.

Make sure that the Computer Browser, DNS Server, Network Logon, Server, and Workstation services are running on the domain controllers (also check DHCP if you are using DHCP in your office). All rights reserved. e.g. I can ping machine1 from the machine2 by its FQDN and ip.

can you RDP to it? Report • #9 Curt R September 26, 2012 at 07:31:01 That's a very unusual error....and fix. That didn't work either.7. http://stevemattley.com/server-2003/server-2003-windows-cannot-bind-to-domain.html Verify that the "Primary DNS suffix of this computer" field is blank.

Should I report it? Setting the date and time of both server and client right solved the problem for me. How to define a "final slide" in a beamer template? So why does this error happen?

Please try again later. The culprit was some component in the custom Symantec client I generated with v11 and had installed on the server a few days ago. 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 Either the Antispam, Antivirus, or Network Protection service must've hampered some other service...

The only thing not working is ANYTHING browsing network shares, specifically, on the DC. –colemanm Sep 4 '09 at 18:49 add a comment| up vote 1 down vote Some suggestions: Make 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 Peuge domain-name-system active-directory share|improve this question asked Mar 31 '10 at 14:11 Peuge EDIT: This might seem like a stupid question but here goes: The two servers are