Exchange Server Forums

Cant connect to new exchange when old exchange is disconnected

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Installation >> Cant connect to new exchange when old exchange is disconnected

Page: [1] 2 next > >>

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Cant connect to new exchange when old exchange is disco... - 4.Jul.2008 5:44:21 PM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

Hi all,

We are in the process of setting up a new exchange 2003 ent. server as the box that our old one is on needs to be rebuilt. I installed exchange on the new server as a new exchange server and have started the process of moving a few test mailboxes over to the new machine. When both old and new machines are running, exchange and outlook work flawlessly. Exchange even tells outlook that the account I am trying to connect to now exists on the new machine and changes outlooks exchange server address to the new box (as it should). My problems arise when I turn off or disconnect the old server from the network. When I do this, outlook can no longer connect to the new machine. I tried to figure out what was going on by checking the mailboxes in Exchange System Manager (on the new server) but it wont show me mailboxes (just hangs when I try to connect to "Administration Groups->First Administrative Group->Servers->New Server->First Storage Group->Mailbox Store->Mailboxes"

Obviosuly the new server is still somehow dependant on the old server. DNS shouldnt be the issue as its running on a seperate box and no other machines had connectivity (to the internet, not exchange) or resolving issues when the test was being done.

Have I missed a step or possibly done something wrong during exchange setup? Any information the experts on here have for me is greatly appreciated.

< Message edited by xgumbyx -- 4.Jul.2008 5:45:39 PM >

Post #: 1

Featured Links*

RE: Cant connect to new exchange when old exchange is d... - 4.Jul.2008 6:09:05 PM

Sembee

Posts: 3500
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

Have you replicated the public and system folders? Moving to a new server is more than just moving the mailboxes. There are a number of settings and content that has to be replicated and moved to the new server before you move the mailboxes. My guide to the process is http://www.amset.info/exchange/migration.asp

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to xgumbyx)

Post #: 2

RE: Cant connect to new exchange when old exchange is d... - 4.Jul.2008 6:19:10 PM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

I've just been looking into this and was in the process of moving the public and system settings over to the new server using your guide before you even replied :)

I'm a bit stuck on the "Send Hierarchy" number of days. I have no idea how many days is a decent amount to set or if there is some standard range (still googling here to try and find out).

Any suggestions?

(in reply to Sembee)

Post #: 3

RE: Cant connect to new exchange when old exchange is d... - 4.Jul.2008 6:51:16 PM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

Reading your instructions I see the following

"Configure the public folders on the replication tab in ESM so that both servers are listed. Use the Propagate settings where appropriate to send the replication setting to the sub folders."

I'm trying to figure out where the "Replication" tab is in ESM as well as "Propagate settings"

Maybe I am taking the instructions too literal, I'm not sure. I do see a "Replication Status" Folder in ESM at "Administrative Groups->First Administrative Group->Servers->Old Server->First Storage Group->Public Folder Store"

I do see both servers listed at "Administrative Groups->First Administrative Group->Folders->Public Folders(right click->properties-general)"

I did try to right click on both "Administrative Groups->First Administrative Group->Folders->Public Folders" and "Administrative Groups->First Administrative Group->Servers->Old Server->First Storage Group->Public Folder Store" and choose "Send Hierarchy" but 45 minutes later it doesnt seem to have done anything. Possibly because I cant find the "propagate settings" option ?

Not quite sure where to go from here :(

(in reply to xgumbyx)

Post #: 4

RE: Cant connect to new exchange when old exchange is d... - 4.Jul.2008 7:09:31 PM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

Ok, I see how to set the Replication now on each items in the "Public Folders" section by going to its properties then Replication. I still however done see any Propagate option. I am however seeing some replication take place now.

(in reply to xgumbyx)

Post #: 5

RE: Cant connect to new exchange when old exchange is d... - 4.Jul.2008 7:16:55 PM

Sembee

Posts: 3500
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

Public Folder replication is slow. I usually leave it a week or more to replicate the content. You can force the content to go across - but you will not see anything happen instantly.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to xgumbyx)

Post #: 6

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 10:39:41 AM

Exchange_Geek

Posts: 992
Joined: 31.Dec.2006
Status: offline

I still however done see any Propagate option. I am however seeing some replication take place now.

Wel,, you would find on the right-click on the Public folder container under folders.
If you want to play around adding multiple / removing replicas try working with PFDavAdmin - its pretty easy and trust me its a great tool to work especially with PF Replication.

http://www.msexchange.org/articles/PFDavAdmin-tool-Part1.html
http://www.msexchange.org/articles/PFDavAdmin-tool-Part2.html
http://www.microsoft.com/downloads/details.aspx?FamilyID=635BE792-D8AD-49E3-ADA4-E2422C0AB424

(in reply to Sembee)

Post #: 7

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 2:22:57 PM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

I again tried removing the old server (just disconnected it from the network) and echaange immediately stopped respnding on the new server as well. Surely I've done something wrong along the way. From memory, here is how I installed the new server.

1) Installed Windows Server 2003 Enterprise and applied all service packages and hotfixes
2) Joined domain
3) Installed SNMP, IIS, NNTP, ASP.NET
4) Install Support Tools
5) From the install disk chose - Deploy Exchange Server
6) Chose New Exchange Server
7) Ran dcdiag /s:DomainController
8) Ran netdiag
9) Ran ForestPrep and used defaults(I see now that I maybe shouldnt have done this as AD was already prepared for Exchange
10) Ran DomainPref and used defaults
11) Ran Exchange Setup and chose "Typical" and used defaults
12) Selected Organization Name
13) Completed Install

This list is pretty much from memory so I might have missed something but its basically just a default install. For some reason, the new server is still dependant on the old one. I've now also replicated the public and system folders but even if I hadnt yet, why would the new server be dependant on the old server at all? I dont see a reason for this as I chose to install a new server and did nothing to tell the new server that the old one even existed.

Does anyone have any ideas or suggestions?

(in reply to Exchange_Geek)

Post #: 8

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 4:04:02 PM

Exchange_Geek

Posts: 992
Joined: 31.Dec.2006
Status: offline

Ok lets get this sorted out ASAP, tell me what excatly you mean by "exchange immediately stopped respnding on the new server as well." Get me the answer to thsi question and we can solve this out. dont worry

(in reply to xgumbyx)

Post #: 9

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 4:04:26 PM

Exchange_Geek

Posts: 992
Joined: 31.Dec.2006
Status: offline

(in reply to xgumbyx)

Post #: 10

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 5:12:00 PM

Sembee

Posts: 3500
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

Is the current server a domain controller or a member server? If it is a domain controller then then "turn off" method (which I don't actually do) will not work. When Exchange is on a domain controller that is the ONLY domain controller used by Exchange - even when you introduce a second server.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to Exchange_Geek)

Post #: 11

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 5:34:09 PM

Exchange_Geek

Posts: 992
Joined: 31.Dec.2006
Status: offline

I am expecting DSAccess errors if thats the case, however i want to understand whats going wrong "exactly", so awaiting response.

(in reply to Sembee)

Post #: 12

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 5:34:50 PM

Exchange_Geek

Posts: 992
Joined: 31.Dec.2006
Status: offline

I am expecting DSAccess errors if thats the case, however i want to understand whats going wrong "exactly", so awaiting response.

(in reply to Sembee)

Post #: 13

RE: Cant connect to new exchange when old exchange is d... - 5.Jul.2008 6:59:10 PM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

Thanks for the responses you two, I do appreciate it.

What I meant by "exchange stops responding" is that client connections are no longer working (client side) and if I try to browse the mailboxes in exchange system manager it just times out showing me nothing.

The old machine is an active directory domain controller as well as an exchange server (this was not setup by me), but we have since added a second (and even a third) domain controller.

After installing the newest DC, we were sure to test its functionality by disconnecting the old dc/exchange box to make sure that the DC portion of our network still worked, and it worked just fine but obviously this doesnt mean much other than our network as far as DNS and Domain Control goes works independant of the old DC/exchange server.

When I did dcdiag I was sure to not use the original DC/exchange server. I used our new DC by doing dcdiag /s:newDC

Thanks again for the response.

< Message edited by xgumbyx -- 5.Jul.2008 7:02:35 PM >

(in reply to Exchange_Geek)

Post #: 14

RE: Cant connect to new exchange when old exchange is d... - 6.Jul.2008 12:58:45 AM

Exchange_Geek

Posts: 992
Joined: 31.Dec.2006
Status: offline

Great, now we have some thing to work upon. You have 2 DCs - both Exchange Servers - both DNS Servers.

Now, what i want you to check is the second DC (your new Exchange server) a GC?
I have a strong intuition that its not - if thats the case please make it a GC and REBOOT once.

Also, on your new Exchange server - how many NIC Cards are there ? Make sure none are teamed and have the correct N/W Binding order. To work even better - have your new server point to itself for preferred DNS Server location.

If possible, please tell us the events do you see when such an issue takes place.
Are they 2102, 2103, 2114 source MsExchangeDSAccess ?????

You might see events 9175 / 8197 - ignore them they are generic when stores go offline.

Awaiting response.

(in reply to xgumbyx)

Post #: 15

RE: Cant connect to new exchange when old exchange is d... - 6.Jul.2008 1:52:35 AM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

Ok, so in response to your first comment that I have two DCs - both exchange servers - both dns servers. This is actually not true. I'll give a breakdown of our current setup which consists of 4 PC's (Including the new one)

Our first DC/DNS/DHCP/Exchange Server
OldServer - Initial Setup (Parts removed will show (removed))
- Windows Server Ent. 2003
- Exchange Server Ent. 2003
- Active Directory
- DNS
- DHCP (Removed)

SecondServer - some web apps here and also ActiveDir in case "OldServer" went down

ThirdServer - Set up as a new DNS/DHCP/DC -Will take over OldServer as main DC box once OldServer is retired.

NewServer - This is the box we are putting exchange on. Currently it has no DNS/ActiveDir(DC)/. Just Exchange

So, what we are wanting to do here is phase out OldServer. ActiveDirectory works well on ThirdServer and SecondServer will be there for redundancy. DNS and DHCP are already running on ThirdServer and most client machines are now using it without issue.

I'm not sure about GC (I assume this is the global catalog) and how its setup. I'm going to do more reading on that after this post. There is also only one NIC in this box. Are the events you were askin for still relevant? I will check for them still if they are. In the meantime, I am going to read more about GC. From what you say, GC seems to be essential or good practice to have on an Exchange server, or is that just for an Exchange server that is also a DC?

I'll await your response and read up on GC and get those error codes if they are still relevant.

Thanks again Exchange_Geek

(in reply to Exchange_Geek)

Post #: 16

RE: Cant connect to new exchange when old exchange is d... - 6.Jul.2008 2:14:23 AM

Exchange_Geek

Posts: 992
Joined: 31.Dec.2006
Status: offline

As per documetation given below Exchange on a DC SHOULD always be a GC (Global Catalog) http://technet.microsoft.com/en-us/library/aa997060(EXCHG.80).aspx

By default the first DC in every domain is always a GC, and thats V.IMP for every OL / Windows Client - since thats the server who authenticates every user against AD. Hence, if you shut down or remove that Server "every" AD integrated application will depend on a GC's existance.

Now, if we had those events clarified we could have proceeded better - still no issues. Can you tell me which server is your New Exchange server pointing as "Preferred DNS Server".

(in reply to xgumbyx)

Post #: 17

RE: Cant connect to new exchange when old exchange is d... - 6.Jul.2008 3:25:42 AM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

On the New Server, the DNS is pointing to our new DNS server (ThirdServer from my previous post).

I want to make sure that you realize that the New Server will NOT be a DC. This is partially the reason for retiring the old server, we want to get away from one server having Exchange and ActiveDirectory installed (which I've been told is best practice). Also in response to your statement "Hence, if you shut down or remove that Server "every" AD integrated application will depend on a GC's existance.", we CAN remove OldServer from the domain and ActiveDir does still run as we have it on "ThirdServer" (also also SecondServer). I just wanted to clarify this.

Now for the events.

I do have a few with 2103 (thats the only one of the few mentioned)
Process MAD.EXE (process=4280) All Global Catalog Server in use are not responding.
name.of.OldServer

So I see that you are most likely correct in regargs to GC. So if I understand correctly, GC will have to be moved (or installed) to "ThirdServer" which will be our main DNS and ActiveDir Server (no exchange) when everything is setup how we want. Does this mean that I should still install GC on NewServer (Exchange Server) as well?

I feel like we are getting somewhere :)

(in reply to Exchange_Geek)

Post #: 18

RE: Cant connect to new exchange when old exchange is d... - 6.Jul.2008 3:38:41 AM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

I've just had a read here http://www.computerperformance.co.uk/w2k3/w2k3_global_catalog.htm at global catalogs adn checked on "ThirdServer" and "SecondServer" and neither had GlobalCatalog checked. I've now checked it off on both servers. I wont be able to test anything tonight (as far as removing a server from the network) as the office is at another location but I may be able to tomorrow if I can make some time to go into the office.

Gumby

(in reply to xgumbyx)

Post #: 19

RE: Cant connect to new exchange when old exchange is d... - 6.Jul.2008 3:47:01 AM

xgumbyx

Posts: 14
Joined: 1.Feb.2008
Status: offline

Also, reading one of the links you posted it mentioned something about DNS tells the other machines on the network where the GC(s) are located. I went to ThirdServer (Our new DNS and eventually main AD/DC) and checked in dnsmgmt and I now see all 3 servers listed now in regards to GC in various places within the dnsmgmt program.

(in reply to xgumbyx)

Post #: 20