I have a single server with SBS 2000 installed and running for 2 days and some problems are appearing. Small network (12 machines + SBS server. Mostly problem seems to be that system name (SBS1) is not always resolved to inside address (10.0.0.2). Sometimes it is but mostly not. Sometimes system name + domain name will resolve (SBS1.office.com)and sometimes not. All of this trouble is on inside LAN. Outside LAN (192.168.1.2) works fine. This machine had W2K server installed after a hardware crash ruined a good, working, NT 4.0 server. I seem to recall that both 10.0.0.1 and 10.0.0.2 were assigned on the NT 4.0 server but can not recall where. Incidentally, this was a fresh install of W2K server not an upgrade. If I could have upgraded I'm sure this would not be a problem. If you are familiar with SBS2K, you will know that this includes DNS, DHCP, Exchange, ISA, all running on the same machine. Any assist would be appreciated. I have plenty of reading material but it is full of what-to-do info on installing and troubleshooting, not what-should-not-have-been-done info.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Name resolution troubles
- Thread starter rxpete
- Start date
ashleym
MIS
- Mar 30, 2001
- 375
What happens when you run NSLOOKUP on a machine on the LAN other then the server? Can it resolve?
Can you ping by hostname on the LAN?
Do people sometimes lose their ability to surf the internet?
Is there anything in your event logs that may indicate what the problem is?
Ashleym
Can you ping by hostname on the LAN?
Do people sometimes lose their ability to surf the internet?
Is there anything in your event logs that may indicate what the problem is?
Ashleym
Quick name resolution checklist:
Make sure all your machines are pointing to the correct DNS server IP.
Make sure all your machines are pointing to the correct WINS server IP (if applicable).
Do you have a hosts or lmhosts file interfering?
Are you using DHCP? Is it handing out the correct domain name?
Do you have any different DNS suffixes configured on the clients?
In case you're unfamiliar with name resolution in Win2k, Windows 2000 uses DNS like NT 4 used WINS. Everything important is resolved using DNS. If you have no legacy clients and you're running WINS, I'd suggest getting rid of it. Marc Creviere
Make sure all your machines are pointing to the correct DNS server IP.
Make sure all your machines are pointing to the correct WINS server IP (if applicable).
Do you have a hosts or lmhosts file interfering?
Are you using DHCP? Is it handing out the correct domain name?
Do you have any different DNS suffixes configured on the clients?
In case you're unfamiliar with name resolution in Win2k, Windows 2000 uses DNS like NT 4 used WINS. Everything important is resolved using DNS. If you have no legacy clients and you're running WINS, I'd suggest getting rid of it. Marc Creviere
- Thread starter
- #4
People not only lose ability to surf the internet, they even lose connection to Exchange Server ("No Exchange Server was available"
. In order to get the connection back I had to type in 10.0.0.2 for ExchSvr name instead of SBS1. Even then it can take five or ten minutes for Outlook to open their mailbox (esp. Win 98 clients?)
Anyway, sometimes "nslookup SBS1" will respond with "SBS1.office.com" and sometimes with error. Ping does the same thing. Ping always responds if I ping the IP directly though. One thing though...when we were running the NT 4.0 server, the domain name on the client network ID was always displayed as OFFICE. Now with W2K it shows up as office.com. Any significance in that? The W2K Pro logon screen still shows OFFICE as the domain and all clients (W2K Pro and Win 98)logon. The Win 98 clients have troubles but I think it's just related to broken trusts (since they couldn't be migrated to the W2K server)
I am using DHCP but I thought DHCP got the domain name from DNS. I don't know what you mean by using different DNS suffixes on the clients. They're all set to obtain DNS server address automatically. The only suffix on the system is office.com. I tried using lmhosts to fix the problem on a couple clients but it didn't do anything that I could tell. There's only one line in the host file I tried so there couldn't be much interference coming from that (lmhost: 10.0.0.2 SBS1)
Thank you both for your thoughtful analysis and assistance.
. In order to get the connection back I had to type in 10.0.0.2 for ExchSvr name instead of SBS1. Even then it can take five or ten minutes for Outlook to open their mailbox (esp. Win 98 clients?)Anyway, sometimes "nslookup SBS1" will respond with "SBS1.office.com" and sometimes with error. Ping does the same thing. Ping always responds if I ping the IP directly though. One thing though...when we were running the NT 4.0 server, the domain name on the client network ID was always displayed as OFFICE. Now with W2K it shows up as office.com. Any significance in that? The W2K Pro logon screen still shows OFFICE as the domain and all clients (W2K Pro and Win 98)logon. The Win 98 clients have troubles but I think it's just related to broken trusts (since they couldn't be migrated to the W2K server)
I am using DHCP but I thought DHCP got the domain name from DNS. I don't know what you mean by using different DNS suffixes on the clients. They're all set to obtain DNS server address automatically. The only suffix on the system is office.com. I tried using lmhosts to fix the problem on a couple clients but it didn't do anything that I could tell. There's only one line in the host file I tried so there couldn't be much interference coming from that (lmhost: 10.0.0.2 SBS1)
Thank you both for your thoughtful analysis and assistance.
- Thread starter
- #5
One thing I just noticed because of a warning in the DNS event list, is that in the DNS console, the server is shown with the name SBS1 and in the DHCP console it is shown as sbs1.office.com. Is this normal? The warning in DNS events is: "The DNS server machine currently has no DNS domain name. Its DNS name is a single label hostname with no domain (example: "host" rather than "host.microsoft.com"."
The solution it gives for correcting it is to just change the name on the system propoerties Network ID tab, but that is greyed out with a message that says "...cannot be changed because the computer is a domain controller." Full computer name is shown as sbs1.office.com and domain shown as office.com.
."The solution it gives for correcting it is to just change the name on the system propoerties Network ID tab, but that is greyed out with a message that says "...cannot be changed because the computer is a domain controller." Full computer name is shown as sbs1.office.com and domain shown as office.com.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question