Yes, both services are running.
Main Topics
Browse All TopicsWe've recently installed a second Exchange 2003 server into a domain. Currently it's co-existing with another Exchange server until all the mailbox moves can be done. Everything is working great with one exception. I can't see the new server in My Network Places from any other system. I can access the server via Remote Desktop using the server name, and I can also get to it using \\<servername> via the Run command. I can PING the server by both servername and IP address. The main problem this is causing is not being able to add the server to my scheduled backups in BackupExec. Any suggestions as to why this server can't be seen? As always, I appreciate all the help!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
In the Network Properties - TCP/IP properties of the Exchange server, is the WINS address configured with the IP address of the WINS server on your network? If it is, open a command prompt and run the command nbtstat -RR (RR is case sensitive). Then go to your WINS server and display the database and ensure that there is a listing for the new Exchange server. This should propagate via the browser (assuming that NetBIOS is configuired for all servers and they are all pointing to the WINS server for NetBIOS name resolution.
No you're not being super ignorant, its just that MS hasn't dropped NetBIOS support for certain aspects of the operating system. Everything that MS talks in W2K and W2K3 and now W2K8 is DNS, DNS, DNS. They never mention NetBIOS anymore, but there is a requirement for it if you want things like the browser service to work.
My Network Places utilizes the old browser service which is NetBIOS based. The replacement for the browser is AD, but that isn't incorporated into the old utilities. If you want the browser service to work correctly then you need to be running NetBIOS over TCP/IP on your servers and workstations and you need a NetBIOS name resolution (WINS) infrastructure.
Take a look at http://support.microsoft.c
OCON is super right, with one exception that should be noted:
Not to take away from the super advice given above: WINS is not necessary unless you are trying to route netbios. By routing, I mean going over a VPN connection across to a different subnets or across NAT. This comes from Netbios not being routeable. So, WINS is the transport between the sites that need to route Netbios broadcasts. If all of your servers and PCs reside on the same subnet and are not going through NAT or a VPN tunnel, then just enabling netbios over TCP/IP will do for you.
@OCON: This particular article is an easier read and is perfectly fits 2003 server. It has free body diagrams and explains the registry edits. I have used it to fix over 100 EE issues with the browser service. I thought you might like it.
NOTE: there is only one tiny difference between the NT4 and 2003 server Browser service:
On NT4 the registry key for the domain master is "Isdomainmasterbrowser"
On 2003 server the registry key for the domain master is shortened to "Isdomainmaster"
http://www.microsoft.com/r
If you are going over a route, use the WINS/WAN configuration of the browser service. Also make your remote DC a Global catalog server. Then, if your computers are on a remote site and connect to this, they will log onto that server for AD and will also look at that server for the browse list and the WINS connection back to the Domain master.
ChiefIT, thanks for the link. I've seen that one before, but never can find it again when I need it. This time I'll add it to my favorites.
BTW - WINS is not a transport, it is a naming service. It translates NetBIOS names to IP addresses, much like DNS for Internet domain names. The transport for NetBIOS is TCP/IP within the MS architecture. The NetBIOS is encapsulated within TCP/IP in order to make it routable.
Not so sure about your last paragraph. NetBIOS knows nothing about AD and therefore nothing about the GC. Also a host that needs the browse list does not query a DC for WINS info.
The browse list comes from the Master Browser on the local network segment. If there is a DC on this segment, then you're right. However, if it is a segment of nothing but workstations or WS's and member servers, etc., then the browser election process determines the master browser. It is the Master Browser for the segment that gets the entire domain browse list from the Domain Master Browser, which is the PDC emulator in a W2K or W2K3 domain.
It is the Master Browser that needs to find the PDC emulator and this is not done in AD/DNS. The master browser will query the WINS server for the record (IP Address) of the server that is the PDC. The WINS server returns the IP address and then the Master Browser requests the browse list from the PDC.
The WINS server that will be queryed by the host is determined by the configuration in the TCP/IP settings of the NIC. All of the hosts including workstations, member servers and domain controllers must be configured to go to the server hosting WINS for WINS lookups. Not only does the service provide the resolution, but it also automatically registers the host in the service.
Right again OCO:
The only reason I mentioned the GC server is because I was under the impression this is a remote site that is accessed through a VPN. In this case, it is recommended that that remote site have a GC that replicates AD/DNS data too so the remote site server is a complete DC server. This information was in addition to fixing the Browser service and I should have separated this out better.
Separating the Browser service from AD and DNS, (as I should have done), the remote site DC should be a master browser. Then, that DC should talk to the PDCe through a WINS connection. This is the only time WINS is really needed for the Browser service.
If all of these computers are on the same site and don't have to go through a VPN connection, over NAT, or need to be routed in some way then allyou have to do is elect Netbios over TCP/IP. The browselist is populated by netbios broadcasts from the client and acknowledged by the server on Netbios port 137 and UDP ports 138 and 139. Using the word "transport" is more of a figure of speach and you are right that DNS is a mirror image of WINS. The free body diagram I drew up for another post illistrates when WINS is really necessary.
My whole point should have simply stated WINS is not needed unless you have to route netbios over a connection. Including the comments on GC and AD / DNS were only to give the remote site some more in-depth thoughts.
Business Accounts
Answer for Membership
by: dineeshPosted on 2008-07-15 at 11:40:10ID: 22009654
hi,
can you check if the computer browser service & server service is running?