Re: Outlook over internet RPC not working
- From: barretech@xxxxxxxxxxx
- Date: Mon, 30 Jun 2008 18:21:50 -0700 (PDT)
On Jun 30, 3:59 pm, "Dave Nickason [SBS MVP]"
<gwdib...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Have you tried creating a new mail profile for the user? It seems like
you've exhausted the connection issues by virtue of the fact that all the
settings between the two laptops match, and that all the connection points
between the laptops and the SBS are the same.
I've had bizarre wireless issues - for example, 802.1x authentication would
work from all but one laptop, and what fixed it was replacing the wireless
NIC. But, I've never had an issue related specifically to wireless where
you had a successful connection, but then a specific function failed over
that connection. I can't remember if you've said, but have you tried
connecting the laptop to a different (preferably wired) connection?
<barret...@xxxxxxxxxxx> wrote in message
news:95db893f-b040-40ca-991d-acc636f04351@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 28, 3:25 pm, "Dave Nickason [SBS MVP]"
<gwdib...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Try connecting some other way than the Verizon card. I had a nightmare a
few months ago where my boss's PC stopped connecting reliably using RPC,
and
the Verizon card ended up being the cause. Luckily, he noticed that he got
the expected results with RPC when connected over his home network.
In that case, it seemed like what was happening was that we couldn't get a
fast enough, consistently reliable connection. In troubleshooting with
Verizon, I discovered that the thing in their software that checks for
updates always reports that your software is current. I was actually a
number of versions behind.
So I would test to see if the problem is specific to the Verizon
connection.
Then if it is, you can either try dealing with their tech support, or go
to
the super secret Verizon software download site and see if you can
download
the current versionhttp://vzam.net/. I had major installation trouble
until I realized that my old version installed more than one application
with its single installer. I had to go into CP add/remove and uninstall
anything related to Verizon (2 or 3 apps), then install the new version,
at
which point it worked.
After you've installed the current software, do the "activate" thing from
one of the menus - it'll update the roaming table or whatever in the card
so
you get the best connection available.
<barret...@xxxxxxxxxxx> wrote in message
news:5cbc843f-9863-4375-a91a-ace613471393@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 26, 8:11 pm, David Thorpe <%firstna...@xxxxxxxxxxxxxxxx> wrote:
barret...@xxxxxxxxxxx wrote
innews:e89a9c1e-7db7-4220-bd71-615946ed08b0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:
Thanks Dave. The cert was already in that store, but I removed it (in
the IE tools) and then went to the OWA site to get it back, and chose
manually to install it into the store you suggested. No help.
The RPCDIAG shows Directory and Referral and Connecting and
connecting. Then eventually says Disconnected.
<snip>
Are the laptops using Basic Authentication or NTLM Authentcation?
--
David Thorpe
Tech Care Team
"In the sandwich world, bread is a given."
Basic it is. Every step in the SBS document was followed. There must
be some 3rd party something installed. Maybe the Verizon broadband
(cellular) software introduced a change to the standard set of XP TCP/
IP support or something... that's the only change I can think of.- Hide
quoted text -
- Show quoted text -
Sorry, I thought I mentioned that I was connecting both laptops with
"wi-fi". I am not connected with the Verizon card. I am connecting
with wireless via a Linksys Linux router on DSL. The other laptop
doesn't have the problem, this one does. The only difference is that
the troubled one has the Verizon software on it.- Hide quoted text -
- Show quoted text -
I just found a bunch of these (following message) on the server. I
would bet that the user is typing his password in properly.
The events reoccur every 10 minutes. That's the interval to which we
have Outlook set to do a "Send and Receive".
Maybe there is a group policy setting that is causing the password to
get mangled or otherwise not be accepted? Like Kerberos or digital
signing or something? What can I try to turn off to make this work?
Logon Failure:
Reason: Unknown user name or bad password
User Name: molson
Domain: SPSERVER
Logon Type: 8
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: SPSERVER
Caller User Name: NETWORK SERVICE
Caller Domain: NT AUTHORITY
Caller Logon ID: (0x0,0x3E4)
Caller Process ID: 4440
Transited Services: -
Source Network Address: 75.9.17.206
Source Port: 3953
.
- Follow-Ups:
- Re: Outlook over internet RPC not working
- From: Dave Nickason [SBS MVP]
- Re: Outlook over internet RPC not working
- Prev by Date: Re: Backup for Dell RD1000?
- Next by Date: RE: Faulting application mtifilter.exe, version 5.4.4.108, faultin
- Previous by thread: Re: server crashed - recovering from backup
- Next by thread: Re: Outlook over internet RPC not working
- Index(es):
Relevant Pages
|
Loading
