| Author |
Message |
MattMJF@Yahoo.com
Guest
|
 Posted:
Wed Nov 09, 2005 9:50 pm Post subject:
1 DC LAN Hosed "No network provider accepted the given netwo |
|
|
NETWORK: 1 Domain Controller - Windows Server 2003 sp1 standard and 4
WindowsXP sp2 (firewall turned off) clients and all are setup to
automatically update from Windows Update fully patched. This small
production LAN has been working just fine for over 1 year.
PROBLEM: on 11/6/5, SUDDENLY without any major change/cause; now when you
try to access a network path (FQDN) "start" "run"
"\\machine_name\share_name", and get error message “No network provider
accepted the given network path.” But when you open the Command Console
(“start“-“run“-“cmd“), you can ping that machine successfully by using the
FQDN. Network shares and browsing across the LAN is inaccessible!
TROUBLESHOOTING DONE: I verified DNS is operational along with DCDIAG
/test:dns, check workstation, netlogon, workstation & other pertinent
services are running and ran system file checker “sfc /scannow” utility. I
removed one workstation from the domain then tried to re-add only to get
error message 'domain controller can not be contacted' even though I can ping
it by IP address.
I search Google.com & support.microsoft.com but have not found anything to
resolve this sudden and dumbfounding problem. Any & All ideas, input and
solutions is GREATLY appreciated.
Any IT genius out there who leads me to solving this problem and saving me
from having to rebuild my W2K3 gets lunch on me!
~Matt
Feel free to contact me about this or other IT Systems Administrator things
at MattMJF@Yahoo.com |
|
| Back to top |
|
 |
Phil
Guest
|
| Posted:
Thu Nov 10, 2005 9:30 am Post subject:
RE: 1 DC LAN Hosed "No network provider accepted the given n |
|
|
Look at the recent patches applied, the ones that rolled out in October. Have
you check to see if your LanManager settings in Local Security Policy are the
same for server and client?
"MattMJF@Yahoo.com" wrote:
| Quote: | NETWORK: 1 Domain Controller - Windows Server 2003 sp1 standard and 4
WindowsXP sp2 (firewall turned off) clients and all are setup to
automatically update from Windows Update fully patched. This small
production LAN has been working just fine for over 1 year.
PROBLEM: on 11/6/5, SUDDENLY without any major change/cause; now when you
try to access a network path (FQDN) "start" "run"
"\\machine_name\share_name", and get error message “No network provider
accepted the given network path.” But when you open the Command Console
(“start“-“run“-“cmd“), you can ping that machine successfully by using the
FQDN. Network shares and browsing across the LAN is inaccessible!
TROUBLESHOOTING DONE: I verified DNS is operational along with DCDIAG
/test:dns, check workstation, netlogon, workstation & other pertinent
services are running and ran system file checker “sfc /scannow” utility. I
removed one workstation from the domain then tried to re-add only to get
error message 'domain controller can not be contacted' even though I can ping
it by IP address.
I search Google.com & support.microsoft.com but have not found anything to
resolve this sudden and dumbfounding problem. Any & All ideas, input and
solutions is GREATLY appreciated.
Any IT genius out there who leads me to solving this problem and saving me
from having to rebuild my W2K3 gets lunch on me!
~Matt
Feel free to contact me about this or other IT Systems Administrator things
at MattMJF@Yahoo.com |
|
|
| Back to top |
|
|
MattMJF@Yahoo.com
Guest
|
| Posted:
Fri Nov 11, 2005 5:50 pm Post subject:
RE: 1 DC LAN Hosed "No network provider accepted the given n |
|
|
Phil,
I have this small, 1 DC LAN set to automatically apply updates (which may be
a mistake but has have had no issues in over a year) and of the Oct. patches
nothing would indicate that could cause this problem.
Both the server and client are configured for send LM & NTLM responses.
When I try to add a machine to the domain I get this: error code 0x0000267c
dns_error_no_dns_servers
however DNS passes simple query test, DC diag comes back nothing etc.
I am dumbfounded.
"Phil" wrote:
| Quote: | Look at the recent patches applied, the ones that rolled out in October. Have
you check to see if your LanManager settings in Local Security Policy are the
same for server and client?
"MattMJF@Yahoo.com" wrote:
NETWORK: 1 Domain Controller - Windows Server 2003 sp1 standard and 4
WindowsXP sp2 (firewall turned off) clients and all are setup to
automatically update from Windows Update fully patched. This small
production LAN has been working just fine for over 1 year.
PROBLEM: on 11/6/5, SUDDENLY without any major change/cause; now when you
try to access a network path (FQDN) "start" "run"
"\\machine_name\share_name", and get error message “No network provider
accepted the given network path.” But when you open the Command Console
(“start“-“run“-“cmd“), you can ping that machine successfully by using the
FQDN. Network shares and browsing across the LAN is inaccessible!
TROUBLESHOOTING DONE: I verified DNS is operational along with DCDIAG
/test:dns, check workstation, netlogon, workstation & other pertinent
services are running and ran system file checker “sfc /scannow” utility. I
removed one workstation from the domain then tried to re-add only to get
error message 'domain controller can not be contacted' even though I can ping
it by IP address.
I search Google.com & support.microsoft.com but have not found anything to
resolve this sudden and dumbfounding problem. Any & All ideas, input and
solutions is GREATLY appreciated.
Any IT genius out there who leads me to solving this problem and saving me
from having to rebuild my W2K3 gets lunch on me!
~Matt
Feel free to contact me about this or other IT Systems Administrator things
at MattMJF@Yahoo.com |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in