| Author |
Message |
brtnharv
Guest
|
 Posted:
Fri Jan 14, 2005 11:17 pm Post subject:
Installed SBS2003 into existing 2003 domain, now issues with |
|
|
Hello there, I recently installed SBS 2003 into our existing domain,
company.local, which has 3 - 2003 standard DC's. It joined the domain fine,
but during installation of Exchange something failed. The only way could get
exchange to come back was to use the /disasterrecovery command on setup. I
then uninstalled and reinstalled it to a new disk on the server. Exchange
works fine now. The next issue was that one of my servers, server8, could
not replicate with other DC's on the domain. I dcpromo'ed server8 back to a
stand alone because it was a new server that was not running anything as of
then. That fixed the replication problem. Now though, I am not seeing my 2
other DC's, server1 and server2, under the company.local -> _msdcs directory.
I am only seeing one server, in this case, server7 which is the SBS 2003
server with exchange. My understanding is that all DC's should show up in
the _msdcs directory in DNS with a Alias (CNAME) entry with its FQDN and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure. Event
viewers are not showing any errors either. I believe the mistake was
installing SBS into an existing domain and not a new domain. Sorry for the
long post, it's been a long 2 days. Thanks. Matt. |
|
| Back to top |
|
 |
Phillip Windell
Guest
|
| Posted:
Sat Jan 15, 2005 1:26 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
SBS can *not* join other Domains. It also can not have a "Trust" with other
Domains. There can only be one Domain and SBS is *it.*
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
| Quote: | Hello there, I recently installed SBS 2003 into our existing domain,
company.local, which has 3 - 2003 standard DC's. It joined the domain
fine,
but during installation of Exchange something failed. The only way could
get
exchange to come back was to use the /disasterrecovery command on setup.
I
then uninstalled and reinstalled it to a new disk on the server. Exchange
works fine now. The next issue was that one of my servers, server8, could
not replicate with other DC's on the domain. I dcpromo'ed server8 back to
a
stand alone because it was a new server that was not running anything as
of
then. That fixed the replication problem. Now though, I am not seeing my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS 2003
server with exchange. My understanding is that all DC's should show up in
the _msdcs directory in DNS with a Alias (CNAME) entry with its FQDN and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure. Event
viewers are not showing any errors either. I believe the mistake was
installing SBS into an existing domain and not a new domain. Sorry for
the
long post, it's been a long 2 days. Thanks. Matt. |
|
|
| Back to top |
|
|
SuperGumby [SBS MVP]
Guest
|
| Posted:
Sat Jan 15, 2005 2:47 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
SBS _CAN_ join an existing AD. Please do not mislead people.
"Phillip Windell" <@.> wrote in message
news:%23EH$$7m%23EHA.3328@TK2MSFTNGP10.phx.gbl...
| Quote: | SBS can *not* join other Domains. It also can not have a "Trust" with
other
Domains. There can only be one Domain and SBS is *it.*
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing domain,
company.local, which has 3 - 2003 standard DC's. It joined the domain
fine,
but during installation of Exchange something failed. The only way could
get
exchange to come back was to use the /disasterrecovery command on setup.
I
then uninstalled and reinstalled it to a new disk on the server.
Exchange
works fine now. The next issue was that one of my servers, server8,
could
not replicate with other DC's on the domain. I dcpromo'ed server8 back
to
a
stand alone because it was a new server that was not running anything as
of
then. That fixed the replication problem. Now though, I am not seeing my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS 2003
server with exchange. My understanding is that all DC's should show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its FQDN and
a
Hex? entry. The network "seems" to be ok but I'm not 100% sure. Event
viewers are not showing any errors either. I believe the mistake was
installing SBS into an existing domain and not a new domain. Sorry for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
SuperGumby [SBS MVP]
Guest
|
| Posted:
Sat Jan 15, 2005 2:57 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the process you
describe suggests to me that the SBS (and therefore Exchange) was installed
with the same name as a previously existing system which may not have been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all traces of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation is
complete but before the SBS installation wizard starts asking questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles moved to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
| Quote: | Hello there, I recently installed SBS 2003 into our existing domain,
company.local, which has 3 - 2003 standard DC's. It joined the domain
fine,
but during installation of Exchange something failed. The only way could
get
exchange to come back was to use the /disasterrecovery command on setup.
I
then uninstalled and reinstalled it to a new disk on the server. Exchange
works fine now. The next issue was that one of my servers, server8, could
not replicate with other DC's on the domain. I dcpromo'ed server8 back to
a
stand alone because it was a new server that was not running anything as
of
then. That fixed the replication problem. Now though, I am not seeing my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS 2003
server with exchange. My understanding is that all DC's should show up in
the _msdcs directory in DNS with a Alias (CNAME) entry with its FQDN and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure. Event
viewers are not showing any errors either. I believe the mistake was
installing SBS into an existing domain and not a new domain. Sorry for
the
long post, it's been a long 2 days. Thanks. Matt. |
|
|
| Back to top |
|
|
Phillip Windell
Guest
|
| Posted:
Sat Jan 15, 2005 3:01 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:%23wtFMpn%23EHA.1392@tk2msftngp13.phx.gbl...
| Quote: | SBS _CAN_ join an existing AD. Please do not mislead people.
|
The last time I asked that question of the SBS MVPs,...because I didn't know
myself,...I was told just what I have stated in that post. So someone is
going to have to quit misleading me. I was told the only thing you *can* do
is have multiple DCs as long as it is all one Domain and the SBS box is in
the "PDC role".
I also heard that there are some things that can be done via some
"convoluted tactics" but that they weren't MS "supported". I don't care
about those and only care about what is "supported",...that in itself is
enough to worry about.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com |
|
| Back to top |
|
|
SuperGumby [SBS MVP]
Guest
|
| Posted:
Sat Jan 15, 2005 3:23 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
I think the problem may be one of interpretation rather than anything major.
Can a fully configured SBS (AD installation complete) join another AD? NO.
Can SBS media be used to upgrade the existing holder of the FSMO roles from
Win2k/2k3 to SBS? YES
Does MS support the 'promotion' of your existing FSMO role holder to SBS?
YES
The process is not convoluted. There is complexity involved if the existing
owner of the FSMO roles is not available (if the owner had crashed, say) but
this is a standard AD FSMO role acquisition, there is nothing specific to
SBS involved.
The previous existence of an Exchange server is similar. If you tried to
install Exchange into any AD as the same named Exchange as a missing server
you would also hit problems. Nothing SBS specific here either.
"Phillip Windell" <@.> wrote in message
news:uDMuKxn%23EHA.1524@TK2MSFTNGP09.phx.gbl...
| Quote: | "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:%23wtFMpn%23EHA.1392@tk2msftngp13.phx.gbl...
SBS _CAN_ join an existing AD. Please do not mislead people.
The last time I asked that question of the SBS MVPs,...because I didn't
know
myself,...I was told just what I have stated in that post. So someone is
going to have to quit misleading me. I was told the only thing you *can*
do
is have multiple DCs as long as it is all one Domain and the SBS box is in
the "PDC role".
I also heard that there are some things that can be done via some
"convoluted tactics" but that they weren't MS "supported". I don't care
about those and only care about what is "supported",...that in itself is
enough to worry about.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
|
|
|
| Back to top |
|
|
Phillip Windell
Guest
|
| Posted:
Sat Jan 15, 2005 3:39 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:OAzAL9n%23EHA.2876@TK2MSFTNGP12.phx.gbl...
| Quote: | I think the problem may be one of interpretation rather than anything
major. |
I would agree with that. I take my "work" in these groups seriously and am
certainly not going around "misleading" people, although I may not always be
correct.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com |
|
| Back to top |
|
|
brtnharv
Guest
|
| Posted:
Sat Jan 15, 2005 5:51 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
Thanks for your replies. I'm still a bit confused though. I dcpromo'ed the
SBS server to an existing 2 - DC 2003 enviroment. I then transfered all 5
FSMO roles to the SBS server. The global catalog still remained on the
server1 (one of the original 2 DC's). Everything was working fine as of then.
Things started to go south when the installation of Exchange on the SBS 2003
server occured. The install of exchange was "successful", but none of its
services would load. Like I said I finally got exchange uninstalled and
reinstalled. This is when I started to have issues, event viewers were going
crazy, DNS wasn't working right and replication was not happening. It looked
as the my other server (server8) that i talked about in my original post
never was part of the replication process. It almost seemed that there were
2 different schemas in the same domain. I therefore got rid of the server8
by taking it back to a standalone. I now currently have server1 and server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange (which is
working fine both internal and external). AD seems fine also, but DNS is not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
| Quote: | please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the process you
describe suggests to me that the SBS (and therefore Exchange) was installed
with the same name as a previously existing system which may not have been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all traces of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation is
complete but before the SBS installation wizard starts asking questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles moved to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing domain,
company.local, which has 3 - 2003 standard DC's. It joined the domain
fine,
but during installation of Exchange something failed. The only way could
get
exchange to come back was to use the /disasterrecovery command on setup.
I
then uninstalled and reinstalled it to a new disk on the server. Exchange
works fine now. The next issue was that one of my servers, server8, could
not replicate with other DC's on the domain. I dcpromo'ed server8 back to
a
stand alone because it was a new server that was not running anything as
of
then. That fixed the replication problem. Now though, I am not seeing my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS 2003
server with exchange. My understanding is that all DC's should show up in
the _msdcs directory in DNS with a Alias (CNAME) entry with its FQDN and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure. Event
viewers are not showing any errors either. I believe the mistake was
installing SBS into an existing domain and not a new domain. Sorry for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
SuperGumby [SBS MVP]
Guest
|
| Posted:
Sat Jan 15, 2005 6:01 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
add the GC role to SBS and post the full output of 'ipconfig /all >
C:\ipconfig.txt' from all servers (and one WS may be handy).
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:BB5EA59F-D505-488F-ABAE-53A8252A648B@microsoft.com...
| Quote: | Thanks for your replies. I'm still a bit confused though. I dcpromo'ed
the
SBS server to an existing 2 - DC 2003 enviroment. I then transfered all 5
FSMO roles to the SBS server. The global catalog still remained on the
server1 (one of the original 2 DC's). Everything was working fine as of
then.
Things started to go south when the installation of Exchange on the SBS
2003
server occured. The install of exchange was "successful", but none of its
services would load. Like I said I finally got exchange uninstalled and
reinstalled. This is when I started to have issues, event viewers were
going
crazy, DNS wasn't working right and replication was not happening. It
looked
as the my other server (server8) that i talked about in my original post
never was part of the replication process. It almost seemed that there
were
2 different schemas in the same domain. I therefore got rid of the
server8
by taking it back to a standalone. I now currently have server1 and
server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange (which is
working fine both internal and external). AD seems fine also, but DNS is
not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the process
you
describe suggests to me that the SBS (and therefore Exchange) was
installed
with the same name as a previously existing system which may not have
been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously
existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all traces
of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation is
complete but before the SBS installation wizard starts asking questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles moved
to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing domain,
company.local, which has 3 - 2003 standard DC's. It joined the domain
fine,
but during installation of Exchange something failed. The only way
could
get
exchange to come back was to use the /disasterrecovery command on
setup.
I
then uninstalled and reinstalled it to a new disk on the server.
Exchange
works fine now. The next issue was that one of my servers, server8,
could
not replicate with other DC's on the domain. I dcpromo'ed server8 back
to
a
stand alone because it was a new server that was not running anything
as
of
then. That fixed the replication problem. Now though, I am not seeing
my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS
2003
server with exchange. My understanding is that all DC's should show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its FQDN
and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure. Event
viewers are not showing any errors either. I believe the mistake was
installing SBS into an existing domain and not a new domain. Sorry for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
brtnharv
Guest
|
| Posted:
Sat Jan 15, 2005 6:39 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
SBS 2003
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn7
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
Physical Address. . . . . . . . . : 00-0E-0C-65-B4-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.246
DNS Servers . . . . . . . . . . . : 10.10.10.100
10.10.10.101
Primary WINS Server . . . . . . . : 10.10.10.105
Secondary WINS Server . . . . . . : 10.10.10.100
2003 standard (server1)
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn1
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0C-F1-7D-2B-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.20
DNS Servers . . . . . . . . . . . : 10.10.10.100
Primary WINS Server . . . . . . . : 10.10.10.100
Thanks again.
"SuperGumby [SBS MVP]" wrote:
| Quote: | add the GC role to SBS and post the full output of 'ipconfig /all
C:\ipconfig.txt' from all servers (and one WS may be handy).
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:BB5EA59F-D505-488F-ABAE-53A8252A648B@microsoft.com...
Thanks for your replies. I'm still a bit confused though. I dcpromo'ed
the
SBS server to an existing 2 - DC 2003 enviroment. I then transfered all 5
FSMO roles to the SBS server. The global catalog still remained on the
server1 (one of the original 2 DC's). Everything was working fine as of
then.
Things started to go south when the installation of Exchange on the SBS
2003
server occured. The install of exchange was "successful", but none of its
services would load. Like I said I finally got exchange uninstalled and
reinstalled. This is when I started to have issues, event viewers were
going
crazy, DNS wasn't working right and replication was not happening. It
looked
as the my other server (server8) that i talked about in my original post
never was part of the replication process. It almost seemed that there
were
2 different schemas in the same domain. I therefore got rid of the
server8
by taking it back to a standalone. I now currently have server1 and
server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange (which is
working fine both internal and external). AD seems fine also, but DNS is
not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the process
you
describe suggests to me that the SBS (and therefore Exchange) was
installed
with the same name as a previously existing system which may not have
been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously
existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all traces
of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation is
complete but before the SBS installation wizard starts asking questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles moved
to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing domain,
company.local, which has 3 - 2003 standard DC's. It joined the domain
fine,
but during installation of Exchange something failed. The only way
could
get
exchange to come back was to use the /disasterrecovery command on
setup.
I
then uninstalled and reinstalled it to a new disk on the server.
Exchange
works fine now. The next issue was that one of my servers, server8,
could
not replicate with other DC's on the domain. I dcpromo'ed server8 back
to
a
stand alone because it was a new server that was not running anything
as
of
then. That fixed the replication problem. Now though, I am not seeing
my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS
2003
server with exchange. My understanding is that all DC's should show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its FQDN
and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure. Event
viewers are not showing any errors either. I believe the mistake was
installing SBS into an existing domain and not a new domain. Sorry for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
Jeff Middleton [SBS-MVP]
Guest
|
| Posted:
Sat Jan 15, 2005 11:12 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
it would probably take a little bit of looking, but I would be willing to
look at your server to confirm the current status regarding the upgrade you
are doing.
The Swing It!! Kit offered at SBSmigration.com does explain how to
accomplish what you originallly described. I believe it would give you an
exit strategy from this situation as well.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:CF21DC9E-E40D-499D-B575-868A513D6346@microsoft.com...
| Quote: | SBS 2003
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn7
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
Physical Address. . . . . . . . . : 00-0E-0C-65-B4-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.246
DNS Servers . . . . . . . . . . . : 10.10.10.100
10.10.10.101
Primary WINS Server . . . . . . . : 10.10.10.105
Secondary WINS Server . . . . . . : 10.10.10.100
2003 standard (server1)
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn1
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-0C-F1-7D-2B-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.20
DNS Servers . . . . . . . . . . . : 10.10.10.100
Primary WINS Server . . . . . . . : 10.10.10.100
Thanks again.
"SuperGumby [SBS MVP]" wrote:
add the GC role to SBS and post the full output of 'ipconfig /all
C:\ipconfig.txt' from all servers (and one WS may be handy).
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:BB5EA59F-D505-488F-ABAE-53A8252A648B@microsoft.com...
Thanks for your replies. I'm still a bit confused though. I
dcpromo'ed
the
SBS server to an existing 2 - DC 2003 enviroment. I then transfered
all 5
FSMO roles to the SBS server. The global catalog still remained on
the
server1 (one of the original 2 DC's). Everything was working fine as
of
then.
Things started to go south when the installation of Exchange on the
SBS
2003
server occured. The install of exchange was "successful", but none of
its
services would load. Like I said I finally got exchange uninstalled
and
reinstalled. This is when I started to have issues, event viewers
were
going
crazy, DNS wasn't working right and replication was not happening. It
looked
as the my other server (server8) that i talked about in my original
post
never was part of the replication process. It almost seemed that
there
were
2 different schemas in the same domain. I therefore got rid of the
server8
by taking it back to a standalone. I now currently have server1 and
server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange
(which is
working fine both internal and external). AD seems fine also, but DNS
is
not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the
process
you
describe suggests to me that the SBS (and therefore Exchange) was
installed
with the same name as a previously existing system which may not have
been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously
existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all
traces
of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation
is
complete but before the SBS installation wizard starts asking
questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles
moved
to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing
domain,
company.local, which has 3 - 2003 standard DC's. It joined the
domain
fine,
but during installation of Exchange something failed. The only way
could
get
exchange to come back was to use the /disasterrecovery command on
setup.
I
then uninstalled and reinstalled it to a new disk on the server.
Exchange
works fine now. The next issue was that one of my servers,
server8,
could
not replicate with other DC's on the domain. I dcpromo'ed server8
back
to
a
stand alone because it was a new server that was not running
anything
as
of
then. That fixed the replication problem. Now though, I am not
seeing
my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS
2003
server with exchange. My understanding is that all DC's should
show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its
FQDN
and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure.
Event
viewers are not showing any errors either. I believe the mistake
was
installing SBS into an existing domain and not a new domain. Sorry
for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
Marina Roos [SBS-MVP]
Guest
|
| Posted:
Sat Jan 15, 2005 8:20 pm Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
Hi,
DNS on the servernic should only point to the server IP. Why are both
servers having a different Gateway?
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"brtnharv" <brtnharv@discussions.microsoft.com> schreef in bericht
news:CF21DC9E-E40D-499D-B575-868A513D6346@microsoft.com...
| Quote: | SBS 2003
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn7
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
Physical Address. . . . . . . . . : 00-0E-0C-65-B4-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.246
DNS Servers . . . . . . . . . . . : 10.10.10.100
10.10.10.101
Primary WINS Server . . . . . . . : 10.10.10.105
Secondary WINS Server . . . . . . : 10.10.10.100
2003 standard (server1)
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn1
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-0C-F1-7D-2B-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.20
DNS Servers . . . . . . . . . . . : 10.10.10.100
Primary WINS Server . . . . . . . : 10.10.10.100
Thanks again.
"SuperGumby [SBS MVP]" wrote:
add the GC role to SBS and post the full output of 'ipconfig /all
C:\ipconfig.txt' from all servers (and one WS may be handy).
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:BB5EA59F-D505-488F-ABAE-53A8252A648B@microsoft.com...
Thanks for your replies. I'm still a bit confused though. I
dcpromo'ed
the
SBS server to an existing 2 - DC 2003 enviroment. I then transfered
all 5
FSMO roles to the SBS server. The global catalog still remained on
the
server1 (one of the original 2 DC's). Everything was working fine as
of
then.
Things started to go south when the installation of Exchange on the
SBS
2003
server occured. The install of exchange was "successful", but none of
its
services would load. Like I said I finally got exchange uninstalled
and
reinstalled. This is when I started to have issues, event viewers
were
going
crazy, DNS wasn't working right and replication was not happening. It
looked
as the my other server (server8) that i talked about in my original
post
never was part of the replication process. It almost seemed that
there
were
2 different schemas in the same domain. I therefore got rid of the
server8
by taking it back to a standalone. I now currently have server1 and
server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange
(which is
working fine both internal and external). AD seems fine also, but DNS
is
not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the
process
you
describe suggests to me that the SBS (and therefore Exchange) was
installed
with the same name as a previously existing system which may not have
been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously
existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all
traces
of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation
is
complete but before the SBS installation wizard starts asking
questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles
moved
to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing
domain,
company.local, which has 3 - 2003 standard DC's. It joined the
domain
fine,
but during installation of Exchange something failed. The only way
could
get
exchange to come back was to use the /disasterrecovery command on
setup.
I
then uninstalled and reinstalled it to a new disk on the server.
Exchange
works fine now. The next issue was that one of my servers,
server8,
could
not replicate with other DC's on the domain. I dcpromo'ed server8
back
to
a
stand alone because it was a new server that was not running
anything
as
of
then. That fixed the replication problem. Now though, I am not
seeing
my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS
2003
server with exchange. My understanding is that all DC's should
show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its
FQDN
and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure.
Event
viewers are not showing any errors either. I believe the mistake
was
installing SBS into an existing domain and not a new domain. Sorry
for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
brtnharv
Guest
|
| Posted:
Sat Jan 15, 2005 10:15 pm Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
Thanks. We have a DSL router with 8-ports and we get 30 static IP's from our
ISP that just passes through the static addresses. I have another router set
up behind the DSL router with a public address to forward the necessary ports
to exchange. Everything is on the same VLAN. So we have 2 routers - 1 for
our production network behind our Lucent firewall and another that forwards
ports to exchange includeing webmail, terminal services, etc. So exchange
points to .246 and the 2003 server standard point to .20...is this the wrong
was to do this?
"Marina Roos [SBS-MVP]" wrote:
| Quote: | Hi,
DNS on the servernic should only point to the server IP. Why are both
servers having a different Gateway?
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"brtnharv" <brtnharv@discussions.microsoft.com> schreef in bericht
news:CF21DC9E-E40D-499D-B575-868A513D6346@microsoft.com...
SBS 2003
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn7
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
Physical Address. . . . . . . . . : 00-0E-0C-65-B4-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.246
DNS Servers . . . . . . . . . . . : 10.10.10.100
10.10.10.101
Primary WINS Server . . . . . . . : 10.10.10.105
Secondary WINS Server . . . . . . : 10.10.10.100
2003 standard (server1)
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn1
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-0C-F1-7D-2B-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.20
DNS Servers . . . . . . . . . . . : 10.10.10.100
Primary WINS Server . . . . . . . : 10.10.10.100
Thanks again.
"SuperGumby [SBS MVP]" wrote:
add the GC role to SBS and post the full output of 'ipconfig /all
C:\ipconfig.txt' from all servers (and one WS may be handy).
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:BB5EA59F-D505-488F-ABAE-53A8252A648B@microsoft.com...
Thanks for your replies. I'm still a bit confused though. I
dcpromo'ed
the
SBS server to an existing 2 - DC 2003 enviroment. I then transfered
all 5
FSMO roles to the SBS server. The global catalog still remained on
the
server1 (one of the original 2 DC's). Everything was working fine as
of
then.
Things started to go south when the installation of Exchange on the
SBS
2003
server occured. The install of exchange was "successful", but none of
its
services would load. Like I said I finally got exchange uninstalled
and
reinstalled. This is when I started to have issues, event viewers
were
going
crazy, DNS wasn't working right and replication was not happening. It
looked
as the my other server (server8) that i talked about in my original
post
never was part of the replication process. It almost seemed that
there
were
2 different schemas in the same domain. I therefore got rid of the
server8
by taking it back to a standalone. I now currently have server1 and
server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange
(which is
working fine both internal and external). AD seems fine also, but DNS
is
not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the
process
you
describe suggests to me that the SBS (and therefore Exchange) was
installed
with the same name as a previously existing system which may not have
been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously
existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all
traces
of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation
is
complete but before the SBS installation wizard starts asking
questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles
moved
to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing
domain,
company.local, which has 3 - 2003 standard DC's. It joined the
domain
fine,
but during installation of Exchange something failed. The only way
could
get
exchange to come back was to use the /disasterrecovery command on
setup.
I
then uninstalled and reinstalled it to a new disk on the server.
Exchange
works fine now. The next issue was that one of my servers,
server8,
could
not replicate with other DC's on the domain. I dcpromo'ed server8
back
to
a
stand alone because it was a new server that was not running
anything
as
of
then. That fixed the replication problem. Now though, I am not
seeing
my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS
2003
server with exchange. My understanding is that all DC's should
show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its
FQDN
and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure.
Event
viewers are not showing any errors either. I believe the mistake
was
installing SBS into an existing domain and not a new domain. Sorry
for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
Jeff Middleton [SBS-MVP]
Guest
|
| Posted:
Sat Jan 15, 2005 10:33 pm Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
You can not have default gateways on both interfaces. You also have two
interfaces on the same subnet, that's not right either except in load
balancing.
The concept of default gateway is "if I'm a packet in this box, I check all
the static routes to see where I should go, and if I can't find a specific
route, I go to the default gateway because that leads to 'all unknown
locations'."
Having two default gateways suggests that there's more than one way to go to
get to everywhere, therefore you have failures because sometimes that
packets go north, sometimes they go south.
You would normally solve this with a different technical approach. I think
if I understand what you are trying to do, you should simply do both a port
and IP translation from the public to the private and send all the traffic
to the one interface on the server facing the web.
I hesitate to say this, but it does appear that you are making this a lot
more complicated that necessary, and I honestly don't see a benefit to the
strategy, but I'm only glancing at this one post with that thought.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:0E26C797-21BA-4590-8866-D55E5D2F9746@microsoft.com...
| Quote: | Thanks. We have a DSL router with 8-ports and we get 30 static IP's from
our
ISP that just passes through the static addresses. I have another router
set
up behind the DSL router with a public address to forward the necessary
ports
to exchange. Everything is on the same VLAN. So we have 2 routers - 1 for
our production network behind our Lucent firewall and another that
forwards
ports to exchange includeing webmail, terminal services, etc. So exchange
points to .246 and the 2003 server standard point to .20...is this the
wrong
was to do this?
"Marina Roos [SBS-MVP]" wrote:
Hi,
DNS on the servernic should only point to the server IP. Why are both
servers having a different Gateway?
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"brtnharv" <brtnharv@discussions.microsoft.com> schreef in bericht
news:CF21DC9E-E40D-499D-B575-868A513D6346@microsoft.com...
SBS 2003
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn7
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server
Adapter
Physical Address. . . . . . . . . : 00-0E-0C-65-B4-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.246
DNS Servers . . . . . . . . . . . : 10.10.10.100
10.10.10.101
Primary WINS Server . . . . . . . : 10.10.10.105
Secondary WINS Server . . . . . . : 10.10.10.100
2003 standard (server1)
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn1
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-0C-F1-7D-2B-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.20
DNS Servers . . . . . . . . . . . : 10.10.10.100
Primary WINS Server . . . . . . . : 10.10.10.100
Thanks again.
"SuperGumby [SBS MVP]" wrote:
add the GC role to SBS and post the full output of 'ipconfig /all
C:\ipconfig.txt' from all servers (and one WS may be handy).
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:BB5EA59F-D505-488F-ABAE-53A8252A648B@microsoft.com...
Thanks for your replies. I'm still a bit confused though. I
dcpromo'ed
the
SBS server to an existing 2 - DC 2003 enviroment. I then
transfered
all 5
FSMO roles to the SBS server. The global catalog still remained
on
the
server1 (one of the original 2 DC's). Everything was working fine
as
of
then.
Things started to go south when the installation of Exchange on
the
SBS
2003
server occured. The install of exchange was "successful", but
none of
its
services would load. Like I said I finally got exchange
uninstalled
and
reinstalled. This is when I started to have issues, event viewers
were
going
crazy, DNS wasn't working right and replication was not happening.
It
looked
as the my other server (server8) that i talked about in my
original
post
never was part of the replication process. It almost seemed that
there
were
2 different schemas in the same domain. I therefore got rid of
the
server8
by taking it back to a standalone. I now currently have server1
and
server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange
(which is
working fine both internal and external). AD seems fine also, but
DNS
is
not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the
process
you
describe suggests to me that the SBS (and therefore Exchange) was
installed
with the same name as a previously existing system which may not
have
been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously
existing
server AD must be inspected for traces of the previous object,
any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed
all
traces
of
this must be removed from AD.
Start the SBS install and stop at the point that the OS
installation
is
complete but before the SBS installation wizard starts asking
questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO
roles
moved
to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing
domain,
company.local, which has 3 - 2003 standard DC's. It joined the
domain
fine,
but during installation of Exchange something failed. The only
way
could
get
exchange to come back was to use the /disasterrecovery command
on
setup.
I
then uninstalled and reinstalled it to a new disk on the
server.
Exchange
works fine now. The next issue was that one of my servers,
server8,
could
not replicate with other DC's on the domain. I dcpromo'ed
server8
back
to
a
stand alone because it was a new server that was not running
anything
as
of
then. That fixed the replication problem. Now though, I am not
seeing
my
2
other DC's, server1 and server2, under the company.local -
_msdcs
directory.
I am only seeing one server, in this case, server7 which is the
SBS
2003
server with exchange. My understanding is that all DC's should
show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its
FQDN
and a
Hex? entry. The network "seems" to be ok but I'm not 100%
sure.
Event
viewers are not showing any errors either. I believe the
mistake
was
installing SBS into an existing domain and not a new domain.
Sorry
for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
brtnharv
Guest
|
| Posted:
Sun Jan 16, 2005 12:13 am Post subject:
Re: Installed SBS2003 into existing 2003 domain, now issues |
|
|
Thanks for the offer. I'm worried that DNS or some other critical service is
going to go south on me soon.
"Jeff Middleton [SBS-MVP]" wrote:
| Quote: | it would probably take a little bit of looking, but I would be willing to
look at your server to confirm the current status regarding the upgrade you
are doing.
The Swing It!! Kit offered at SBSmigration.com does explain how to
accomplish what you originallly described. I believe it would give you an
exit strategy from this situation as well.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:CF21DC9E-E40D-499D-B575-868A513D6346@microsoft.com...
SBS 2003
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn7
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
Physical Address. . . . . . . . . : 00-0E-0C-65-B4-02
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.246
DNS Servers . . . . . . . . . . . : 10.10.10.100
10.10.10.101
Primary WINS Server . . . . . . . : 10.10.10.105
Secondary WINS Server . . . . . . : 10.10.10.100
2003 standard (server1)
Windows IP Configuration
Host Name . . . . . . . . . . . . : saturn1
Primary Dns Suffix . . . . . . . : saturn.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : saturn.local
Ethernet adapter Intel Pro 1000 MT Gigabit Ethernet Adapter - onboard:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-0C-F1-7D-2B-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.20
DNS Servers . . . . . . . . . . . : 10.10.10.100
Primary WINS Server . . . . . . . : 10.10.10.100
Thanks again.
"SuperGumby [SBS MVP]" wrote:
add the GC role to SBS and post the full output of 'ipconfig /all
C:\ipconfig.txt' from all servers (and one WS may be handy).
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:BB5EA59F-D505-488F-ABAE-53A8252A648B@microsoft.com...
Thanks for your replies. I'm still a bit confused though. I
dcpromo'ed
the
SBS server to an existing 2 - DC 2003 enviroment. I then transfered
all 5
FSMO roles to the SBS server. The global catalog still remained on
the
server1 (one of the original 2 DC's). Everything was working fine as
of
then.
Things started to go south when the installation of Exchange on the
SBS
2003
server occured. The install of exchange was "successful", but none of
its
services would load. Like I said I finally got exchange uninstalled
and
reinstalled. This is when I started to have issues, event viewers
were
going
crazy, DNS wasn't working right and replication was not happening. It
looked
as the my other server (server8) that i talked about in my original
post
never was part of the replication process. It almost seemed that
there
were
2 different schemas in the same domain. I therefore got rid of the
server8
by taking it back to a standalone. I now currently have server1 and
server
2, both 2003 standard, and server7, which is SBS 2003 w/exchange
(which is
working fine both internal and external). AD seems fine also, but DNS
is
not
giving me a warm and fuzzy feeling. thanks again. Matt.
"SuperGumby [SBS MVP]" wrote:
please describe your installation process/environment.
The fact you had a problem with Exchange which was fixed by the
process
you
describe suggests to me that the SBS (and therefore Exchange) was
installed
with the same name as a previously existing system which may not have
been
fully removed from AD.
Your process should have been similar to:
If the SBS was to be installed with the same name as a previously
existing
server AD must be inspected for traces of the previous object, any
references must be removed. All DC's must be available.
If there was a previous Exchange server which had been removed all
traces
of
this must be removed from AD.
Start the SBS install and stop at the point that the OS installation
is
complete but before the SBS installation wizard starts asking
questions
about creating the AD and installing SBS components.
The target must then be promoted into a DC role and the FSMO roles
moved
to
it, it must also be made a GC.
You can then continue the SBS installation wizard.
"brtnharv" <brtnharv@discussions.microsoft.com> wrote in message
news:AE7FC560-D22C-4910-B075-70546EA5E6D5@microsoft.com...
Hello there, I recently installed SBS 2003 into our existing
domain,
company.local, which has 3 - 2003 standard DC's. It joined the
domain
fine,
but during installation of Exchange something failed. The only way
could
get
exchange to come back was to use the /disasterrecovery command on
setup.
I
then uninstalled and reinstalled it to a new disk on the server.
Exchange
works fine now. The next issue was that one of my servers,
server8,
could
not replicate with other DC's on the domain. I dcpromo'ed server8
back
to
a
stand alone because it was a new server that was not running
anything
as
of
then. That fixed the replication problem. Now though, I am not
seeing
my
2
other DC's, server1 and server2, under the company.local -> _msdcs
directory.
I am only seeing one server, in this case, server7 which is the SBS
2003
server with exchange. My understanding is that all DC's should
show up
in
the _msdcs directory in DNS with a Alias (CNAME) entry with its
FQDN
and a
Hex? entry. The network "seems" to be ok but I'm not 100% sure.
Event
viewers are not showing any errors either. I believe the mistake
was
installing SBS into an existing domain and not a new domain. Sorry
for
the
long post, it's been a long 2 days. Thanks. Matt.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in