Computing.Net > Forums > Windows Server 2003 > Cannot connect to exchange server

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Cannot connect to exchange server

Reply to Message Icon

Name: saluk2007
Date: April 21, 2006 at 05:57:20 Pacific
OS: server\exchange 2003
CPU/Ram: 1ghz\1gb
Product: amari
Comment:

Hello,

All users who are dialling up or connecting via broadband cannot connect to the exchange server using outlook RPC. Not using VPN. Checked RPC services are running and Restarted exchange 2003 server. What services are dependable on RPC services. Any one have any more ideas.


Sal



Sponsored Link
Ads by Google

Response Number 1
Name: heropsycho2177
Date: April 21, 2006 at 07:49:25 Pacific
Reply:

You're allowing Outlook users to connect directly via RPC through the internet?! Holy crap, dude!!! DON'T DO THAT!!!

"Milk was a bad choice!"


0

Response Number 2
Name: saluk2007
Date: April 21, 2006 at 07:58:53 Pacific
Reply:

Well its not up to me? Why??


0

Response Number 3
Name: Dirty_Sanchez
Date: April 21, 2006 at 09:00:50 Pacific
Reply:

Why? How long of a list do you want?


0

Response Number 4
Name: saluk2007
Date: April 21, 2006 at 09:04:39 Pacific
Reply:

as long as they come, i know its not very secure and we are looking to get VPN soon as soon as the budget comes through, but back to the original question, any ideas on that.


0

Response Number 5
Name: Dirty_Sanchez
Date: April 21, 2006 at 10:39:43 Pacific
Reply:

Security is the main reason but, there are tons of security issues that are associated with it. Why not just setup OWA and let your users access that instead of connecting directly to the server as that is just flat out a horrible idea. I gotta be honest, I have never even heard of anyone considering setting it up the way you are. You are just begging for someone to piggy back in on one of your users and gaining complete access to not only your exchange server (where they could spoof, mail bomb, redirect, etc)but your entire NW. Do a little research on OWA (Outloo Web Access) and maybe a SSL_VPN setup.


0

Related Posts

See More



Response Number 6
Name: heropsycho2177
Date: April 21, 2006 at 17:45:34 Pacific
Reply:

"I have never even heard of anyone considering setting it up the way you are."

I have, and it doesn't take long before they find out how much of an incredibly bad idea it is. :-)

"Milk was a bad choice!"


0

Response Number 7
Name: Dirty_Sanchez
Date: April 22, 2006 at 09:49:37 Pacific
Reply:

So hero, how long before they either got hacked OR the users FUBAR'd the server by 'playing with it'?


0

Response Number 8
Name: heropsycho2177
Date: April 22, 2006 at 10:32:21 Pacific
Reply:

How long until?!

I think it's been hacked already.

Please help survivors of Hurricane Katrina!

www.redcross.org


0

Response Number 9
Name: Dirty_Sanchez
Date: April 22, 2006 at 11:12:37 Pacific
Reply:

Geeze, I guess I shouldnt be surprised by stuff like that given what i've seen but, d@mn, it still does. I just dont get it happening in a business when it isnt that hard to screen people and see if they know they are doing.


0

Response Number 10
Name: heropsycho2177
Date: April 22, 2006 at 11:55:26 Pacific
Reply:

BTW, the reason broadband users can't connect is probably because their ISP's are blocking RPC traffic, and for good reason!

Either that or his firewall is blocking it...which I hope is true...but if that's the case, this guy shouldn't be the one asking these questions since he doesn't know his own configuration.

Bottom line is outside clients should not be allowed to use Outlook to connect to the exchange server unless:

A. they are using VPN.
B. They're using RPC over HTTP.

Please help survivors of Hurricane Katrina!

www.redcross.org


0

Response Number 11
Name: heropsycho2177
Date: April 22, 2006 at 12:00:42 Pacific
Reply:

Correction...Use Outlook as a MAPI client...Pop3 or IMAP4 would be acceptable.

Please help survivors of Hurricane Katrina!

www.redcross.org


0

Response Number 12
Name: saluk2007
Date: April 24, 2006 at 02:07:29 Pacific
Reply:

Ok thanks for all your help appreciate everything that you have suggested. It turns out that the rpcproxy.dll has expired. Thanks for all your help once again.


0

Response Number 13
Name: Droz
Date: April 27, 2006 at 14:56:40 Pacific
Reply:

You sure he didn't mean RPC over HTTP? Not that that is neccesarily a good idea either....


0

Response Number 14
Name: heropsycho2177
Date: April 27, 2006 at 16:07:11 Pacific
Reply:

Why wouldn't it be? It's more secure than IMAP4 or POP3.

Did he mean that? Well, he apparently didn't know if he was using it or not, which implies he used default settings...which means he wasn't using it.

Please help survivors of Hurricane Katrina!

www.redcross.org


0

Response Number 15
Name: saluk2007
Date: April 28, 2006 at 07:42:38 Pacific
Reply:

Hi,

Sorry i was panicing the before because people were on my back, im not much experienced only 2 years and am currentley studying to get some MCPs. What i meant to say is that we are using RPC over HTTP. The CA had expired took me a bit of time to find the solution on the internet but evetually i did, renewed the CA and outlook connected as straight as i clicked ok.


Regards

Sal


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Cannot connect to exchange server

Cannot connect to Exchange Server www.computing.net/answers/windows-2003/cannot-connect-to-exchange-server/4955.html

Cannot Connect to Exchange on new P www.computing.net/answers/windows-2003/cannot-connect-to-exchange-on-new-p/8731.html

Cannot connect to Win2k3 server www.computing.net/answers/windows-2003/cannot-connect-to-win2k3-server/6677.html