Re: Branch Office Networking
- From: "Robert Craig" <craig.robert@xxxxxxxxxxx>
- Date: Sat, 7 Jun 2008 23:40:59 -0500
Ahh, thank you. I just changed it. I'll give it a day or so and see if the errors come back. Thanks for your help!
Robert
"Robert L. (MS-MVP)" <findemail@xxxxxxxxxxxxxxx> wrote in message news:uJattsOyIHA.2384@xxxxxxxxxxxxxxxxxxxxxxx
Event ID 1054 is DNS issue. The internal DNS should point to itself not 127.0.0.1. This search result may help too..
Troubleshooting Windows Event ID
Event ID 1054 - Windows cannot obtain the domain controller name for your computer ..... You also receive the Event ID 1054 in the application event log: ...
www.chicagotech.net/wineventid.htm
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Robert" <Robert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:637886DA-19EE-4425-A42A-666884307141@xxxxxxxxxxxxxxxxEverything you suggested is configured that way. Here is the information you
requested.
BRANCH OFFICE CLIENT
WINDOWS IP CONFIGURATION
HOST NAME................TSHOP1
PRIMARY DNS SUFFIX.......ATW.LOCAL
NODE TYPE................HYBRID
IP ROUTING ENABLED.......NO
WINS PROXY ENABLED.......NO
DNS SUFFIC SEARCH LIST...ATW.LOCAL
ETHERNET NIC
PHYSICAL ADDRESS.......BLAHBLAHBLAHBLAHBLAH
DHCP ENABLED...........NO
IP ADDRESS.............192.168.16.12
SUBNET MASK............255.255.255.0
DEFAULT GATEWAY........192.168.16.1 <<<-----THIS IS THE ROUTER ON THE
BRANCH OFFICE SIDE
DNS SERVERS............192.168.15.3 <<<-----DNS SERVER AT MAIN OFFICE
SERVER AT MAIN OFFICE
wINDOWS IP CONFIGURATION
HOST NAME................ATWDC1
PRIMARY DNS SUFFIX.......ATW.LOCAL
NODE TYPE................UNKNOWN
IP ROUTING ENABLED.......NO
WINS PROXY ENABLED.......NO
DNS SUFFIC SEARCH LIST...ATW.LOCAL
ETHERNET NIC
PHYSICAL ADDRESS.......BLAHBLAHBLAHBLAHBLAH
DHCP ENABLED...........NO
IP ADDRESS.............192.168.15.3
SUBNET MASK............255.255.255.0
DEFAULT GATEWAY........192.168.15.1 <<<-----THIS IS THE ROUTER ON THE MAIN
OFFICE SIDE
DNS SERVERS............127.0.0.1
"Meinolf Weber" wrote:
Hello robert,
Make sure that no external DNS servers are configured on any NIC on the machines,
use only the domain internal DNS servers. Please post an unedited ipconfig
/all from the problem machine and the DC/DNS servers you use.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> I have a branch office that is connected to the main office via VPN
> routers.
> Everything works fine (able to access network, email, dns, etc.). But
> for
> some reason my error logs on the branch office computers keep filling
> up with
> error (1054 Windows cannot obtain the domain controller name for your
> computer network. (An unexpected network error occurred. ). Group
> Policy
> processing aborted.). Yet, when I do a manual gpupdate /force from
> the
> command prompt, the error log says Successful. I've tried various
> network
> diagnostics tools and haven't been able to find any problems. Anyone
> have
> any ideas?
> Server 2003 - DNS - Two subnets
> Using hardware router for entire network (NOT USING RRAS)
> Robert
>
- References:
- Re: Branch Office Networking
- From: Meinolf Weber
- Re: Branch Office Networking
- From: Robert
- Re: Branch Office Networking
- From: Robert L. \(MS-MVP\)
- Re: Branch Office Networking
- Prev by Date: Re: IPConfig is blank
- Next by Date: Re: Browsing domains across a WAN
- Previous by thread: Re: Branch Office Networking
- Next by thread: Re: Branch Office Networking
- Index(es):
Relevant Pages
|
Loading