Can't log on to MS Exchange Server
This is page 2 of the discussion. Read the opening post
Software
This is page 2 of the discussion. Read the opening post
by shanghai sam
by justinf
by shanghai sam
by charleskin
Since there are some pretty decent troubleshooting steps already here and it seems almost every aspect of the problem has been touched on, I'll give a couple of "last gasp" ideas for you to try.
Step one: find out the IP address for the exchange server. Enter this value instead of the server name for "connect to".
Step two: (this one is a stretch) add the IP address of the exchange server to your web-browser's proxy list.
My recommndation is try step one first, then step one and two together, then if that still doesn't help try step two by itself.
I know, this is out there, but it might help.
by estvb
by fivemajors
by estvb
by estvb
by stolli
When we set up our Exchange server, we had logon problems because of our Sonic firewall and the DMZ. We replaced the appliance with a PIX and that fixed the general NT and 2000 population's problem. However, Win95 users still could not logon. It was resolved by editing the Hosts file to id the mail server. But the WEIRDEST part was that for Win95 users, I had to make a DNS entry using our local domain name and then disable it. It worked every time.
I think no matter what - the answer isin DNS\WINS and HOSTS. But start by triple checking your spelling and typing. If you didn't know what the server names were to begin with, maybe the IT staff can't spell and you just had to type what they told you. Could be...
Good luck - thisis better than a mystery novel!
by estvb
by fenaikh
Hi
pls read these articles from micrsoft.
Good luck
Mohamed
***Very Important NOTE *********
After you copy the URL a space or a %20 maybe gets inserted in the URL when you paste it into your browser. Delete any spaces or such characters from the URL for the page to be loaded.
using the number of the article as QXXXXXX
http://support.microsoft.com/default.aspx?scid=kb;en-us;QXXXXXX
How to Connect over the Internet to an Exchange Server (Q152725)
Troubleshooting Startup of Windows Client Using TCP/IP (Q155048)
How to use RPCPing to test RPC Communication (Q167260)
Troubleshooting Intrasite Directory Replication (Q170334)
Troubleshooting RPC Problems for Exchange Clients (Q174701)
Using RPCPING To Troubleshoot MTA Connections (Q175496)
Exchange Client Top Support Issues and KB Articles (Q175698)
How to Test Microsoft Remote Procedure Call Performance (Q177446)
HOWTO: Troubleshoot RPC Errors (Q197814)
Troubleshooting DynamicRAS Connector (TCP/IP) (Q199971)
Troubleshooting Calendar Connector for Lotus Notes (Q222893)
List of KB Articles Explaining MTA Basic Concepts and Troubleshooting (Q247133)
troubleshooting Link Monitor When Red Arrow Is Displayed (Q252209)
The Microsoft Exchange Address Book was Unable to Log on to the Microsoft Exchange Server Computer (Q268575)
You Cannot Connect to Simple Mail Transfer Protocol Message Transfer Agent (Q297139)
by estvb
by estvb
I found and tried out the rpingc32 program that some people suggested and got this message:
RPC Binding returned (0x6be). Could not bind using these parameters:
network address = minermail.umr.edu
endpoint = 251
UUID =
Failed to Bind onALL Protocols
If I changed the Protocol Sequence to TCPIP I got three error messages that said "RPC call raised exception 0x6ba. The server is unavailable." and got this message:
Successful RPC binding using these parameters:
network address = minermail.umr.edu
endpoint = 2256
UUID =
protocol sequence = ncacn_ip_tcp
Server Statistics:
#Calls Received at Server = 0
#Calls Initiated by Server = 0
#Packets Received at Server = 0
#Packets Initiated by Server = 0
Ping #1Failed
I have no idea what any of it means or if its usseful, please interpret!
by estvb
by r.alvarez
The problem is local to your computer since you are able to access it from any computers in the institute.
There are two things you need to check in your PC - TCP/IP and the MS Outlook(Office) software. We had cases were the TCP/IP stack got corrupted and couldn't access emails. We had to re install the TCP/IP protocol(Sometimes you need to reinstall the network card driver.)
You can try reinstalling MS Outlook. It could have some corrupted files that affects the name resolution of mailboxes.
by estvb
by estvb
by estvb
Sorry for the lack of response for Answer 46. I'd set the rating but went back to another unrated answer and then forgot about it. Our accounts are used for more than just email. I don't know how much trouble or how long it would take but I need to access my account for several classes.
Also, there's only a couple of weeks left of classes. I doubt that I'll go through reinstalling Windows and all my applications anytime soon, so if I can't solve the problem before school ends then I'll just close the question and see what happens next year.
The solution to your problem is somewhere within the first 50 answers.
Here's how you determine exactly which answer:
Print out this qestion and all the answers. Offer a reward of $25 - $50 to all your fellow student computer geeks (depending on the financial strength of those students). Pay the reward to anyone who can fix your problem relying ONLY on the Q&A printout that you will provide.
With a fresh set of eyes going over the suggested solutions, something is bound to stand out.
Maxwell
by estvb
The point I was attempting to make in answer 51 was that the solution IS, without question, within the dozens of answers posted on this thread. If you followed ALL of the suggestions made thus far EXACTLY as instructed, your problem would be fixed.
Therefore I can only draw one of two conclusions.
Either you don't possess the technical
wherewithal to delve into the issue to the degree necessary (which is why I made the "pay a buddy" suggestion), or you are simply wasting everyone's time.
By the way, I find it interesting that there are very few, if any, notes of thanks among the previous 51 rejections.
You're welcome.
Best of luck to you,
Maxwell
by estvb
Well I hadn't noticed that I've never thanked any of the individual answers. Rather than thank each person's answer in my response, like you seem to do, I chose to do it a couple of times in my comments. However I haven't given thanks any time recently and for that I'm sorry. I do appreciate all of the help everyone has offered. Thanks!
As for your possible conclusions, I'm sorry if you feel I've just wasted your time but I've tried everything suggested and posted a response with a reason for the rejected answer. I understand that it seems like I'm just overlooking a setting but I'm not. You already suggested in an earlier post that I go through each setting and I did. I checked my settings against the ones helpdesk said were correct and then went through each answer here. If it is a wrong setting somewhere, then it's not one that has been brought up yet. Maybe it's something in the registry?
I suppose that there could be an additional conclusion drawn from this evidence, one of which, of course, is that everyone has simply missed something. In addition, I've seen my share of those unexplainable and elusive little puzzlers, and I wouldsurmise that this is a distinct possibility in your case. When confronted with one of those, I usually weigh the consequences of following each of only two possible courses of action. One, of course, is to continue to troubleshoot, while the other is to simply wipe everything clean and start over from scratch. If I had to decide how to proceed, especially after several hours of troubleshooting with no obvious solution in sight, I would most likely choose the latter.
Nonetheless, reading intoone's intentions on a thread like this (as I touched upon in my previous answer) is probably an exercise in futility, and would most likely lead to incorrect or misguided conclusions. So to give the benefit of a doubt I'll retract my comment about you wanting to waste everyone's time and conclude that your intentions are indeed honorable, and that your problem simply one that is quite baffling and has stumped quite a few talented and well-informed professionals. (At least it has stumped this one.)
Best of luck with your future studies,
Maxwell
by shanghai sam
by athanman
Ok, here's a course of action that in my experience has worked during a predicament similar to yours:
First: Right Click on the Outlook Icon.
You will get a dialog box that says properties.
If your name does not appear before the word properties then it's very likely that we're headed in the right direction.
Next: Left click the properties button towards the middle of the dialog box.
Another dialog box will appear. It will have the heading: "Microsoft Exchange Sever"
...now for the easy part... and this should be easy especially because nothing is wrong with your account... from what you mentioned in your question...
Next: there should be two fields, the top one will say Microsoft Exchange Server: what you need to enter there is the Server Name or ID. If this is already filled in ...leave it as it is. If it isn't you can get it in two ways. You can call your university IT helpdesk or you can go to another computer on Campus and after you've logged on follow the steps above to get to this window and copy the characters there. You can the type them in here on your computer. You'd probably be better off doing this yourself from another computer on Campus.
Next: In the field that say's mailbox, you put in you name as it appears in the Outlook Address Book. Once you've entered it click the "Check Name" button next to it. (Note: You may want to check the spelling of you name in the Address Book to make sure it's properly spelled before doing this.... if it isn'tyou need to spell it exactly as it's spelled in the Address-book.)
Once you've done this... click the apply button at the buttom of the dialog box. Then click OK! Click OK again!
Now you're out of the dialog menus and all you'll ever have to do to log in is to double click on the Outlook Icon.
If this does not work let me know!
by shanghai sam
by athanman
Ok, here's a course of action that in my experience has worked during a predicament similar to yours:
First: Right Click on the Outlook Icon.
You will get a dialog box that says properties.
If your name does not appear before the word properties then it's very likely that we're headed in the right direction.
Next: Left click the properties button towards the middle of the dialog box.
Another dialog box will appear. It will have the heading: "Microsoft Exchange Sever"
...now for the easy part... and this should be easy especially because nothing is wrong with your account... from what you mentioned in your question...
Next: there should be two fields, the top one will say Microsoft Exchange Server: what you need to enter there is the Server Name or ID. If this is already filled in ...leave it as it is. If it isn't you can get it in two ways. You can call your university IT helpdesk or you can go to another computer on Campus and after you've logged on follow the steps above to get to this window and copy the characters there. You can the type them in here on your computer. You'd probably be better off doing this yourself from another computer on Campus.
Next: In the field that say's mailbox, you put in you name as it appears in the Outlook Address Book. Once you've entered it click the "Check Name" button next to it. (Note: You may want to check the spelling of you name in the Address Book to make sure it's properly spelled before doing this.... if it isn'tyou need to spell it exactly as it's spelled in the Address-book.)
Once you've done this... click the apply button at the buttom of the dialog box. Then click OK! Click OK again!
Now you're out of the dialog menus and all you'll ever have to do to log in is to double click on the Outlook Icon.
If this does not work let me know!
by shanghai sam
by lordinfidel
Do you have a personal firewall installed on your system?
If you can not resolve the name using the properties resolve button then several things are happening.
1. Your system can not resolve the exchange server name.
2. Your system can notreach the exchnage server itself via IP.
3. RPC communication is being blocked at a firewall.
Check the following. Open a command prompt
(start/run/ type cmd (2k) command (98/xp).
Press enter.
type (without quotes) "ping mailservername" Do not use a FQDN. Use the netbios name.
Does it resolve and what does it resolve too. If it does not resolve, did you turn off netbios resolution on your network adapter?
If it resolves, but incorrectly, do you have entries in your lmhosts file.
(type nbtstat -c ,press enter and look for the names)
The next place would be your hosts file, this is in c:\windows or c:\winnt\system32\drivers\etc
Open it in notepad, uncheck use this program always. Look to see if you have any static entries.
Once you can ping the exchnage server by netbios name, assuming you are on the same subnet as it. Or by host name if your on different subnets. Try the name resolution again in the outlook exchange properties.
If that does not work... Then look at any personal firewalls. You need tcp 138 and 139, in and out, open in order to connect to exchnage.
by shanghai sam
by jayanth
Hi,
I just came across your post and to be honest, I didn't have the patience to go through all the 55 answers so far.
How is your Outlook Configured? Are you using the 'Corporate Workgroup Option'. Also are you using PST for your mail storagein Outlook. Sometimes what may happen is that the Outlook profile may get corrupted on the local machine.
Before doing anything, backup all your mails. Store them as a single PST file if you wish to.
Now Right Click the Outlook icon on the Desktop and select Properties. If theres no icon, then goto 'Control Panel --> Mail'. Click on Show Profiles and you should be seeing the Profile created for you. **Remove** that Profile and recreate a new one giving all the necessary parameters. Now try accessing your mailbox. Hope this one helps.
Please forgive me, if I have repeated this solution, as I didnt go through all the answers given so far.
by shanghai sam
by wlbowers
Here is a couple of things you can try. Create a
host file in the windows directory. The hosts
file helps windows when it gets stupid.
There should be a hosts.sam (this is a
sample file with some explination). Use
notepad to create the file. Enter a line such as
this:
10.0.0.2 server
Use the tcp/ip address of the server and the
servers name.
Even though you set this information in wins,
according to MS, the os can still say duh, and
refuse to talk to exchange untillit is in the
hosts file.
Number 2
Go into regedit and navigate to the following:
Hkey_Local_Machine\software\Microsoft\Prote
cted Storage Systems Provider
There should be a profile key with your name
on it. Delete it.
You will know needto go to the control panel
and enter mail. Delete your mail profile and
reenter them. And try it.
I had a lot of problems with a clients network
when he upgraded for the 2k blow out. This
became a standard procedure untill I got
everyone stable.
Good Luck Lee
by shanghai sam
The only hosts file I found was in the windows\system32\drivers\etc folder. I don't know if this is the one you meant but I already have an entry in there for the exchange server. The results are the same whether its in their or not so I just leftit there.
I wanted to try recreating the profile after deleting the registry key you mentioned but it wasn't there. I went to HKLM\Software\Microsoft but there was no "Protected Storage Systems Provider". Was it the right key? Well, I guess ifI was going to delete it anyway it just saved me the trouble!
by athanman
Hello, it is I again. I want to revisit the solution I offered in answers no 54 and 55 ... oh and I'm sorry for posting it twice. I got an error message the first time. So I tried again.
Based on my experience I am absolutely sure that when you bring up the Microsoft Exchange server dialog box if for any reason you fail to enter the correct Identity for the Microsoft Exchange Server you will get an error message saying:
"The name could not be resolved. The action could not be completed."
This might very well be your problem. Make sure you have the correct character in there. Make sure that you letter O's are really O's and not the number "0" (zero). The last four characters are usually numbers not letters. Play with it to see ....you have nothing to loose. Whatever happens have a good day!
by shanghai sam
by lordinfidel
Do you have Client for Microsoft networks installed?
If you do not then your system will never be able to respond on ports 138 and 139.
Client for MS networks needs to be installed.
RPC communincation is the key here. Did you confirm however with the IT dept that the IP address of the exchange server is the correct one.
Also, if your system is not part of the domain, I would strongly suggest setting your authentication to none.
In properties of outlook/exchange/Advanced/Logon Security/ choose none. This will force outlook to prompt for a username/password and domain when you try to connect.
In case you don't know who I am.... I am a exchange guru. There is very little that I don't know about exchange.
As far as the RPC util that you tried. It is a client/server app. There are 2 parts to it. Unless the server side of the app was running, what you received was a false positive.
The IT dept would need to have the server side portion in order to verify rpc connectivity. But that will only say that there is nothing blocking connectivity. It will not mean anything though if Client for MS networks is not installed. You will still have the same issue.
Client for MS networks is bound to your network adapter. If it is not there, install it.
by estvb
by lordinfidel
Our next step is to see what it is trying to do.
1. Open a command prompt. (start/run/cmd)
2. type the following:
netstat -a 5 > c:\netstat.txt
3. press enter, you will not see anything, it will appear to hang, that's ok. It's writingthe results to a file. Leave the command prompt open.
4. Now go and try to resolve the name in outlook.
5. Once it times out, wait about 10 seconds. Then go back to your command prompt and press
ctrl-c. This will stop it.
6. Now go toyour c drive and look in there for netstat.txt.
7. You can try posting them here, but it will probably be too much. Or you can send them to me directly.
What did we just do? netstat -a will show us all of the connections your system has in real time.
The 5 says to run every 5 seconds, and the > c:\netstat.txt is just piping the results to a file instead of to the screen.
What I want to know is if the program is actually trying to create a socket.
Also check in the properties for client for MS networks, is it using windows locator service or dce cell?
Also in your services (XP should have services) make sure that RPC is started and set to automatic. And the RPC locator is set to manual.
What I am trying to do is narrow this down of where we need to look. If we don't see ANY connections to the remote server being initiated, then we have to look more closely at the app. If we see a connection being initiated then we have to look at the OS.
by lordinfidel
.... Just took the time to read thru all of the posts and checked out the time line.
Here is what I read into it, let me know if these points are wroing.
1. It used to work.
2. It used to work after you did a clean install.
3. It stoppedworking....when? This is the point i'm confused on. What changed to make it stop working. Did it stop working when you first enabled the firewall, and when you disabled the firewall it continued to not work?
a. if so, and someone else might know this better than I, is there a way in add/remove programs/windows components to totally remove the personal firewall in XP. (I hate xp with a passion because it serves no valid purpose on corporate networks)
4. Have you done a fresh reinstall of the OS?
a- Points to earlier question.
"A fresh install means just that. It does not mean to install the os over the current system. It entails starting from scratch, formatting the drive and installing. This 'requires' that you make sure that all of your data is backed up and that you have install disks for any programs that you have. Preparing your drive for reinstall is somewhat of an art form, you need to know where to look to get all of your data, ie local e-mail."
5. I'm just curious, someone mentioned wins. From what I can tell, wins should not be a part of this equation. If at the command prompt you type in ipconfig /all , it will tell you all of your settings for your adapters.
a. What did you manually set in your tcp/ip properties?
6. NetBios over tcp/ip, must also be enabled. Set it back. Also netbt service helper for tcp/ip must also be started.
by shanghai sam
Ok, here we go. As far as your comment goes you have the timeline correct. The problem started a couple of weeks into February. I hadn't done anything recently that I can relate to causing the problem. I did the enabling/disabling of the firewall long before the problem started, I was just curios and turned it on, then turned it off the same day. I did a fresh intall of WinXP in December and haven't done any sort of reinstall or clean install since. I checked the wins in the TCP/IP properties and it didn't have anything listed under it. When I typed ipconfig /all in the command prompt it said "WINS proxy enabled: no". Farther down it had a listing for the primary and secondary wins servers and both had the same ip listed. I haven't changed anything in the TCP/IP properties except when someone suggested something, but then I changed it back to the default. The NetBIOS setting was set to Default but I changed it to enabled.
I checked the services and the RPC and RPC locatorwere started/automatic and manual respectively. I guess the "netbt service helper for tcp/ip" is "TCP/IP NetBIOS Helper", it was started and set to automatic. The Client for Microsoft Networks is using the Windows Locator.
I also tried the netstat suggestion and emailed you the file. I also posted a comment with a summarized version of the file for anyone else that wants to see it. Thanks for the troubleshooting help.
by estvb
by estvb
(see answer 61) The only changes I made were removing some repetition and removing some spacing so that I could fit everything into one comment. There were six repetitions of the first set and two of the second. After starting recording netstat I went to outlook and tried the Check Name first with ?minermail.umr.edu? as the exchange server and then with ?umr-mail5?.
Active Connections
Proto Local Address Foreign Address State
TCP ea:epmap ea:0 LISTENING
TCP ea:microsoft-ds ea:0 LISTENING
TCP ea:1025 ea:0 LISTENING
TCP ea:1027 ea:0 LISTENING
TCP ea:5000 ea:0 LISTENING
TCP ea:1035 ea:0 LISTENING
TCP ea:netbios-ssn ea:0 LISTENING
UDP ea:microsoft-ds *:*
UDP ea:isakmp *:*
UDP ea:ntp *:*
UDP ea:1045 *:*
UDP ea:1900 *:*
UDP ea:ntp *:*
UDP ea:netbios-ns *:*
UDP ea:netbios-dgm *:*
UDP ea:1900 *:*
Active Connections
Proto Local Address Foreign Address State
TCP ea:epmap ea:0 LISTENING
TCP ea:microsoft-ds ea:0 LISTENING
TCP ea:1025 ea:0 LISTENING
TCP ea:1027 ea:0 LISTENING
TCP ea:5000 ea:0 LISTENING
TCP ea:1035 ea:0 LISTENING
TCP ea:netbios-ssn ea:0 LISTENING
TCP ea:1223 umr-mail5.umr.edu:microsoft-ds TIME_WAIT
TCP ea:1226 umr-mail5.umr.edu:microsoft-ds TIME_WAIT
TCP ea:1228 umr-mail5.umr.edu:microsoft-ds TIME_WAIT
UDP ea:microsoft-ds *:*
UDP ea:isakmp *:*
UDP ea:ntp *:*
UDP ea:1045 *:*
UDP ea:1900 *:*
UDP ea:ntp *:*
UDP ea:netbios-ns *:*
UDP ea:netbios-dgm *:*
UDP ea:1900 *:*
by lordinfidel
Ask your IT dept if your network uses employs wins servers or if it just uses dns.
I say this because you said that wins was enabled to no, but you had ip's in the primary & secondary wins servers.
Also.... Do you know if you have a static IP or if you get your settings via dhcp?
If it's dhcp and there is no wins, in your network adapter properties (tcp/ip properties), there should be absolutely no entries in there. No static dns server entries, no static gateways, no extra IP's, no wins server address'.
If it is supposed to be pure dhcp, then to be on the safe side, open a command prompt (your starting to like the command prompt aren't you, I live for the command line) type in ipconfig /release_all (this releases all dhcp leases bound to any dhcp enabled adapters)
Normally I would just say renew, but in this case reboot. When it comes back up open the command prompt and check the config again (ipconfig /all).
My purpose for saying the above, I want to get your adapter into a very basic default state. There have been a lot of creative answers, but connecting to exchange is not brain surgery. It is generally straight forward. So straight forward that you can walk up to anty machine on the network and connect just by changing the exchange mailbox properties. Regardless of who your logged in as.
by lordinfidel
Just so the general public can follow along with our off-line conversation.
His results of netstat shows that he was trying to go to the fqdn of the mail server. This associated into a time-wait state and then gave the could not resolve name.When he enters in just the netbios name of the server, he does get the u/d/p box. Which is what we want. I've instructed him to continue to use only the netbios name.
The next step is to have him try to resolve one of his friends accounts usinghis friends account information.
If he can open his friends mailbox, then he will go into the tools/services/advanced and add his name to the mailbox and see if it resolves.
If it does, then he can contact tech support and have them add his friends name into the permissions of his mailbox as owner. Once in, he then needs to export his mail into a pst.
The reverse all of the changes, and put his name in as the primary. If that still does not work, then Before having tech support blow away your mailbox, go and get rid off ALL of your profiles. But don't do it from the outlook icon.
Go into your control panel and look for the mail icon. Get rid of your profiles from there.
Then go back to your outlook icon and see if there are any profiles there. If there are, get rid of them.
Then close out. Reboot. then check to see if your profiles are still there (in both locations)
If they are not, then in outlook icon, add the profile again, add exchange and configure it.
If that still does not work, get rid of the profiles again. Remove Outlook totally. Reboot, reinstall outlook and try it again.
If that still fails, then it's time for tech support to blow away the mailbox and recreate it.
by estvb
by estvb
Well my campus helpdesk seems to have exhausted all of their troubleshooting options and closed my question. They told me to reinstall and possibly seek outside help.
Luckily I've already done that (the outside help anyway) and posted my question here. Thanks for all the help!
by estvb
by estvb
This discussion is closed to new replies.
Sort by Trending