Re: Exchange on VMWare

Thanks for the response,
When you say "To find resources on other servers outside your vm, I
recommend to use forwarders for sake of simplicity." I dont want to find
resources outside of my vm machines, I just want this member server virtual
machine (which is on the same domain and subnet etc as the virtual DC) to be
able to contact the schema master role on the virtual DC so that exchange
will install. If my understanding of forwarders is correct (which it probably
isnt) then they are not really applicable in this situation. Just to clarify:
I have a virtual DC and Virtual member server on their own 192.168.50.x
subnet and they are the only things on that subnet. They can contact each
other fine with regards to connecting to shares, pinging, joining the domain.
However when i install exchange on the member server it cannot find the
Schema master role which is on the DC. Sorry if im just not understanding
your reply properly

"Al Mulnick" wrote:

"With regards to name resolution, I can ping the servers names from each
other and it returns the correct I.P address and FQDN, is that not
sufficient?"


No, that just tells you that it can find them via *some* dns or worse, a
hosts file or just plain broadcast. That's not an indicator at all until you
try using SRV records. That would be a more indicative test.

Your virtual DC should use itself for name resolution. Only. To find
resources on other servers outside your vm, I recommend to use forwarders
for sake of simplicity. Verify your DC is configured this way and that the
only NS records available are those that you can verify as DNS servers in
your virtual world (ie. the DC).

As for the connectivity - that's great. But your hosts should be using your
virtual dc and your virtual dc only to find records. There are a lot more
records than just A records or ip address that are needed to be successfull
and reliable.

Try it and let us know.

"ChrisW (MCP)" <ChrisWMCP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DA2093EF-D499-420A-82B6-68983D007D73@xxxxxxxxxxxxxxxx
Hi, sorry for the late response.

With regards to name resolution, I can ping the servers names from each
other and it returns the correct I.P address and FQDN, is that not
sufficient?

I have run dcdiag on the dc and it says passed on every test, I ran
netdiag
on the dc and it says passed or skipped on everything except one that says
it
could not find an authorative DNS server for dc.ex.local (the machine im
running it on). I assumed this DC would be an authorative DNS server as it
is
the only DNS server in the domain.

"Al Mulnick" wrote:

Nah. I suspect the same as the others: your name resolution is not setup
properly. Interested to hear otherwise, but I see no reason to think you
have yet setup your network to handle the name resolution such that your
domain controller can be found.

the netdiag and dcdiag outputs asked for should show that if you run it
from
multiple points (both the DC and the server you want to install Exchange
on
should do)


"Robertis Tongbram" <RobertisTongbram@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:46F03D7D-F63C-45C4-8728-A9D8D07E1188@xxxxxxxxxxxxxxxx

Hi,

Mine worked when i installed DC, AD and the Exchange server on new
machine.
What I 'd suggest is to install the Active Directory, and install the
exchange server nicely from scratch in a different machine. Install it
by
running ForestPrep and DomainPrep properly. When it complains that it
cannot
contact the schema master , then I 'd sespect the Domain Controller.

Hope you find this useful:
http://technet.microsoft.com/en-us/library/bb123643.aspx

Robertis






"Jamestechman" wrote:

Run dcdiag/netdiag (part of windows support tools) and post any
errors, it should report who your schema master is and if there are
any issues contacting it.


James Chong (MVP)
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com


On Mar 18, 7:46 am, ChrisW (MCP) <ChrisW...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Yes yes and yes :) On ym vmware network there is just one XP
machine,
one
member server (which im trying to install exchange 2003 on) and one
DC.
I'm
logged in as domain admin, which is in the schema admins etc

"Chris Scharff [MVP - Exchange]" wrote:



On Fri, 16 Mar 2007 09:04:10 -0700, ChrisW (MCP)
<ChrisW...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi All,

I use Vmware a lot and have configured my own network on it with
a
windows
2003 AD. I have checked all prerequisits for exchange 2003 but
whenever I try
and install exchange i get an error saying the schema master
could
not be
contacted. I researched this but found that this supposedly only
happens when
you have had an exchange 5.5 org before...which I havent. I
crteated
a new
set of vmware machines and it worked fine this time. However, I
have
formatted my PC and rebuilt the vmware machines and now get the
same
problem.
I can install exchange on the DC, but obviously i should be able
to
install
it on a member 2003 server. I can ping from each server to the
other
and the
DC definately holds the schema master role. Any suggestions?

Is your Exchange server using the correct DNS server? Is the GC
properly registered in DNS? Are you logged in with an account
which
has appropriate permissions to the schema?

--
Chris Scharff
Messaging Services Architect
MessageOne- Hide quoted text -

- Show quoted text -









.

Relevant Pages

  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: First DC Down .. What Now?
    ... Each site had a single DC and DHCP server. ... We also installed Exchange 2000 Standard. ... install into same directory and MAKE SURE that it ask if you wish to do a Repair install and confirm the repair. ... Can we just, somehow, put in a brand new 2000 server, do a chromo on it, then somehow designate it as the schema master or whatever else it needs to ...
    (microsoft.public.win2000.active_directory)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)