Not working after installation

Not working after installation (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Installation

Message

J0H4N -> Not working after installation (19.Dec.2005 9:26:36 AM)
I have installed Exchange Server 2003 on my server 2003. The problem is that I can't get Outlook to connect to the exchange server from any other computer exept the computer where I istalled exchange server???? I says it can´t connect to the exchange server. Im a newbie on exchange server so any help would be good. It´s propably something that I haven't completed in the installation.... What could be wrong with my setup?? Outlook Webaccess is working fine on all computers.

pjhutch -> RE: Not working after installation (19.Dec.2005 1:38:34 PM)
Do server's DNS (and WINS) entries exist? Do the client's point to Windows 2000/2003 DNS servers? Run IPCONFIG /all Is the Server on the LAN or in a DMZ? Is there a firewall present between client and servers? Try using RPCPing utility between a client and the server to test connectivity. Also, try using DCDIAG and NETDIAG utilities on the server as well. Use Exchange Analyzer tool to check for mis-configurations.

J0H4N -> RE: Not working after installation (19.Dec.2005 2:09:17 PM)
What do you mean by "Do server's DNS (and WINS) entries exist?"? The client points to a 2003 dns server. The server in on LAN. There is a firewall but I have tried diseabling the firewall and it doesn´t help. RPCPing on XP, is that possible. How du you use that program? DCDIAG = passed all tests. NETDIAG = error on WINS service test: the test failed, We were unable to query the WINS servers

pjhutch -> RE: Not working after installation (19.Dec.2005 2:42:09 PM)
For DNS, check that the Host (A) address exists. For rPCPing there are two programs, a server and a client, run the server program on server and then run the client bit on client PC. it should check that RPC calls can be received on server. (Vital for Outlook to work). http://support.microsoft.com/kb/175496/EN-US/ Also make sure Exchange MTA service is running. WINS is useful for Netbios name resolution rather than DNS Host name resolution.

J0H4N -> RE: Not working after installation (19.Dec.2005 3:19:24 PM)
Can´t get rpcping to work. Only gives me errors. Do I have to set up RPC on the exchange server?

pjhutch -> RE: Not working after installation (19.Dec.2005 3:24:36 PM)
What are the errors?

J0H4N -> RE: Not working after installation (19.Dec.2005 3:24:37 PM)
I haven´t done anything exept installed exchange server. What are the vital steps in end after the installation? I have tried clicking on so many thing now that I can´t remember what I have done. I wonder if it would be best to uninstall and install again. But doesn´t it seem like theres someting in the connections that are not right since webmail is working and outlook is working on the server where exchange is installed? Can i test the connection to the exchange server somehow? I have tried pinging the servers Ip and that works.

pjhutch -> RE: Not working after installation (19.Dec.2005 3:27:24 PM)
If you have installed Exchange, have all the services start in Services.msc on the server (The Events and SRS aren`t usually required). Then to use outlook you need to create AD accounts with Mailboxes. To get outlook to connect, you just need to setup Outlook, point it to Exchange Server name and name of mailbox and thats it.

J0H4N -> RE: Not working after installation (19.Dec.2005 3:28:30 PM)
First error: RPC call raised exception 0x6ba The server is unavailable Klick Ok. Second error: RPC call raised exception 0x6ba The server is unavailable Third error: RPC call to RPING's Server side app raised exception 0x6ba The server is unavailable

J0H4N -> RE: Not working after installation (19.Dec.2005 3:35:35 PM)
Services: Status Microsoft Exchange Event Not started Microsoft Exchange IMAP4 Not started Microsoft Exchange Informatino Store Started Microsoft Exchange Management Started Microsoft Exchange MTA Stacks Started Microsoft Exchange POP3 Not started Microsoft Exchange Routing Engine Started Microsoft Exchange Site Replication Service Not started Microsoft Exchange System Attendant Started

pjhutch -> RE: Not working after installation (19.Dec.2005 3:38:02 PM)
Has the Remote PRocedure Call (RPC) service started as well? Other than that, I have no idea why Outlook cannot connect...

J0H4N -> RE: Not working after installation (19.Dec.2005 3:42:59 PM)
Yes. The Remote PRocedure Call (RPC) locator service in not running

J0H4N -> RE: Not working after installation (19.Dec.2005 3:44:58 PM)
Still doesn´t it seem like theres some problem with DNS since clients doesn´t find the exchange server?

de.blackman -> RE: Not working after installation (20.Dec.2005 4:59:39 AM)
Where you able to successfully create profiles for the users? When you click checkname, does it resolve the user's name? from the client what happens when you type \\ExchangeServerName??

J0H4N -> RE: Not working after installation (20.Dec.2005 7:23:37 AM)
I haven´t created any new users. But i have created mailboxes on the old users that "were moved" to active directory with the installation of exchange server. When I try to create a new user it allways complains about the password that I type in?????? When I click checkname, it stops to think for a while, and then a messagebox pops up and it says "The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action." So it does not resolve the user's name. I have tried typing the IP, name of the exchange server, but the result is allways the same.

pjhutch -> RE: Not working after installation (20.Dec.2005 10:12:50 AM)
Check group policy about passwords, mybe you have enabled strong passwords that require a specific length and or use if mixed letters and numbers. Look in the Default Domain Policy under Computer Config, Windows Settings, Security Settings, Account Policies. As for the client end, are the accounts enabled? You cannot access a mailbox if its disabled or locked out in any way. Check DNS again, where are your DNS servers? Are they on the DCs or elsewhere? Are you using Dynamic updates? Is DNS AD Integrated or use the Primary/Secondary setup? How are the clients set up? Are they joined to the Domain? Is it the same domain as the Exchange server? Do clients get TCP/IP via DHCP? Are the correct DNS IP addresses allocated? It must be the AD DNS to work properly. IF you have Outlook installed on the server, make sure that the correct mapi32.dll is in C:\Windows\System32 (Version 6.5.7226.0, 620K) and not the one for Outlook.

J0H4N -> RE: Not working after installation (20.Dec.2005 1:16:29 PM)
The accounts are enabled. What do you mean by check DNS "Are they on the DCs or elsewhere?"? Not sure if I am using Dynamic updates, what is it and what does it do? DNS AD is integrated. Clients are not joined to the domain, they are in a workgroup. I have heard that clients doesn´t have to be in the same domain as the exchange server. Also I have notised that login to the workstations gets slow when they are part of the domain, this is not the case when they are in workgroup. Do clients get TCP/IP via a SMC firewall/router that works as DHCP. The server itself is not configured as a DHCP. "Are the correct DNS IP addresses allocated? It must be the AD DNS to work properly." Not sure. Can I control this in a easy way? The correct mapi32.dll is in C:\Windows\System32

J0H4N -> RE: Not working after installation (20.Dec.2005 2:43:06 PM)
How do I get the IP of my DNS server? I tried to run NSLOOKUP on both the server and on clients. On the server it reqonised my DNS server IP 127.0.0.1 But on workstations NSLOOKUP returned "Can´t find server name for address 127.0.0.1. No response from server" Is this the problem????

pjhutch -> RE: Not working after installation (20.Dec.2005 2:53:38 PM)
ON the DNS server type IPCONFIG, it should display the IP address of itself. 127.0.0.1 is a generic IP address meaning 'me' no matter what the IP address. You only ping that to test the network card. It will refer to itself and not another machine. On the client ping the IP address of the server, you get it using NSLOOKUP <servername> or the just use PING <servername> Typing IPCONFIG /ALL will display IP address and the DNS IP addesses as well. It should display the server's IP address in the list on the client. Dynamic DNS means that clients incl Windows 2000, XP and 2003 will automatically add or update Host records on the DNS server w/o user intervention. If you give me an ex

J0H4N -> RE: Not working after installation (20.Dec.2005 3:10:38 PM)
Ipconfig on server returned: IP: 192.168.2.21 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.2.57 Pinging 192.168.2.21 -> Worked fine. Ipconfig /all on client: C:\WINDOWS\system32>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : huolto Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network on Physical Address. . . . . . . . . : 00-0C-F1-CF-6B-2C Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.2.121 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.57 DHCP Server . . . . . . . . . . . : 192.168.2.57 DNS Servers . . . . . . . . . . . : 127.0.0.1 192.168.2.57 Primary WINS Server . . . . . . . : 192.168.2.21 Lease Obtained. . . . . . . . . . : 20. joulukuuta 2005 15:59:28 Lease Expires . . . . . . . . . . : 27. joulukuuta 2005 15:59:28

Page: [1] 2 next > >>