<div>
Also when dcdiag is completed: &nbsp;at netlogons test i get error message: &nbsp;Entry point not found. &nbsp;The procedure entry point ?QueryComputerName@NET_NAM<wbr />E@@QAEJPAV<wbr />NLS_STR@@@<wbr />Z could not be located in the dynamic link library NETUI1.dll
</div>


<div>
Go in to the control panel, then administrative tools, then services. Put the services in order of status, and check all the automatic ones to make sure they all say &quot;Started&quot;. <br />
<br />
Check the server service. Make sure that is started. Also computer browser, and network. If any of the automatic services are not started - start them. <br />
<br />
If everything looks fine there, what happens when you type \\localhost from a run box. <br />
<br />

</div>


<div>
All services stared that are automatic except mr monitor and performance logs, but I don't think those would create the problem. &nbsp;computer browser and server are running. &nbsp;didn't see just a network service, there are network xx services, but none look important.<br />
<br />
All really looks good on the services<br />
<br />
When you type that in the run box I get &quot;no network provider accepted the given network path&quot;<br />
<br />
again, the workstations can see the file shares just fine (pre-mapped already when they log in)
</div>


<div>
It may also ask for your Windows server CD. its basically doing a integrity check of the important system files. 
</div>


<div>
That did it! &nbsp;Any guess as to what happened? &nbsp;Can you give me an idea of why you were leaning in this direction to do a system file check??<br />
<br />
Thanks a MILLION! &nbsp;You saved me a long night ahead........now I can still make it home by midnight!
</div>


<div>
Can't thank you enough again. &nbsp;Thank you, Thank you, Thank you
</div>


<div>
The sfc command checks important system files for corruption. it sounds like the server blue screened and corrupted some system files (because they wernt unloaded cleanly). SFC will scan those files and repair any damaged ones. Kind of like an advanced check disk - but for files :)<br />
<br />
Glad it's working. <br />
Cheers<br />

</div>


<div>
<div class="content wysiwyg-content">
Had a blue screen with server 2003 and it rebooted itself and came back up. &nbsp;Since then I am no longer able to access my \\servername or mapped drives ONLY FROM THE SERVER. &nbsp;The rest of the network is still working fine. &nbsp;I'm lost!<br />
<br />
Server is main DC with DNS<br />
Can ping server, and can ping name of server and properly resolves<br />
no problems from the clients. &nbsp;They can access the shares just fine.<br />
<br />
netbios over TCP/IP is enabled and WINS is set.<br />
<br />
when I attempt to access \\servername or \\server IP &nbsp;<br />
I get an error: &nbsp;no network provider accepted the given network path<br />
<br />
Dcdiag'ed<br />
Error out at LsaPolicy operation failed with error 1203, no network provider accepted the given network path.<br />
<br />
I also noticed that under entire network, microsoft windows network selection is gone. &nbsp;Only TS and Web Client show up.<br />
<br />
What happened? &nbsp;Please help. &nbsp;I need to be able to map a drive again at the server.<br />
<br />
Everything that I see as far as research goes points to a possible DNS issue. &nbsp;getting DNS issues in event viewer, asking me to check that AD is functioning properly.
</div>
</div>


Had a blue screen with server 2003 and it rebooted itself and came back up.  Since then I am no longer able to access my \\servername or mapped drives ONLY FROM THE SERVER.  The rest of the network is still working fine.  I'm lost!

Server is main DC with DNS
Can ping server, and can ping name of server and properly resolves
no problems from the clients.  They can access the shares just fine.

netbios over TCP/IP is enabled and WINS is set.

when I attempt to access \\servername or \\server IP  
I get an error:  no network provider accepted the given network path

Dcdiag'ed
Error out at LsaPolicy operation failed with error 1203, no network provider accepted the given network path.

I also noticed that under entire network, microsoft windows network selection is gone.  Only TS and Web Client show up.

What happened?  Please help.  I need to be able to map a drive again at the server.

Everything that I see as far as research goes points to a possible DNS issue.  getting DNS issues in event viewer, asking me to check that AD is functioning properly.

can't browse share files or see network from server

The Internet Protocol (IP) is the principal communications protocol in the Internet protocol suite for relaying datagrams across network boundaries, organized in abstraction layers, traditionally called "Link," "Internet," "Transport" and "Application”. Its routing function enables internetworking, and essentially establishes the Internet. IP defines packet structures that encapsulate the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information.

Internet Protocols

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.