Hi,
on a Windows 8.1 Home 64bit system with Heimdal, OpenAFS 1.7.28 and Network
Identity Manager 2.0 installed, I don't get tickets/tokens at logon. Instead,
I need to type the kerberos password into NIM again to obtain credentials.
The same setup works fine on a Win7 Enterprise 64bit. Indeed,
On 1/12/2014 11:04 AM, Dirk Heinrichs wrote:
Hi,
on a Windows 8.1 Home 64bit system with Heimdal, OpenAFS 1.7.28 and Network
Identity Manager 2.0 installed, I don't get tickets/tokens at logon. Instead,
I need to type the kerberos password into NIM again to obtain credentials.
The same
Am Sonntag 12 Januar 2014, 11:37:02 schrieb Jeffrey Altman:
If you are logging in with a domain account then NIM will use your
domain credentials to acquire an AFS token (if it can).
You're refering to the Win7 case, right? No, I don't use a domain account.
It's a local machine account, which
Hey folks. Odd problem. I have gone over many things, and I am stumped. I
am tempted to just destroy and rebuild my errant vlserver, but I'd like to
know what's going on and I know I am missing something :-)
I have three vlservers, one in each of my colos. Lets call them A
(10.33.10.43),
Wow. Just as you send it outyou find the problem. Always the way :-)
This turned out to be a subtle network problem. There was a change in the
cross colo VPN link by our provider, and while it didn't affect the
majority of our traffic, apparently -some- udp traffic was affected, due to
some
Oh FYI, when I said ' some udp traffic was affected', I didn't mean
blocked. I meant mangled. Some packets were being partially truncated, so
looking at the headers only didn't give me any data. This was very non
obvious, until I had a hint of the problem.
Best,
On Sun, Jan 12, 2014 at 4:17 PM,
The log reports:
Sun Jan 12 23:20:40 2014 ubik:server 10.33.10.43 still down
Therefore, 10.33.10.43 is either not receiving the messages from
10.38.10.7 or its replies are not being delivered.
Look again for a connectivity or firewall issue.
smime.p7s
Description: S/MIME Cryptographic
