Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
How can I find:
1. "The NetBIOS name of the Web server..."
2. "The DNS name of the Web server..."
Thanks,
Pat
Patrick J. Lynch
You can find the host name in a couple ways. Host name is sometimes referred to as the netbios name. Type IPCONFIG /ALL at a command prompt. The Host Name will be displayed. That is the netbios name. There really isn't such a thing as the DNS name but I assume you mean the fully qualified domain name, FQDN. That is the host name plus the primary DNS suffix which is also displayed with the IPCONFIG /ALL command.
0 
Hi again Glen,
Thanks again for the help.
I can connect the client to the server, using the server's ip address.
My client's and server's "Host Name" (aka NetBIOS name) are the same. So I am unable to connect the client to the server, using it. Do I have to change one of the names?
Finally, "Primary Dns Suffix" is blank.
I'd appreciate any help.
Pat
0
the blank suffix is ok, but you need to have each machine use a diffrent name or you will get error "duplicate name exists on network",, blah blah.
and you won't be able to connect via explorer or network places, etc., (which use netbios names).
0
I was thinking that netbios is an older way to lan computers. Not sure if you need it in a modern xp pro 2003 setup at all.
0
Well sort of but not really. The protocol is still used by some application. Don't confuse netbios with netbeui. The netbios name is sort of a throwback to the day when a computer only had the simple name vs. the FQDN. It's not a question of needing it, it's a question of what you want to call it. As I said in my first post, it is also calld the hostname today. Either way, as Rick mentioned they can't be the same. You can only have one computer with the same name. Some applications, older appications still rely on that host name.
If the primary DNS suffix is blank, I'm wondering if you've added this computer to the domain?
0
Glen,
I checked 'System Properties' and the server belongs to 'Workgroup' and does not belong to a 'Domain'.In addition, I tried changing my 'computer name' on my client pc, but I was unable to do so...I gave my administrator account/password but this was not good enough to make the change...
Pat
0
If it's a member of a workgroup then that explains the blank DNS suffix as I expected.
If you add it to the domain, then you will see the FQDN I talked about. If it won't let you change the name that certainly seems like a permission issue. Make sure you are actually logged in as a user with administrative permissions on that computer. Look in Local Users and Group and look in the Administrator group to be sure the account is in that group.
If it's a member of a workgroup you won't need any domain permissions to change the name but once it is a member of the domain you will also need security in the domain to change a computers name since it will also have to change the name of the computer account in the domain.
Good luck.
0
Hi Glen,
I definitely am logging in as the Administrator.There are no 'domains' listed on my System Properties/Computer Name Changes window.
Do I have to create a 'domain' before proceeding? This seems like a formidable task.
It looks like it might be easier to change the computer name on my client pc -- something that I am afraid to do.
Pat
0
I'm a bit confused. The administrator should be able to change the computer name. I would feel better changing it on a client then on a server. What is the exact error you get when trying to change the name on either one?
0
Glen,
I changed the server's computer name...It worked fine...I'll see if I can access the server from my client pc.
I'll let you know.Pat
0
Glen,
I am able to connect from the client to the server using the IP address of the server.
I am using "Microsoft Windows Server 2003 Administrator's Companion" as a reference. It states: "The NetBIOS name of the Web server...".I used the 'Host Name' as the 'NetBios' name and it fails.
Pat
0
How are you trying to connect? Also, if you can connect via IP but not name then it is one of two things I would think. A name resoution issue, which would point to DNS or WINS, or you don't have NetBios enabled. Go to My Network Places, Properties of the LAN Connection, TCP/IP Advanced, and the WINS tab (I think) and look to see that NetBios over TCP/IP is enabled.
If not, enable it. If it is, then we have to look at how you have DNS configured.
0
Glen,
The setting is:
"Default RadioButton is checked"
The following is the text associated with the RadioButton:
"Use NetBIOS setting from the DHCP server. If static address is used or the DHCP server does not provide NetBIOS setting, enable NetBIOS over TCP/IP"Pat
0
Well apparently you need it so I would enable NetBios and then see if you can connect. If it's possible, I'd also reboot that server. Once that is done, then we have to look to name resolution.
From the client, open a command prompt, (Start|Run|CMD - not COMMAND). Type NSLOOKUP and hit Enter. You'll have a > prompt. Type the name of the server and see if it finds a reply or if nslookup even works.
Type EXIT to get out of nslookup.
0
Glen,
The results:After typing NSLOOKUP, the following was displayed:
"Can't find server name for address 65.84.241.167: non-existent domain..."After the MyServer entered at the prompt, the following was displayed:
"...ibsonnline.com can't find MyServer: non-existent domain"Pat
0
rick and Glen put out some good info. I am still trying to learn and like it when they and other offer tips. Sure I lay out some lame answers.
Just wondering again, are we confusing an internet web server with active directory domain?
0
Jefro,
I'm a grunt developer and system tester who is trying to 'crack' ASP.NET, C#, MySQL and MS SQL Server. I got a copy of Win2K3 and I'm trying to make all of this work together.I may indeed be confusing internet web server with active directory domain.
All I want to do is to run my C# programs on my Win2K3 server from my client XP Pro and Win2K client pcs. I can do this, if I use my server's IP address explicitly.
I picked up some reference books on Win2K3 ("[MS] Windows Server 2003 Administrator's Companion", "[MS] Introducing Windows Server 2003" and "Windows Server 2003 for Dummies".
I will make a serious study of Win2K3 using them, but I expect this to take some time.
If you have any suggestions on how to proceed, please send them to me.
Pat
0
I am just trying to figure this all out myself. I meant no disrespect to anyone but rather to complement others. I only meant that it seemed that the answers that rick and Glen refer to active directory I thought. (again untrained opinion) Your original post refered to web server. I just wondered if you had the web edition of 2003.
So that leads me to this question. OK, I am confused. If you are running IIS to test your apps can you use netbios names?
How about making a hosts file on each client that resolves name to ip. Otherwise I would think that you would have to fiddle with setting up dns on the server.
I am just not smart enought to get the connection between dns and netbios across ip.
0
Hi Jefre,
I don't think that you were disrespectful. Many of us are in this thing together...I really appreciate your advice.This the last technical hurdle that I have to overcome.
I'm not using the Win2K3 Web Edition I have the Enterprise Edition...
I'm tired now, I'll start on this tomorrow...
Thanks again,
Pat
0
what your trying to do should work without ad or the internet dns, etc.
you really only need a good ole peer 2 peer workgroup lan to transfer files and such between an internal lan of 2 pc's.
enable the nebios over tcp/ip, make sure the 2 boxes are named differentlly on the same ip subnet, same gateway, etc.
and make some shared folders, put the name of the user your using on each box as a valid user on the other box etc.
your trying to use whats called unc, (Universal Naming Convention), paths, netbuie uses, (ie; windows explorer, network places), the unc path to find, "see" the other box.
without shared folders set up there will be nothing to "see".
0
Hi Rick,
Sorry for the delay in the reply...I'm starting up a new project and I had to attend to it fully for a few days...I'm trying to set up my Win2K3 Server as a Web Server...I can do this if I access the server, using the Win2K3 Server's explicit IP address, but I can't do it using the Server's name...
I'm going to read the manuals and see if they will be of some help...
Thanks again for all your help...it has helped me to pose my problem properly...
Have a good day,
Pat
0
Good news!
I attended the Northern NJ .Net Users Group last night. They conducted a 'birds of the feather' meeting. I presented my problem. One of the members had the same problem and he has given me a solution.As it turns out, my problem is part network and part server management. My environment consists of a Win2K3 server and an XP client - both connect to a Linksys router and the router is connected to my cable modem...
So when I connect to the server from my client, using the server's ip address, I am actually going from the client to the router and then directly to the server (I am not going to the cable modem).
So if I configure the router properly, I will be able to access the server from the client thru the router (not the internet), using the server name.
The last problem to resolve, is to connect to the server from a remote client, using the Internet.
I'll let you know when this is all resolved.
Once again, thanks for your help,
Pat
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
