yes it is

"neo [mvp outlook]" wrote:

Are you sure the HTTP virtual server is setup to accept basic
authentication?

"jmiller" wrote in message
...
yes I am entering my credentials as domain\userid then password.
authentication is basic. when you enter your credentials to log on it
tries
and keeps bouncing back to password. owa works and i can log on to the
server
using https I just can't connect with http over rpc... the main thing we
are
trying to use since most machines are outside of the lan

"neo [mvp outlook]" wrote:

Are you entering your credentials as domain\userid then password?

When you setup the rpc/https connection, did set the authenticate to
basic
or ntlm? (basic is usually the best bet as some firewalls don't handle
ntlm
very well.)

"jmiller" wrote in message
...
I have no certificate problems and can get to owa and establish an ssl
connection but every time I try to use rpc after setting up a profile,
I
can't establish a connection. I enter my password and it keeps going
back
to
the password screen. running sbs 03 with sp1

Assuming this is a single server setup, did you specify on the RPC/HTTP tab
that this is a back-end server? (This tab is in Exchange System Manager.
Just bring up the properties on the server object.)

/neo

PS - This tab is introduced in Exchange 2003 SP1. Not familiar with SBS
2003 SP1 to know if it includes SP1 for Exchange 2003.

"jmiller" wrote in message
...
yes it is

"neo [mvp outlook]" wrote:

Are you sure the HTTP virtual server is setup to accept basic
authentication?

"jmiller" wrote in message
...
yes I am entering my credentials as domain\userid then password.
authentication is basic. when you enter your credentials to log on it
tries
and keeps bouncing back to password. owa works and i can log on to the
server
using https I just can't connect with http over rpc... the main thing
we
are
trying to use since most machines are outside of the lan

"neo [mvp outlook]" wrote:

Are you entering your credentials as domain\userid then password?

When you setup the rpc/https connection, did set the authenticate to
basic
or ntlm? (basic is usually the best bet as some firewalls don't handle
ntlm
very well.)

"jmiller" wrote in message
...
I have no certificate problems and can get to owa and establish an
ssl
connection but every time I try to use rpc after setting up a
profile,
I
can't establish a connection. I enter my password and it keeps
going
back
to
the password screen. running sbs 03 with sp1

it is a single server setup... and on the server prop. tab it is set to not
part of an rpc topology... I tried to set it to back end server and I get a
error

"neo [mvp outlook]" wrote:

Assuming this is a single server setup, did you specify on the RPC/HTTP tab
that this is a back-end server? (This tab is in Exchange System Manager.
Just bring up the properties on the server object.)

/neo

PS - This tab is introduced in Exchange 2003 SP1. Not familiar with SBS
2003 SP1 to know if it includes SP1 for Exchange 2003.

"jmiller" wrote in message
...
yes it is

"neo [mvp outlook]" wrote:

Are you sure the HTTP virtual server is setup to accept basic
authentication?

"jmiller" wrote in message
...
yes I am entering my credentials as domain\userid then password.
authentication is basic. when you enter your credentials to log on it
tries
and keeps bouncing back to password. owa works and i can log on to the
server
using https I just can't connect with http over rpc... the main thing
we
are
trying to use since most machines are outside of the lan

"neo [mvp outlook]" wrote:

Are you entering your credentials as domain\userid then password?

When you setup the rpc/https connection, did set the authenticate to
basic
or ntlm? (basic is usually the best bet as some firewalls don't handle
ntlm
very well.)

"jmiller" wrote in message
...
I have no certificate problems and can get to owa and establish an
ssl
connection but every time I try to use rpc after setting up a
profile,
I
can't establish a connection. I enter my password and it keeps
going
back
to
the password screen. running sbs 03 with sp1

If its the dialog I'm thinking of, its normal because it serves as a
reminder to those setting up a front end/back end solution. RPC/HTTPs works
fine in single server solutions. (and yes, my single server here at home is
set as a back end server.)


"jmiller" wrote in message
...
it is a single server setup... and on the server prop. tab it is set to
not
part of an rpc topology... I tried to set it to back end server and I get
a
error

"neo [mvp outlook]" wrote:

Assuming this is a single server setup, did you specify on the RPC/HTTP
tab
that this is a back-end server? (This tab is in Exchange System Manager.
Just bring up the properties on the server object.)

/neo

PS - This tab is introduced in Exchange 2003 SP1. Not familiar with SBS
2003 SP1 to know if it includes SP1 for Exchange 2003.

"jmiller" wrote in message
...
yes it is

"neo [mvp outlook]" wrote:

Are you sure the HTTP virtual server is setup to accept basic
authentication?

"jmiller" wrote in message
...
yes I am entering my credentials as domain\userid then password.
authentication is basic. when you enter your credentials to log on
it
tries
and keeps bouncing back to password. owa works and i can log on to
the
server
using https I just can't connect with http over rpc... the main
thing
we
are
trying to use since most machines are outside of the lan

"neo [mvp outlook]" wrote:

Are you entering your credentials as domain\userid then password?

When you setup the rpc/https connection, did set the authenticate
to
basic
or ntlm? (basic is usually the best bet as some firewalls don't
handle
ntlm
very well.)

"jmiller" wrote in message
...
I have no certificate problems and can get to owa and establish an
ssl
connection but every time I try to use rpc after setting up a
profile,
I
can't establish a connection. I enter my password and it keeps
going
back
to
the password screen. running sbs 03 with sp1

I changed it to back end server and tried it again.... same situation it pops
back to the log in for a password. does the service need to be stopped and
restarted? I checked the log and it doesn't show anything that Ive tried to
log in and fail

"neo [mvp outlook]" wrote:

If its the dialog I'm thinking of, its normal because it serves as a
reminder to those setting up a front end/back end solution. RPC/HTTPs works
fine in single server solutions. (and yes, my single server here at home is
set as a back end server.)


"jmiller" wrote in message
...
it is a single server setup... and on the server prop. tab it is set to
not
part of an rpc topology... I tried to set it to back end server and I get
a
error

"neo [mvp outlook]" wrote:

Assuming this is a single server setup, did you specify on the RPC/HTTP
tab
that this is a back-end server? (This tab is in Exchange System Manager.
Just bring up the properties on the server object.)

/neo

PS - This tab is introduced in Exchange 2003 SP1. Not familiar with SBS
2003 SP1 to know if it includes SP1 for Exchange 2003.

"jmiller" wrote in message
...
yes it is

"neo [mvp outlook]" wrote:

Are you sure the HTTP virtual server is setup to accept basic
authentication?

"jmiller" wrote in message
...
yes I am entering my credentials as domain\userid then password.
authentication is basic. when you enter your credentials to log on
it
tries
and keeps bouncing back to password. owa works and i can log on to
the
server
using https I just can't connect with http over rpc... the main
thing
we
are
trying to use since most machines are outside of the lan

"neo [mvp outlook]" wrote:

Are you entering your credentials as domain\userid then password?

When you setup the rpc/https connection, did set the authenticate
to
basic
or ntlm? (basic is usually the best bet as some firewalls don't
handle
ntlm
very well.)

"jmiller" wrote in message
...
I have no certificate problems and can get to owa and establish an
ssl
connection but every time I try to use rpc after setting up a
profile,
I
can't establish a connection. I enter my password and it keeps
going
back
to
the password screen. running sbs 03 with sp1

Yes, but before you do this, please double check two registry key values on
the exchange server. Open regedit and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy


Enabled should be set to 1

ValidPorts should show the netbios and fully qualified domain name for you
exchange server. Port numbers would be 6001-6002 and 6004. To explain
better, if mail server name is MSEXCH in the CONTOSO.COM domain then the
entry would look like:

msexch:6001-6002;msexch.contoso.com:6001-6002;msexch:6004;msexch.contoso.com:6004


"jmiller" wrote in message
news
I changed it to back end server and tried it again.... same situation it
pops
back to the log in for a password. does the service need to be stopped
and
restarted? I checked the log and it doesn't show anything that Ive tried
to
log in and fail

"neo [mvp outlook]" wrote:

If its the dialog I'm thinking of, its normal because it serves as a
reminder to those setting up a front end/back end solution. RPC/HTTPs
works
fine in single server solutions. (and yes, my single server here at home
is
set as a back end server.)


"jmiller" wrote in message
...
it is a single server setup... and on the server prop. tab it is set to
not
part of an rpc topology... I tried to set it to back end server and I
get
a
error

"neo [mvp outlook]" wrote:

Assuming this is a single server setup, did you specify on the
RPC/HTTP
tab
that this is a back-end server? (This tab is in Exchange System
Manager.
Just bring up the properties on the server object.)

/neo

PS - This tab is introduced in Exchange 2003 SP1. Not familiar with
SBS
2003 SP1 to know if it includes SP1 for Exchange 2003.

"jmiller" wrote in message
...
yes it is

"neo [mvp outlook]" wrote:

Are you sure the HTTP virtual server is setup to accept basic
authentication?

"jmiller" wrote in message
...
yes I am entering my credentials as domain\userid then password.
authentication is basic. when you enter your credentials to log
on
it
tries
and keeps bouncing back to password. owa works and i can log on
to
the
server
using https I just can't connect with http over rpc... the main
thing
we
are
trying to use since most machines are outside of the lan

"neo [mvp outlook]" wrote:

Are you entering your credentials as domain\userid then
password?

When you setup the rpc/https connection, did set the
authenticate
to
basic
or ntlm? (basic is usually the best bet as some firewalls don't
handle
ntlm
very well.)

"jmiller" wrote in message
...
I have no certificate problems and can get to owa and establish
an
ssl
connection but every time I try to use rpc after setting up a
profile,
I
can't establish a connection. I enter my password and it
keeps
going
back
to
the password screen. running sbs 03 with sp1