Advertisement

11.25.2008 at 02:21PM PST, ID: 23935709
[x]
Attachment Details

Unable to Browse Network with AD Windows 2008 and XP workstations

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
6.2
Zones:

Windows Server 2008, Domain Name Service (DNS), Network Operations

Tags:

Microsoft, Windows Server, 2008
'll try to keep this quick and simple.

Running Windows 2008 Server with the following setup on the server
- Active Directory
- DNS
- Make sure that the network discovery is turned on through control panel/network

I have multiple XP 32/64 and Mac workstations (all fully updated XP 32-bit SP3, XP 64-bit SP2, OSX 10.5.5)

Trouble Shooting:
Thinking that after joining the domain, active directory should by default resolve the computers connected to them.  Well I was wrong.. so I ended up putting all the computer manually into the DNS records thinking it was the DNS that was causing the problem.. well that didn't work either.  Turned WIndows Firewall off on server and workstations.. no luck.  Tried to connect manually to computers via workstation name and ip (ex. \\Computername\  or  \\192.168.10.10... that works.   Everytime I try to view who is connected to the domain I get this error

"DOMAIN-NAME is not accessible. You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.

The Network path was not found"

Went to see the AD user and group settings, but couldn't find anything useful there.
Checked the Group Policy and still couldn't find anything.

I know that there is something I missed, but I can't seem to find it.
If you require more info please specify what information you need.
Start your 7 day free trial to see this answer
Answered By: PongBuddy
Expert Since: 11/18/2008
Accepted Solutions: 1
PongBuddy has been an Expert for 1 month, during which he has posted 9 comments and answered 1 question. PongBuddy is just one of 1271 experts in the Windows Server 2008 Zone. 3 experts collaborated on this answer, which was graded an "A" by the asker.
 
 
20081119-EE-VQP-48 - Hierarchy / EE_QW_2_20070628