• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 858
  • Last Modified:

Windows Server Computer Broswer service Event ID 8021 & 8032 on Member server

I have on DC running Windows server 2003 std, also acts as DNS & DHCP server.  I have a second server member server that runs Windows server 2003 std with Exchange 2003 std,  On the member server I keep receiving Event ID: 8032 Source: Browser.  I cannot browse the network throu Network Places on the member server or any of the XP Clients.  I receive the message "The %domainname% is not accessible.  You might not have permission to use this network resource."

I have tried checking the registry value on the member server in HKLM\Software\CurrentControlSet\Services\Browser\Parameters\IsDomainMaster=FALSE

How can I get the memberserver to retreive a copy of the browser list & how can I correct the issue of being able to browse via Network Places?  Do I need WINS?
0
Zorniac
Asked:
Zorniac
  • 6
  • 4
1 Solution
 
DenverRickCommented:
Check the Messenger service on your DC, it needs to be running.

Run NetDiag (install Tools from CD) on both machines and see if you get any errors.
0
 
ZorniacAuthor Commented:
I enabled Messenger service on both the DC and Member server, installed Support tools and restarted.  So far I don't see the any events from the browser service.  I ran net diag on the DC and member server with the following results.
DC= Passed everthing, skipped WINS, Trust relationship,  WAN, IP security tests
Member Srv= Failed DC List Test "Failed to Enumerate DC's using the browser. [ERROR_NO_BROWSER_SEVERS_FOUND] skipped WINS, WAN, IP security tests
Was not able to browse network either.

Not sure if this has any impact on the browser service, noticed on DC I receive and Event ID 4319 "dupicate name been detected on the TCP network", this I beleive is because my servers are multihomed.
0
 
DenverRickCommented:
Check your DNS settings on both machines.  The DC should have its own address in the primary, and so should the member.

Now about Multihomed 2003 machines...

1- make sure only one NIC has a gateway.
2- Two NIC's should not be on the same subnet unless they are Teamed
3- DNS should be the internal DNS (DC) on all NIC's
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
ZorniacAuthor Commented:
The DC has 127.0.0.1 as it's DNS on both NIC's.  The member is set for the IP address of the DC which is 10.100.100.16 & 10.100.100.17.  So I should set the member server to it's own ip too (does using the loopback addr. make a difference)?

XP client's DNS points to DC's NIC's

Touching on the two NIC's does enabling Load Balancing via the checkbox, all that it requires to load balance?  
0
 
ZorniacAuthor Commented:
changed member server's primary DNS to it's own IP (loopback & defined IP) then ran netdiag, pretty much every test failed.  I also disabled one of each of the two NIC's, so now the DC & member server are only connected with one NIC each.  
0
 
ZorniacAuthor Commented:
DRick-  I restarted the Member server, I noticed that when I disabled one NIC on each server that I received a BROWSER forced election in the event viewer on the DC and Membersrv.  After restarting the Member server I am now able to browse the network on the servers and on my XP workstations.  
Thanks for your help.  I will reward you all the points with an A grade.  

But do you have any thoughts on why it did this, obviously related to Multihoming right?  Can't I use the load balancing feature built-in with both NIC's to maximize my performance and still use the broswer service?  

Thanks again and any advice regarding those NICS is appreciated.  since it's a seperate question if you want I can open up another post.... Just let me know
0
 
DenverRickCommented:
Depends on what you were doing with the second NIC.  Generally a 2nd NIC is for a second network, being used either to make the server a Router between the two subnets, or say in a DMZ to the Internet with a Public Address, the DMZ coming through a Firewall that allows just enough for whatever service(s) need, i.e. Exchange.

On a big system, say several hundred heavy load workstations, you can Team NIC's for increased bandwidth to Switches that can actually handle that much traffic.  I do see this application some times in smaller networks where it is for Redundancy, so basically the traffic is flowing over one NIC to the Switch, with the second NIC standing by in case of loss of link on the primary.

Does that all make sense?
0
 
DenverRickCommented:
By the way, I see guys setting up Teaming on Servers that don't have the speed (processor, RAID, etc) to push that much bandwidth, so they're actually not gaining anything.
0
 
ZorniacAuthor Commented:
Yeah that makes sense, I knew about using it for connecting different subnets but thought I would get large performance jump by enabling the load balancing.  But given that all NIC's in my current situation are running gigabyte with 100 or < wks attached, I believe what I have now is sufficient

Thanks again for your help, my server Event Viewer logs are now prestine.

0
 
ZorniacAuthor Commented:
This answer in conjunction with DenverRick's first answer were the answer to solving this problem
0

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now