Re: setup unable to determine the dns name of this computer.
- From: "geoca" <geoca@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 29 Jan 2006 12:19:30 -0800
I have managed to disable the extra interfaces on both machines and the
browsing errors have stopped appearing in the event viewer. Have tidied up
the redundant records from WINS and DNS. However I still get the same error
when trying to install exchange. There are no other errors appearing in the
event viewer.
W2K3 has SP1 installed on it. I get a warning when starting the exchange
installation that the version of exchange has a compatibility issue with the
OS version, but the documentation that the warning points me to doesn't
indicate that it should prevent me from performing the installation. Is it
worth me rolling SP1 back? Do you have any other idea what is wrong? I'm
really clutching at straws now.
"Lanwench [MVP - Exchange]" wrote:
>
> "geoca" <geoca@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:0C388E2B-0B30-410A-8A22-1CEA94402FFD@xxxxxxxxxxxxxxxx
> > This is what ipconfig /all says:
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : lbsmaster
> > Primary Dns Suffix . . . . . . . : LBS
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : LBS
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> > Connection
> > Physical Address. . . . . . . . . : 00-0E-0C-4B-42-E2
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.13.10
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.13.254
> > DNS Servers . . . . . . . . . . . : 192.168.13.4
> > Primary WINS Server . . . . . . . : 192.168.13.10
> >
> > Ethernet adapter Local Area Connection 2:
> >
> >
> > Media State . . . . . . . . . . . : Media disconnected
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> > Connection #2
> > Physical Address. . . . . . . . . : 00-0E-0C-4B-42-E3
> >
> >
> > Previously the second interface was plugged in and configured to obtain
> > its
> > ip address which it did, recieving the address 192.168.13.55. I unplugged
> > it
> > so that it wouldn't be able to interfere with anything.
>
> Disable it and reboot.
>
> > The machine has two interfaces on the motherboard. I'm not exactly sure
> > what you mean by "what's bound to each", but each use Client for Microsoft
> > Networks, File and Printer Sharing for Microsoft Networks, and TCP/IP.
>
> DNS and WINS for each would be the issue - but as you don't need two NICs in
> this server, disable one interface and see what happens. You should also
> make sure to a) remove the erroneous/old entry in WINS from when the NIC was
> enabled, and b) try running ipconfig /registerdns to make sure this server
> is registered properly in your local DNS.
>
> > The domain controller on the network is also a W2K3 server with two
> > interfaces on the same subnet. I cannot disable either of those
> > interfaces
> > because there is an application server running on it that requires them
> > both.
>
> Ugh - but that shouldn't be relevant as this is not that server.
>
> > From what I've read the browser service doesn't handle well on multi-homed
> > servers.
>
> Yep - I don't recommend multihomed DCs in general. Check the binding in each
> interface on that server to make sure that only one NIC specifies the WINS
> server. Re DNS on it, can't say as I don't know what your application is
> doing....
>
>
> > I think the domain controller is acting as the master browser on
> > the network and I have been considering stopping it from being this (I
> > think
> > you can do this by changing a certain registry setting).
> > What do you think I should do?
>
> Well, you need something to be the master browser.
> >
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >>
> >>
> >> In news:63C91785-8BF5-45EA-8E1A-9D7FE381E71B@xxxxxxxxxxxxx,
> >> geoca <geoca@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> >> > I've recently installed a new W2K3 member server into a client's
> >> > domain. I'm trying to install exchange 2003 onto this server.
> >> > However when I run the exchange setup executable it gives me the
> >> > following error: "Setup is unable to determine the DNS name of this
> >> > computer. See Microsoft Knowledge Base article 817543 for
> >> > information on how to correct this problem. Then run Setup again."
> >> > I have followed through the intructions of this KB article but it
> >> > doesn't resolve the problem. The network interfaces are correctly
> >> > configured to use internal DNS servers and dcdiag & netdiag show no
> >> > network connection issues. There is a problem appearing in the event
> >> > viewer where the browser service is having some issues. The event
> >> > IDs appearing are 8021 and 8032. Is it possible that these browser
> >> > issues are related to the error message I get when running exchange
> >> > setup?
> >>
> >> Yes.
> >>
> >> What does ipconfig /all tell you on this box?
> >>
> >> You mention network interfaces - meaning, you have more than one? If so,
> >> what's bound to each? (and, why do you have more than one.....?)
> >>
> >>
> >>
>
>
>
.
- References:
- Re: setup unable to determine the dns name of this computer.
- From: Lanwench [MVP - Exchange]
- Re: setup unable to determine the dns name of this computer.
- From: geoca
- Re: setup unable to determine the dns name of this computer.
- From: Lanwench [MVP - Exchange]
- Re: setup unable to determine the dns name of this computer.
- Prev by Date: Re: domain and SMTP
- Next by Date: Exchange 2003 SP2 & OWA SSL Setup Assistance...
- Previous by thread: Re: setup unable to determine the dns name of this computer.
- Next by thread: Need Advise on Exchange 2003 Move
- Index(es):
Relevant Pages
|
