Networking Forums

Networking Forums > Computer Networking > Windows Networking > Branch Office Networking

Reply
Thread Tools Display Modes

Branch Office Networking

 
 
Robert
Guest
Posts: n/a

 
      06-07-2008, 03:41 PM
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
 
Reply With Quote
 
 
 
 
Meinolf Weber
Guest
Posts: n/a

 
      06-07-2008, 03:58 PM
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
>



 
Reply With Quote
 
Robert
Guest
Posts: n/a

 
      06-07-2008, 04:43 PM
Everything 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
> >

>
>
>

 
Reply With Quote
 
Robert L. \(MS-MVP\)
Guest
Posts: n/a

 
      06-07-2008, 10:11 PM
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" <(E-Mail Removed)> wrote in message
news:637886DA-19EE-4425-A42A-(E-Mail Removed)...
> Everything 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
>> >

>>
>>
>>


 
Reply With Quote
 
Robert Craig
Guest
Posts: n/a

 
      06-08-2008, 04:40 AM
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)" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:637886DA-19EE-4425-A42A-(E-Mail Removed)...
>> Everything 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
>>> >
>>>
>>>
>>>

>

 
Reply With Quote
 
Meinolf Weber
Guest
Posts: n/a

 
      06-08-2008, 06:42 PM
Hello robert,

Change the DNS ip from the DNS server to the real ip address, loopback ip
127.0.0.1 sometimes creates unwanted problems although it should work.

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

> Everything 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



 
Reply With Quote
 
Robert Craig
Guest
Posts: n/a

 
      06-09-2008, 01:46 AM
OK guys, I changed the IP Address and gave it a day. I just checked the
error logs of my branch office computers and they are still generating the
same error code. This is just a hunch, but is there any way a VPN tunnel
can cause this?

Robert

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:(E-Mail Removed) .com...
> Hello robert,
>
> Change the DNS ip from the DNS server to the real ip address, loopback ip
> 127.0.0.1 sometimes creates unwanted problems although it should work.
>
> 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
>
>> Everything 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

>
>

 
Reply With Quote
 
Bill Grant
Guest
Posts: n/a

 
      06-09-2008, 02:54 AM
No, there is not much chance of this being a VPN tunnel problem.

A VPN link is simply a point-to-point link. What goes in on end comes out
the other. It isn't even affected by firewalls because the tunnel traffic is
encrypted end encapsulated as it goes through the firewall, so the firewall
only sees the "wrapper" of the packet.

Once the VPN link is set up, the two sites work just like any two subnets
joined by an IP router.
 
Reply With Quote
 
Robert Craig
Guest
Posts: n/a

 
      06-09-2008, 03:44 AM
Yeah, that's what I thought. I know it has to be something with DNS, but I
can't lay my finger on it. I rebuilt this domain about a month ago and
built it the exact same way I did in the original. I never had this problem
with the original domain. What really boggs my brain is this problem is
only affecting the branch office computers. Everyone else in the main
office doesn't have this problem.

Rob

"Bill Grant" <not.available@online> wrote in message
news:#(E-Mail Removed)...
> No, there is not much chance of this being a VPN tunnel problem.
>
> A VPN link is simply a point-to-point link. What goes in on end comes out
> the other. It isn't even affected by firewalls because the tunnel traffic
> is encrypted end encapsulated as it goes through the firewall, so the
> firewall only sees the "wrapper" of the packet.
>
> Once the VPN link is set up, the two sites work just like any two subnets
> joined by an IP router.


 
Reply With Quote
 
Robert Craig
Guest
Posts: n/a

 
      06-09-2008, 03:45 AM
Another thought. Should I install and start using Wins? I read an article
somewhere that if you had multiple subnets, you needed Wins.

Robert

"Robert Craig" <(E-Mail Removed)> wrote in message
news:AFF7F749-1A4F-4DD4-98CE-(E-Mail Removed)...
> OK guys, I changed the IP Address and gave it a day. I just checked the
> error logs of my branch office computers and they are still generating the
> same error code. This is just a hunch, but is there any way a VPN tunnel
> can cause this?
>
> Robert
>
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:(E-Mail Removed) .com...
>> Hello robert,
>>
>> Change the DNS ip from the DNS server to the real ip address, loopback ip
>> 127.0.0.1 sometimes creates unwanted problems although it should work.
>>
>> 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
>>
>>> Everything 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

>>
>>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Branch Office setup TJ Windows Networking 5 07-29-2008 11:56 AM
AD and a Branch office ecavedude Windows Networking 2 10-03-2007 01:43 PM
Connecting a branch office...HELP ecavedude Windows Networking 7 09-23-2007 04:24 PM
Branch Office Issues it-al Windows Networking 7 07-12-2007 06:14 AM
Branch Office/VPN Question melickas@yahoo.com Windows Networking 4 07-05-2006 10:41 PM



1 2 3 4 5 6 7 8 9 10 11