Link to home
Start Free TrialLog in
Avatar of Scott Nowacki
Scott Nowacki

asked on

SBS 2008 Recovery Issue

I have rebuilt a SBS 2008 server following a crash. Because of the No Backup reason I had to reinstall it in migration mode with a new name. It brought over AD from the backup domain controller. Apparently it still thinks the old server is on the network and is causing a lot of issues.

The first of which is that Exchange doesn't work. The computers won't connect to the new server when we add a new profile in Outlook 2010. It keeps telling me that outlook is offline.

Here's a screenshot of the server. How do I start getting rid of this and fixing it?

Also - connecting to http://servername/remote doesn't work. It gives me an IIS error.

THanks

Scott
Capture.PNG
ASKER CERTIFIED SOLUTION
Avatar of Gareth Gudger
Gareth Gudger
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of dsnegi_25dec
dsnegi_25dec

Did you check through OWA ?
Can you check with new outlook profile ?
Avatar of Scott Nowacki

ASKER

OWA does not work. https://servername/remote does not work either. Throwing errors about permissions and missing files.

VPN connection is running even though it seems that the RRAS service is running in services but RRAS is not enabled or configured on the server.

I'm pretty close to rebuilding it as a new domain and rolling over the 8 workstations. Just to get a fresh start. The data is on another drive that can be simply moved to the new server.
Might be quicker at this point. Good luck!
diggisaur:

I used the commands you mentioned and redirected all the mailboxes to the new server. Then I reconfigured Outlook to connect to the new server and imported their mailboxes back into the new mail server. It all seemed Ok on Friday and now today none of the Outlook mailboxes are connecting. As a matter of fact, a number of the machines can't find the new server on the network. I'm thinking it's a DNS issue.

Do you have a link to some details for using ADSIEDIT like you mentioned above?

Thanks,

Scott
When you say a number of machines can't find the server on the network, are you referring to email services only? Or they can't find the server through DNS or a ping?
Pinging machine name was not working this morning. Pinging IP address is always working. Now they're pinging just fine either way. It was like the DNS was not working across the VPN this morning.
Ah. So was this just affecting VPN users?

How is it now? Is everything working again?
The VPN is a PITA. I'm going to start a new question specifically about the VPN here.
Understood. Glad you were able to get internal users working correctly!