Registered users    
MembershipMembership:
Latest New UserLatest:lovely raaaa
New TodayNew Today:9
New YesterdayNew Yesterday:13
User CountOverall:22448

Private messaging    
You must be logged in to use this module.
Top 10 posters    
NamePosts
Mariette Knap12480
Marina Roos11431
Eriq Neale2069
Michael Patrick1879
Stan Guinn1779
Robert Pearman1704
Nick Pieters1425
Stewart Brown607
Eddie Kerr534
Kevin D.519
Welcome unauthorized visitor    
If you want to join us in the discussions on this forum you need to register first. Registration is free! If you are already a registered user please login to join the forum.
Small Business Server Support Forum    
Subject: Branch office server : event 1054 logged
Prev Next
You are not authorized to post a reply.

Author Messages
Nicolas Rabaté User is Offline
France
Member since
7/1/2006

Platinum Membership
Posts: 32

5/08/2008 06:54 AM  
Hello,
 
SBS box : SBS std 2003/SP1, one NIC
Branch office server : win srv 2K3 R2, one NIC
Hardware firewall/router/VPN on both ends, same brand (zywall), no firewalll rules on VPN
 
Branch office server :
  • NETDIAG: only one error related to DC
  • Ping to sbs box using DNS that is sbs.domain.local  or any other PC in the SBS sub network: OK
  • Access to sysvol share \\domain.local\sysvol\doamin.local: OK
  • Active directory users and computers mmc: OK
 Event 1054 is logged on branch office server after boot and on a regularly basis afterwards
 ipconfig/all of both are attached. Any idea will be appreciated?

Attachment: 158185561271.txt
Attachment: 158185562754.txt

David Houston User is Offline
Ireland
Member since
3/6/2006

Registered Users
Posts: 88

5/09/2008 01:20 PM  
Why do you have the two dns servers on the client?
Usually they should only point to the SBS Server.
Have updated all the drivers for the processor and network cards?
Thanks
David

Usergroups: Learn more and help others, http://www.sbsgroups.com
Nicolas Rabaté User is Offline
France
Member since
7/1/2006

Platinum Membership
Posts: 32

5/09/2008 03:49 PM  
Hello David
 
2nd DNS has been removed. SBS DNS address is now the only one. Still fails.
Network drivers have been checked, no updates available. I would be surprised this could cause the problem. RPC communications have been checked using PortQueryUI in order to make sure that nothing was inadvertandly blocked by one of the routers. No problem have been noticed.
 
Well I'm stuck
 
Thank you
Nicolas
Marina Roos User is Offline
The Netherlands
Member since
3/24/2005

Forum Admins
Posts: 11431

5/09/2008 09:15 PM  
Hi Nicolas,
 
What are the vmadapters doing on the sbs server? Can you disable them if you are not using vmware on the sbs (and I wouldn't really recommend trying to do that on SBS in the first place)?
You are missing WINS on the SBS nic, and WINS is still needed when doing VPN (as well as Exchange still needs WINS).
Are you indeed running WINS server on the additional DC? Have you disabled the advanced features on the nics of both servers, as well as disabling them in the registry, the TCPIP key?
Does the additional DC have the sysvol and netlogon shares?

Marina Roos Smallbizserver.Net AdministratorMission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local  network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain'
Nicolas Rabaté User is Offline
France
Member since
7/1/2006

Platinum Membership
Posts: 32

5/10/2008 07:58 AM  

VMWAre : VMWare server has been installed and running for more than a year to support a specific business application. Test with both virtual interfaces deactivated has already been done with no change on the result

WINS: Well it has been running for more than 3 years like this. Shall I check installation of WINS service and add SBS IP to the WINS tab? Still could you be more specific on this need?

Are you indeed running WINS server on the additional DC? Have you disabled the advanced features on the nics of both servers, as well as disabling them in the registry, the TCPIP key?
I did that on the branch office, not on the SBS Box. Are you reffering to what is described in part 2?

Does the additional DC have the sysvol and netlogon shares? No and this is the problem. As described in previous thread :
  • NETDIAG: only one error related to DC
  • Ping to sbs box using DNS that is sbs.domain.local  or any other PC in the SBS sub network: OK
  • Access to sysvol share \\domain.local\sysvol\doamin.local: OK
  • Active directory users and computers mmc: OK

Thank you
Nicolas

Nicolas Rabaté User is Offline
France
Member since
7/1/2006

Platinum Membership
Posts: 32

5/13/2008 03:33 PM  
The problem has been fixed using the following procedure on both servers. Unfortunately I don't know if the fix applied to one of the server was the solution:
1. Expand "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters"
2. Change value for "Enable Journal Wrap Automatic Restore" from 0 to 1. If the DWORD Value does not exist, create a new one with the exact spelling as above, including spaces but without the quotes.
3. Stop the NTFRS Service (open a command prompt and type "net stop ntfrs")
4. Start the NTFRS Service (net start ntfrs)

5. Change value for "Enable Journal Wrap Automatic Restore" from 1 to 0.
 
Other interesting links related to time stamp and negative ping values :
 
Nicolas
You are not authorized to post a reply.
Forums > Microsoft Smallbusiness Server > Small Business Server 2003 > Branch office server : event 1054 logged



ActiveForums 3.7
Forum policy    
These Discussion Forums are dedicated to the discussion of the Small Business Server and related server and client software. For the benefit of the community please observe the following posting guidelines:
  1. No Advertising. This includes promotion of commercial products and non-commercial products which are not directly related to Small Business Server and related server and client software.
  2. No Flaming or Trolling.
  3. No Profanity, Racism, or Prejudice.
  4. Site Moderators have the final word on approving/removing a thread or post or comment.