Exchange 2003 & Outlook 2003 connection problem

[maxster]

I have an existing Exchange 2003 server. Today a new batch of XP Pro machines turned up so we confgired Outlook 2003 to connect to our mail server. I can ping the mail server and DNS resolves the name OK.

When I try to add a new E-mail Account i put in the mail server and existing user name but get the following error "the name could not be resolved. The action could not be completed". I have search the web some people suggest removing the TCP/IP stack but this option is not available.

Any ideas.....?

 

[Marcs41]

When you create a new users, it takes some time to get settled.
You can 'force' it a little with the recipient update server, or, if you really are in a hurry, restart some services.
Then, you send an e-mail to that new user.
Only then, you try your Outlook connection.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC![/sub]

Have a look at the shop @

http://www.cafepress.com/tektips

!

 

[exchangesolution]

If they are "existing" users and you still have problem and this is happening on XP ....then try this
disable firewall on XP
or ADD outlook to the allowed applications
or reinstall ur nic cards driver again...
or uncheck the little box in your tcpip properties page next to TCPIP protocal and click OK your way out.....once finished check the box again and click your way out

if they are new users then MARCS41 is pointing you to the right direction...

 

[maxster]

Thanks 'exchangesolution' I have disabled the firewall, I removed & installed the NIC and updated the driver. I then unchecked TCP/IP and then enabled it but that made no difference.

I can browse the internet OK across the LAN. The users are all existing AD & exchange users who can currently access mail from their old machines; all I doing is replacing there old machines.

Any further thoughts??

 

[Marcs41]

Some things you can check:

DNS
Are the new PC's in the correct Domain or Workgroup?
Do they have the correct rights?
Do the passwords match?
Did you try connecting with IP instead of servername.
Can you connect if you login as Administrator?

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.
Free Tip: The F1 Key does NOT destroy your PC![/sub]

Have a look at the shop @

http://www.cafepress.com/tektips

!

 

[maxster]

Hi Marcs41,

The answer your questions:

All the machines are in the same Domain.
They have the correct rights as they are all current users.
The passwords match because I can log them onto the Domain and authenticate them.
I tried the IP address of the exch server and that had the same failure.
I logged on as the Administrator but the same issue.

This is just weird...

 

[exchangesolution]

try this article...check your rpc binding order...

also make sure chache mod is not enabled when you first configure outlook 2003...

welll since we have no clue...also try enabling netbios oevr tcpip in your outlook clients tcpip settings and then
try netbios name of your exchange server to see if you get lucky...

 

[exchangesolution]

http://support.microsoft.com/default.aspx?scid=kb;en-us;235683

sorry i forgot to post the article...

 

[maxster]

Thanks for your suggestions.

I tried that but still do joy. I actually compared the registery settings from another XP machines regarding RPC bindings and they are identicle. In frustration I rebuilt the machine over the weekend so now it is just a fresh build of XP SP2 and Outlook 2003; still no good.

I am not sure that the NIC (embedded Broadspeed) has anything to do with it although I can browse our network and the internet.

It is really strange; any further thoughts???

 

[maxster]

Do you think that this might be a port/s being blocked on the XP machine preventing it from either connecting or authenticating the user?

 

[exchangesolution]

Well it could be...to test install a second nic card...disable the onboard nic and try outlook...if successfull then you know what to do....if you fail again then it is most likely xp2 firewall
....

 

[DColcl]

Does Exchange 2k3 restrict new clients if Licenses have been exceeded? Or does it allow new connections, but logs License error messages in the Event Viewer like it did in older versions?

Just a thought.

 

[maxster]

There are no new clients; I am using existing mailboxes. So mt current mailbox is the one I am testing on. I have another laptop which I am teting with connecting to my mail box OK. The new XP machine is trying to connect to this mailbox as well, not at the same time though.

I have installed a new NIC card but I still have the same problem. Just to let you know that Dell are not willing to give me any assistance on this issue; "we only support hardware was the response".

 

[DColcl]

And there is nothing stated in the Event Logs about the failure to connect? I would think that at least the Application log would log any issues with Outlook connection failures. <shrug>.

 

[maxster]

I have cleared both the Application & System logs and tried again.

Nothing has been written the either of these??

 

[DColcl]

About 2 weeks ago I had the very same problem with a Sony Laptop not connecting. I returned that unit and got another of the SAME model; and then bought a 3rd Sony (same model) for another user. All 3 of these VERY SAME models didn't allow me to connect to Exchange 2k3 using Outlook 2k3.
My Sony laptop, as well as all other laptops, were connecting fine. So, I returned all 3 of these Sony laptops and changed them for another. All 3 new laptops (different make and/or models) work perfectly.
Both Sony and MS (yes, I dished out the $$ for MS Tech support -- but got it back) were at a loss.

Can you change out your new computers? Maybe you are coming accross the same glitch that I did? I even reformated my laptops, too.

dc

 

[exchangesolution]

DColcl i was never aware of this problem with outlook and exchange...nice of you to post THE SOLUTION...but it would be nice to know why??? if it was up to me i will do this..
reformat one PC...three partition...
1- on the first partition install win2000 with outlook 2003
2-on second partion install XP and outlook 2003 from a diffrent CD....
3-on a third partition install XP and outlook from the CD that came from DELL and is having problem...
depending which combination works one MAY BE able to figure out the solution to this problem...
Maxter sorry could not give you a working solution...if nothing worked then you should take DCcolcl solution since it has been tested with a poitive result...
All you folks take care and good luck...

 

[DColcl]

first, I dont know of a "General" problem with Outlook and exchange. Please read my post and note that the problem is with a specific Sony model laptop, MS Outlook 2k3 connecting to Exhcnage 2k. and that there were a total of 3 different laptop models and 3 seperate software packages and TWO different networks.

yeah, that would be a great solution, Exhcange, for someone who had that kind of time. Unfortunatly at the time, I did not have the time/patience to spend countless time troublshoooting the issues. If Tier 3 Sony and MS can't figure it out on 3 confernce calls totalling over 20 hours, then I, as a consultant, I pack my bags in, return the defective units before return policy warrenty runs out and get something to the client that works...quick!

To that effect, if I can post the information on what model Sony I was using and YOU can spend the time troubleshooting and finding out why. Again, I dont have the luxury of another 20+ hours on something that can be easily fixed by a unit that works.

Am I curious to find out why this config didn't work? sure, to an extent.

As to the options that I peformed
1. I reformated the laptop and started over
2. I reformated the Laptop and installed XP Pro from antoher CD. We installed the BIOS updates & drivers from the Sony site. once without Sony Tech. Again with Sony tech.
3. I reformated the Laptop from CD XP and JUST installed outlook 2k3.

4. involved MS with confernece all with Sony.

At this point, after 3 differnt calls, my time was running out. I needed to get a solution that works. For now, I will have to settle on reading why this configution failed from those who have the time and energy to resolve the issues.

Dan

 

[exchangesolution]

http://windowsxp.mvps.org/winsock.htm

read this carefully...and try the command
netsh winsock reset....and see if that would help solve ur problem...

 

[DColcl]

Nope, it didnt work. (