richtree
asked on
Why Outlook 2003 is unable to connect to Exchange 2003?
Origin: single network single domain (Windows 2003):
default gateway: 10.0.1.1
svr-dc-dns1: 10.0.1.11
svr-dc-dns2: 10.0.1.12
svr-exch: 10.0.1.13; dns = 10.0.1.11/12
workstations use dhcp.
all servers and workstations are in the same network.
No issues noticed.
Changes made:
segment workstations from servers as follow:
servers stay the same
workstations are put in 10.0.2.0/24 network
use dhcp to dispatch ip (10.0.2.x) and dns (10.0.1.11/12);
workstations are able to ping servers by ip and host name;
There are no dc in 10.0.2.x network.
Issues noticed so far (6 days since change):
A few users are not able to open Outlook properly. When setting up the user's Outlook profile again, Outlook says 'The name could not be matched to a ame in the address list'. When trying to set up another user, Outlook is unable to resolve the mailbox even though the mailbox is there.
Q#1. Is the above issue related to the above network change? If yes, what's the ultimate cause?
Q#2. Any potential issues if there is no domain controller in the new user segment? for example, will computer accounts become out of synch with AD?
Q#3. If there must be a domain controller in the new user segment, is it easy to modify svr-dc-dns2 and put it in the new 10.0.2.x network?
Q#4. Will more uses run into Outlook issues?
Thanks.
default gateway: 10.0.1.1
svr-dc-dns1: 10.0.1.11
svr-dc-dns2: 10.0.1.12
svr-exch: 10.0.1.13; dns = 10.0.1.11/12
workstations use dhcp.
all servers and workstations are in the same network.
No issues noticed.
Changes made:
segment workstations from servers as follow:
servers stay the same
workstations are put in 10.0.2.0/24 network
use dhcp to dispatch ip (10.0.2.x) and dns (10.0.1.11/12);
workstations are able to ping servers by ip and host name;
There are no dc in 10.0.2.x network.
Issues noticed so far (6 days since change):
A few users are not able to open Outlook properly. When setting up the user's Outlook profile again, Outlook says 'The name could not be matched to a ame in the address list'. When trying to set up another user, Outlook is unable to resolve the mailbox even though the mailbox is there.
Q#1. Is the above issue related to the above network change? If yes, what's the ultimate cause?
Q#2. Any potential issues if there is no domain controller in the new user segment? for example, will computer accounts become out of synch with AD?
Q#3. If there must be a domain controller in the new user segment, is it easy to modify svr-dc-dns2 and put it in the new 10.0.2.x network?
Q#4. Will more uses run into Outlook issues?
Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Is DC not required in the new subnet once a new site is added in AD?
ASKER
Is it ok to add the new subnet (10.0.2.x) to the site where the original subnet (10.0.1.x) sits?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks.
ASKER
10.0.2.X is physically same site as 10.0.1.x,gigabit link between them.
Please comment on my questions.