The default netbios domain name vishwanath0 was seleted due to name conflic

hi

i am trying to install a domain controller on windows 2003 by typing dcpromo but when entering netbios name e.g vishwanath.ind.com it is giving me below error message
"The default netbios domain name vishwanath0 was seleted due to name conflict on the network "

 

A computer with the name vishwanath already exists on your network. The netbios name have to be unique.

 

vishwanath.ind.com is not a NetBIOS name. That's a DNS name. The two are different. The NetBIOS name is the single word name. That's the name you gave the server when you set it up.

As NetBIOS names lack the hierachy of DNS you should avoid using the same name for your server (or other computer) as your domain. With DNS you could cope with domain.domain.local, but in NetBIOS the server and domain can't both be called 'domain'.

Also if you are setting up a new domain, I'd recommend you use a .local DNS name space for the internal network, rather than a .com address. So vishwanath.local.

 

hi

First of all My server host name is vishwanath and i have not assigned this name to other computers. I want to set host name same as netbios name. When i am typing vishwanath in netbios name it is asking me to enter name just like this e.g headquaters.microsoft.com, even after entering vishwanath.local.com an error message is displayed which i have mentione d in my previos quote. Previosly when i was doing practicals in my Lab it was working fine

 

Have you set up active directory and DNS, and if so what was the domain name you used there?

 

hi Reggie

When i am entering Full DNS Name as vishwanath.local.com it is giving me error message which i have sent in my previos post but when i entered Full DNS Name as ind.local.com it is taking Netbios name as "ind" ,but here it is not showing that error message. After creating the domain when i checked in MY Computer by right clicking and then click on Computer name it is showing me Computer Name as VISHWANATH and Domain Name as ind.local.com. But instead of ind i want vishwanath.local.com how can i get this name

 

I think you should start from scratch.

I presume that you don't actually own the domain local.com, but rather have been confused over the details of my previous post. When I said a .local domain should be used internally, I meant that .local would replace .com. See this Microsoft article for information on why this is the preferred solution:

http://support.microsoft.com/kb/296250/ko

So first thing is to choose a suitable internal domain name. I'd suggest you use:

domain.local

However, if you have an organisation or company name, you could replace 'domain' with that name (for example, if your company is called 'Widgets Ltd' you could use widget.local as your internal domain name.

Then follow this guide to set up DNS on the server:

http://support.microsoft.com/kb/814591

At step 5c, enter domain.local or your preferred domain name as the zone name.

That will set up the server. Records for your server will automatically be created.

To set up client PCs, the best option is to use DHCP. Have a look at this guide that explains how to do that:

http://support.microsoft.com/kb/816592/en-us

However, if you want to use static IPs, then you'll have to add A records for each PC. To do this:

• open the DNS manager on the server
• right click on the "domain.local" icon in "Forward Lookup Zones" and select "New Host (A).. ".
• In the dialogue that appears, enter the computer name in the Name box (for your example this will be vishwanath). As you enter the name, the full DNS name will appear in the box below (for this example, vishwanath.domain.local).
• In the IP address fields, enter the IP address of the computer (again, in your example this would be the IP address of the computer VISHWANATH).
• Click on Add host

That will create a A record for the PC.

You can test this by using nslookup at the server. It should resolve the DNS name to an IP address. So:

nslookup vishwanath.domain.local

Should resolve to the IP address of the PC vishwanath.

For the PCs with static IPs to work properly, they will have to have TCP/IP set so that DNS points at the IP address of the server, and the domain name will be domain.local

Again nslookup can be used to check the DNS settings on the PC. You should get the same results as you get at the server.

 

Dear Reggie

Thanks for your reply, actually i am doing some Practicals on my pc. I have a piv system with 4GB of RAM AND I HAVE INSTALLED WINDOWS 2003 STANDARD EDITION and also i have installed virtual os (2 windows xp and windows server 2003 std edition ) .

 

Then I suggest you strip services like DNS and DHCP out of the host system and run it like a desktop PC. Install and play with these services on the visual installation of 2003. Use a generic domain name like domain.local and use other virtual instances as test client PCs.

The great thing about using a virtual environment, is that you can create and tear down systems very quickly and easily. I'd recommend you take the time to create a clean install of a virtual 2003 instance and then save that as a template. Then copy that virtual machine and play with the copy. Once you've got the hang of it, or if you want to start over, simply delete the copy and create another to play with and improve on.

 

hi reggie

I am trying to create a group policy for let us say n number of users on windows 2003 domain controller through which i can disable usb storage device but. when i checked on client system (windows xp) the policy is not reflecting to the client system.


The Howto!
If we combine Mark Heitbrink's approach with the one outlined in knowledge base article 823732, we get a more reliable solution. Firstly, we need to prevent USBSTOR from being installed unless the currently logged on user is allowed to use USB storage. We do that by restricting access to USBSTOR.INF and USBSTORE.PNF in a GPO such that PNP can't automatically install the driver. This is possible because when PNP installs a driver, the installation is performed using the priviledges of the currently logged on user. Secondly, we need to make sure that USBSTOR is not started when a USB storage device is plugged in. For that we use Mark's ADM template. The only minor drawback of my solution is that users with access to USB storage need to manually start USBSTOR before connecting USB storage devices.

In Active Directory Users and Computers, open an existing GPO or create a new one and open it. Use the security settings of that GPO to specify which computers it affects.
In that GPO, go to Computer Configuration "“ Windows Settings "“ Security Settings "“ File System and create a new entry (right-click File System and select Add File). Specify the location of USBSTOR.INF (usually SystemRoot%\Inf\USBSTOR.INF)
Change the security settings of the new entry. The security settings that you specify here will be enforced on the USBSTOR.INF of every computer to which the GPO is applied. This process is not additive, which means that the previous security settings of USBSTOR.INF will be overwritten by the ones given in the GPO. It is therefore recommended to grant full control to SYSTEM and local administrators. But unlike in the default security settings of USBSTOR.INF, you should not grant any priviledges to Everybody. You do not need to explicitly deny access "“ just omit an entry for Everybody. Optionally, you can grant read access to a certain group. Members of this group will be able to use USB storage.
Repeat the above two steps for USBSTOR.PNF.
Download USBSTOR.ADM.
Back in the GPO, right-click Administrative Templates under Computer Configuration and select Add/Remove Templates. Click Add and browse to the location of USBSTOR.ADM. Close the dialog.
You should now have an additional entry called Services and Drivers in Administrative Templates. Click on it. If it is empty, select View from the menu and uncheck Show Policies Only. Click back on Services and Drivers in Administrative Templates. It should now show the USB Storage policy. Double click it, select Enabled and pick Disabled from the Startup Type drop down. Again, the policy must be enabled wheras Startup Type must be Disabled.
Close the dialog as well as the GPO and boot/reboot one of your workstations. Make sure no USB strorage device is connected to that computer. Log on with administrative privileges and check the permissions of USBSTOR.INF and USBSTOR.PNF. Check the value of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor\Start. It should be 4. It is also ok if the UsbStor key doesn't exist at all.
On the same workstation, log off and back on as a user that should not have access to USB storage. Connect a USB memory stick or a similar device. Nothing should happen. Remove the memory stick.
Log on as a user that should have access to USB storage and execute net start usbstor in a command shell or at Start "“ Run before connecting the memory stick. The memory stick should initialized and mapped to a drive letter. If USBSTOR fails to start, it's probably because this is the first time a memory stick is plugged into the workstation in which case USBSTOR is not yet installed. Nevertheless, the memory stick should be initialized and mapped correctly but you need to reboot in order to reapply the administrative template such that USBSTOR is disabled again. Alternatively, you can disable it manually by downloading and double clicking USBSTOR.REG as well as executing net stop usbstor.
Instruct the users with access to USB storage that they need to execute net start usbstor before they can connect a USB storage device.