Need help troubleshooting small Exchange server

[TerryMathews]

I've got an Exchange server working for my cell phone and Outlook support, has been working great for almost a month now, AirSync with the smartphone and Outlook as well. The server is my workstation.

I'm trying to get the girlfriend's computer working at her house. I've tried just connecting Outlook to the Exchange over the internet, and I've tried setting it up as an RPC-HTTP connection.

I just can't get it to authenticate. Anyone have any walkthroughs, or am I going to have to switch over to 4smartphones.com?

FWIW, I'd be willing to do a VPN connection with her, but I've never been able to get that to work. I think sitting behind my NAT router (D-Link DI-614+) breaks it.

 

[coolVariable]

which phone are you getting?
The Siemens sx66?

 

[TerryMathews]

Originally posted by: coolVariable
which phone are you getting?
The Siemens sx66?

HTC Wizard/QTEK 9100/iMate KJam. SX66 (Or HTC Blue Angel) is a WM2003SE phone.

 

[coolVariable]

well. great. and which one are you getting Mr. I-Am-so-smart?????



How about the unsupported WM5 ROM update????

 

[TerryMathews]

Originally posted by: coolVariable
well. great. and which one are you getting Mr. I-Am-so-smart?????



How about the unsupported WM5 ROM update????

Probably the iMate KJam.

And I don't want the SX66 since I want a larger keyboard. The HTC Wizard/QTEK 9100/iMate KJam has a keyboard that is the size of the device that slides out the side and puts the machine into a landscape orientation.

 

[coolVariable]

Any idea whether Cingular is going to carry that phone at some point (or the HP hw6700 which I find very promising)?

I too am looking to get a Pocket PC phone for Cingular or T-mobile sometime between now and Christmas ...

 

[Ol Bob]

I think that you should order the evaluation kit of server 2003 sbs from microsoft. It's free but for shipping charges.I just got one in order to try exchange myself, but found that it would not run on my home network as I have no domain, just a workgroup.

 

[TerryMathews]

Originally posted by: coolVariable
Any idea whether Cingular is going to carry that phone at some point (or the HP hw6700 which I find very promising)?

I too am looking to get a Pocket PC phone for Cingular or T-mobile sometime between now and Christmas ...

Supposedly, they will on the 26th. There's a future phones spreadsheet leaked on the internet that mentions the two new HTC handhelds (A smartphone and a pocket PC).

Cing is going to carry the 6515, which IMO is a waste. I'm going with the KJam, even if I have to buy it outright (It's a quad-band phone with EDGE support, so it'll work even if you import it).

 

[coolVariable]

Thanks for the info. I guess I will wait a little longer ...
The iMate K-Jam looks cool - I am a little weary though about its thickness ...

The s66/PDA2k with Windows Mobile 2005 would be killer!

 

[coolVariable]

Actually looks like one of the phones to be released soon will be the Samsung SGH-D307 (with WM2003SE)

 

[TerryMathews]

In case anyone was wondering, I got Exchange set up and running in anticipation of my switchover. Going to be going Cingular, from Nextel, on 11/27.

As much as I dislike certain Microsoft products, I have to admit that Exchange is a very easy to use program, as e-mail servers go. I think that anyone with a background in basic e-mail theory (FQDNs, SMTP for delivery, ports, etc) and user management in 2000 or later including XP Pro would just be able to sit down at an Exchange 2003 server and do 90% of the tasks you need to do.

That said, it's been hell-on-Earth migrating e-mail from DreamHost into my new Exchange server. Why hasn't Microsoft written a good connector to go from IMAP to Exchange? I mean, c'mon porting fetchmail and putting a wrapper around it would get you 90% there and it'd be better than the commercial connector alternatives that are out now.

And, just incase anyone duplicates this endeavor and runs into the same problem I did: On a fresh Server 2003 installation, you need to edit a registry entry after Active Directory is configured before proceeding with ForestPrep. It's not mentioned in the Exchange installation notes, but it fixes the installation error I kept running into.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed needs to be set to 1. Default is 0. Took me two installation and over an hour to run it down.

 

[TerryMathews]

Need help troubleshooting bump.