SBS 2003 domain

[knarf]

Problem is i can map a drive using UNC path but i cannot browse the network or see the network map. I have discovery turned on and i am using static IP addresses. i also have enable netbios over tcip enabled. My sbs server is setup as the 1# dns. Any suggestions would be great!
Thanks!

Happy Holidays!

 

[knarf]

bump

 

[RedBirdDad]

Have you joined the domain and is the SBS server set up to share drives and folders with the proper permisssions?

 

[patwhatsthat]

I am running SBS 2k3 as a DC and it is the primary DNS resolver for my domain and am not having any problems. Just what you wanted to here right. Did you have any problems joining the Win7 machine to the domain as RedBirdDad suggested? If not, then examine the netbios cache on the Win 7 machine, first flush it by typing nbtstat -R at a command prompt, then ping by name your SBS 2k3 server, then type nbtstat -c at a command prompt and see if it contains the netbios name of the server. If you're still having trouble then you could force the netbios informations by either adding WINS to the SBS 2k3 server (not exactly what I would do but) or edit the LMhost file on the Win 7 machine and see if that helps. Or simply remove the Win 7 machine from the domain and try re-adding it.

 

[knarf]

I have joined the domain, i can get email from the exchange server via outlook, i can mapdrives typing in unc paths but cannot browse a network map but the xp machines and servers can see my workstation.

 

[knarf]

Yes and the shares and permissions are setup this network has been up for 3 years and it is 1st non win xp / windows server (2000/2003/sbs2003) os install on it.

 

[PooMan UK]

Did you connect the workstation to the domain using the //domainname/connectcomputer via internet explorer or did you use the "system properties - computer name tab" option ?
Also what service pack are you using on the server ?

Connecting via your browser does way more than manually connecting the computer to the network through the control panel:

First, there's the whole server site setup that enables and configures
dependencies and configuration options that connectcomputer funcionality
uses.

1. Checks Client OS and takes appropriate path (ATAP)
2. Causes an activex control to become available.
3. Determines whether the computer is or is not a member of the domain, and
is or is not a DC or SBS server, (ATAP)
4. Tests resolution to the SBS server (ATAP)
5. Checks for multiple non VPN network connections (ATAP)
6. Checks account permissions, allowed to join computer to domain?
7. Assigns users, and migrates local profile(s), if they exist, to domain
profile (SID mapping)
8. Assigns requered local permissions to domain user account.
9. Provides selection of computer name from list, automatically if there is
one-to-one mapping of user/computer on the SBS.
10. Joins the domain (creating a temp user account for autologon to ease the
process) - including getting the client computer in the correct AD OU so the
GP applies correctly.
11. Sets some runonce reg keys to clean up after the above process.
12. After required input is provided, steps through the above process,
including automatic restarts as required.
13. Now we are into Application Deployment
This is seen on the workstation as the Client Setup Wizard, which is
automatic on login after the above 12 main steps are complete.
14. The list of configurations made after Application deployment:
My network places
TAPI information
Connection Manager
Fax Printer
SSL Certificate
ActiveSync (special, just for SBS and mobility devices)
IE
Outlook
Additional global settings:
DNS Timeout Value
Deleted Item Recovey
Remote Desktop permissions
Network Printer(s)
Disable getting started screen (annoying XP thing)
Disable ICS
(used to turn off ICF, but now handled by GP (xp firewall settings))
Disables network bridging

 

[patwhatsthat]

Also check the Win 7 machine and make sure that the TCP/IP NetBIOS Helper service is running as well as the computer browser service

 

[knarf]

... sometimes i forget it is microsoft... i left the domain and rejoined it and what do you know... lol thanks for the help all

 

[patwhatsthat]

I am running SBS 2k3 as a DC and it is the primary DNS resolver for my domain and am not having any problems. Just what you wanted to here right. Did you have any problems joining the Win7 machine to the domain as RedBirdDad suggested? If not, then examine the netbios cache on the Win 7 machine, first flush it by typing nbtstat -R at a command prompt, then ping by name your SBS 2k3 server, then type nbtstat -c at a command prompt and see if it contains the netbios name of the server. If you're still having trouble then you could force the netbios informations by either adding WINS to the SBS 2k3 server (not exactly what I would do but) or edit the LMhost file on the Win 7 machine and see if that helps. Or simply remove the Win 7 machine from the domain and try re-adding it.

Yep, that was one of my suggestions in an earlier post here. Microsoft will be Microsoft.