date:20120219

Moxie Marlinspike's CloudCracker Aims For Speedier, Cheaper Password Cracking

2012-02-19 Thread Kurt Buff

http://www.forbes.com/sites/andygreenberg/2012/02/14/moxie-marlinspikes-cloudcracker-aims-for-speedier-cheaper-password-cracking/

By Andy Greenberg
Forbes Staff
2/14/2012

A little over two years ago, well-known hacker and security researcher
Moxie Marlinspike launched an online service that, for a fee of $17,
could crack most wifi networks’ password in less than hour. Apparently
that wasn’t fast enough.

On Tuesday, Marlinspike launched CloudCracker, an upgrade to the
Web-based penetration testing service he formerly called WPACracker,
with a major upgrade to the speed and versatility of that
password-breaking service. For $17, CloudCracker can now break into a
standard WPA-PSK wireless networks by burning through dictionaries of
possible passwords at about twice the speed of WPACracker, exhausting
600 million words in one hour instead of 260 million in the previous
version .

For networks with especially obscure passwords, the tool can now use
dictionaries as big as 4.8 billion words in the same amount of time
for the price of $136. And instead of only focusing on cracking wifi
networks, the tool can now break passwords protected by Microsoft‘s
Windows LAN Manager and NT LAN Manager hashing systems too, for a
price of fifty cents for every password. Marlinspike says he hopes to
add more password formats in the future.

“We’re really trying to push the envelope in terms of password
cracking,” says Marlinspike, a well known security researcher who now
works for Twitter but built CloudCracker as an independent project.
“Basically you get more dictionaries for your dollar, about twice the
cracking power for the same price.”

[...]

__
Certified Ethical Hacker and CISSP training with Expanding Security gives
the best training and support.
Get a free live class invite weekly. Best program, best price.
www.ExpandingSecurity.com/PainPill

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: dns issue with browser (OS X)

2012-02-19 Thread James Hill

This sounds like the most likely cause.

Or even some type of Malware.

*gasp... did he just say that!?

-Original Message-
From: Matthew W. Ross [mailto:mr...@ephrataschools.org] 
Sent: Saturday, 18 February 2012 3:09 AM
To: NT System Admin Issues
Subject: Re: dns issue with browser (OS X)

Doublecheck the browser/OS proxy settings.


--Matt Ross
Ephrata School District


- Original Message -
From: Jimmy Tran
[mailto:jt...@teachtci.com]
To: NT System Admin Issues
[mailto:ntsysadmin@lyris.sunbelt-software.com]
Sent: Fri, 17 Feb 2012
08:52:56 -0800
Subject: dns issue with browser (OS X)


> Hi All,
> 
>  
> 
> I have one specific user using a Mac who cannot resolve DNS properly 
> in Firefox or Safari on OS X 10.6.8.  They can ping by hostnames just
fine.
> They can get to any website by IP just fine but not by hostname.  Any 
> ideas?  I'm stumped and Google hasn't been very helpful this morning.
> 
>  
> 
> Thanks,
> 
>  
> 
> Jimmy
> 
>  
> 
> 
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
>   ~
> 
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: So...we broke SMS and Lice Communcations Server 2005

2012-02-19 Thread David Lum

I'm no longer getting backend database errors, but I still get EventID 30710 
errors

Looking at the LCS management console, it tells me we have no certificates as 
default certificate settings - does that matter if we're no federated and not 
accessing this server from anywhere except our own network? Sadly I have no 
idea what this console indicated when everything was working...

At this point we're rolling the old server back and hopefully that clears 
everything up.

Dave

-Original Message-
From: Steve Kradel [mailto:skra...@zetetic.net] 
Sent: Sunday, February 19, 2012 5:25 PM
To: NT System Admin Issues
Subject: Re: So...we broke SMS and Lice Communcations Server 2005

This looks possibly relevant to your issue:
  Sadly none of the events in this 
thread hint at the real problem, such as a permissions problem, failure to 
resolve a server name, or wonky connection string.
However, this detail ought to show up in the SQL Server logs, and possibly also 
in the SQL server machine's OS event logs.  Most likely the LCS / SMS AD 
accounts or groups aren't mapped to server logins...
your DBA should be able to check the database users and verify they have valid 
logins.

In SQL Server parlance, a "login" is a server-level object mapped to a Windows 
principal or SQL Server username+password.
A "user" is a database-level object that maps to the server-level "login" and 
can receive various database-level privileges and roles.

A regular database-level backup and restore will preserve the database "users" 
(and also all kinds of other stuff like the database compatibility level, 
recovery mode, etc.) but not the "logins" if you simply restore to a new box, 
without using any of the Server Migration tools or taking any other special 
steps.

--Steve

On Sun, Feb 19, 2012 at 11:24 AM, David Lum  wrote:
> FYI the new SQL server has the same name as the previous one and I 
> found it also has the same version of SQL. Looking at the LCS console 
> it gives me a red "x" for default certificate settings. I've read 
> somewhere that that's required but we haven't made any changes to the LCS 
> server.
>
>
>
> RtcSrv does not start:
>
> Event Type:    Error
>
> Event Source:    Service Control Manager
>
> Event Category:    None
>
> Event ID:  7024
>
> Date: 2/18/2012
>
> Time: 10:04:00 PM
>
> User: N/A
>
> Computer:  
>
> Description:
>
> The Live Communications Server service terminated with 
> service-specific error 2147942487 (0x80070057).
>
>
>
> Event Type:    Error
>
> Event Source:    Live Communications Server Snap-in
>
> Event Category:    (1004)
>
> Event ID:  30710
>
> Date: 2/18/2012
>
> Time: 9:37:42 PM
>
> User: N/A
>
> Computer:  
>
> Description:
>
> Live Communications Server Snap-in failed to start service:
>
>  Service Name = RtcSrv
>
>  Machine Name = 
>
>  HRESULT = 8007042a
>
>  Error Description = The service has returned a service-specific error code.
>
>
>
>
>
> Event Type:    Error
>
> Event Source:    Live Communications User Services
>
> Event Category:    (1006)
>
> Event ID:  30961
>
> Date: 2/17/2012
>
> Time: 6:22:29 PM
>
> User: N/A
>
> Computer:  
>
> Description:
>
> Failed to connect to backend database.  Live Communications Server 
> will continuously attempt to reconnect to the backend.  While this 
> condition persists, incoming messages will receive error responses.
>
>
>
> Backend Server: OurSQLServer   Database: LCSDb  Connection string of:
>
> driver={SQL
> Server};Trusted_Connection=yes;AutoTranslate=no;server=OurSQLServer;da
> tabase=LCSDb;
>
> Cause: Possible issues with backend database.
>
> Resolution:
>
> Ensure the backend is functioning correctly.
>
>
>
> From: Ken Schaefer [mailto:k...@adopenstatic.com]
> Sent: Sunday, February 19, 2012 4:27 AM
>
>
> To: NT System Admin Issues
> Subject: RE: So...we broke SMS and Lice Communcations Server 2005
>
>
>
> SCOM doesn't require any "weird" access to SQL Server. Any access 
> denied is traceable via Profiler. Dunno about LCS.
>
>
>
> If you manually try to start the rtcsrv, do you get an error code back?
>
>
>
> Cheers
>
> Ken
>
>
>
>
>
> From: Steven Peck [mailto:sep...@gmail.com]
> Sent: Sunday, 19 February 2012 12:42 PM
> To: NT System Admin Issues
> Subject: Re: So...we broke SMS and Lice Communcations Server 2005
>
>
>
> I'd call Microsoft. However if the SQL server was updated, then make 
> sure things like compatibility mode are on and such (and beat the SQL 
> guys for not having people check app compatilibity first).
>
>
>
> In general, it LCS either works or is just broken.  LCS (and SCOM) 
> seriously rely on weird access to SQL so they need rights most SQL 
> DBA's like to take awa

RE: So...we broke SMS and Lice Communcations Server 2005

2012-02-19 Thread Ken Schaefer

Hi,

What is SQL Server Profiler showing? Any failed logins?

Cheers
Ken

From: David Lum [mailto:david@nwea.org]
Sent: Monday, 20 February 2012 12:24 AM
To: NT System Admin Issues
Subject: RE: So...we broke SMS and Lice Communcations Server 2005

FYI the new SQL server has the same name as the previous one and I found it 
also has the same version of SQL. Looking at the LCS console it gives me a red 
"x" for default certificate settings. I've read somewhere that that's required 
but we haven't made any changes to the LCS server.

RtcSrv does not start:
Event Type:Error
Event Source:Service Control Manager
Event Category:None
Event ID:  7024
Date: 2/18/2012
Time: 10:04:00 PM
User: N/A
Computer:  
Description:
The Live Communications Server service terminated with service-specific error 
2147942487 (0x80070057).

Event Type:Error
Event Source:Live Communications Server Snap-in
Event Category:(1004)
Event ID:  30710
Date: 2/18/2012
Time: 9:37:42 PM
User: N/A
Computer:  
Description:
Live Communications Server Snap-in failed to start service:
 Service Name = RtcSrv
 Machine Name = 
 HRESULT = 8007042a
 Error Description = The service has returned a service-specific error code.

Event Type:Error
Event Source:Live Communications User Services
Event Category:(1006)
Event ID:  30961
Date: 2/17/2012
Time: 6:22:29 PM
User: N/A
Computer:  
Description:
Failed to connect to backend database.  Live Communications Server will 
continuously attempt to reconnect to the backend.  While this condition 
persists, incoming messages will receive error responses.

Backend Server: OurSQLServer   Database: LCSDb  Connection string of:
driver={SQL 
Server};Trusted_Connection=yes;AutoTranslate=no;server=OurSQLServer;database=LCSDb;
Cause: Possible issues with backend database.
Resolution:
Ensure the backend is functioning correctly.

From: Ken Schaefer 
[mailto:k...@adopenstatic.com]
Sent: Sunday, February 19, 2012 4:27 AM
To: NT System Admin Issues
Subject: RE: So...we broke SMS and Lice Communcations Server 2005

SCOM doesn't require any "weird" access to SQL Server. Any access denied is 
traceable via Profiler. Dunno about LCS.

If you manually try to start the rtcsrv, do you get an error code back?

Cheers
Ken

From: Steven Peck [mailto:sep...@gmail.com]
Sent: Sunday, 19 February 2012 12:42 PM
To: NT System Admin Issues
Subject: Re: So...we broke SMS and Lice Communcations Server 2005

I'd call Microsoft. However if the SQL server was updated, then make sure 
things like compatibility mode are on and such (and beat the SQL guys for not 
having people check app compatilibity first).

In general, it LCS either works or is just broken.  LCS (and SCOM) seriously 
rely on weird access to SQL so they need rights most SQL DBA's like to take 
away and never give back.  It may be the Upgrade broke something with 
permissions.
On Sat, Feb 18, 2012 at 7:56 PM, David Lum 
mailto:david@nwea.org>> wrote:
LCS service (rtcsrv) does not start.
Event Type:Error
Event Source:Live Communications Server Snap-in
Event Category:(1004)
Event ID:  30710
Date: 2/18/2012
Time:4:24:55 PM
User: N/A
Computer:  LCS
Description:
Live Communications Server Snap-in failed to start service:
 Service Name = RtcSrv
 Machine Name = lcs.americas.nwea.pvt
 HRESULT = 8007042a
 Error Description = The service has returned a service-specific error code.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: So...we broke SMS and Lice Communcations Server 2005

2012-02-19 Thread Steve Kradel

This looks possibly relevant to your issue:
  Sadly none of the events in
this thread hint at the real problem, such as a permissions problem,
failure to resolve a server name, or wonky connection string.
However, this detail ought to show up in the SQL Server logs, and
possibly also in the SQL server machine's OS event logs.  Most likely
the LCS / SMS AD accounts or groups aren't mapped to server logins...
your DBA should be able to check the database users and verify they
have valid logins.

In SQL Server parlance, a "login" is a server-level object mapped to a
Windows principal or SQL Server username+password.
A "user" is a database-level object that maps to the server-level
"login" and can receive various database-level privileges and roles.

A regular database-level backup and restore will preserve the database
"users" (and also all kinds of other stuff like the database
compatibility level, recovery mode, etc.) but not the "logins" if you
simply restore to a new box, without using any of the Server Migration
tools or taking any other special steps.

--Steve

On Sun, Feb 19, 2012 at 11:24 AM, David Lum  wrote:
> FYI the new SQL server has the same name as the previous one and I found it
> also has the same version of SQL. Looking at the LCS console it gives me a
> red “x” for default certificate settings. I’ve read somewhere that that’s
> required but we haven’t made any changes to the LCS server.
>
>
>
> RtcSrv does not start:
>
> Event Type:    Error
>
> Event Source:    Service Control Manager
>
> Event Category:    None
>
> Event ID:  7024
>
> Date: 2/18/2012
>
> Time: 10:04:00 PM
>
> User: N/A
>
> Computer:  
>
> Description:
>
> The Live Communications Server service terminated with service-specific
> error 2147942487 (0x80070057).
>
>
>
> Event Type:    Error
>
> Event Source:    Live Communications Server Snap-in
>
> Event Category:    (1004)
>
> Event ID:  30710
>
> Date: 2/18/2012
>
> Time: 9:37:42 PM
>
> User: N/A
>
> Computer:  
>
> Description:
>
> Live Communications Server Snap-in failed to start service:
>
>  Service Name = RtcSrv
>
>  Machine Name = 
>
>  HRESULT = 8007042a
>
>  Error Description = The service has returned a service-specific error code.
>
>
>
>
>
> Event Type:    Error
>
> Event Source:    Live Communications User Services
>
> Event Category:    (1006)
>
> Event ID:  30961
>
> Date: 2/17/2012
>
> Time: 6:22:29 PM
>
> User: N/A
>
> Computer:  
>
> Description:
>
> Failed to connect to backend database.  Live Communications Server will
> continuously attempt to reconnect to the backend.  While this condition
> persists, incoming messages will receive error responses.
>
>
>
> Backend Server: OurSQLServer   Database: LCSDb  Connection string of:
>
> driver={SQL
> Server};Trusted_Connection=yes;AutoTranslate=no;server=OurSQLServer;database=LCSDb;
>
> Cause: Possible issues with backend database.
>
> Resolution:
>
> Ensure the backend is functioning correctly.
>
>
>
> From: Ken Schaefer [mailto:k...@adopenstatic.com]
> Sent: Sunday, February 19, 2012 4:27 AM
>
>
> To: NT System Admin Issues
> Subject: RE: So...we broke SMS and Lice Communcations Server 2005
>
>
>
> SCOM doesn’t require any “weird” access to SQL Server. Any access denied is
> traceable via Profiler. Dunno about LCS.
>
>
>
> If you manually try to start the rtcsrv, do you get an error code back?
>
>
>
> Cheers
>
> Ken
>
>
>
>
>
> From: Steven Peck [mailto:sep...@gmail.com]
> Sent: Sunday, 19 February 2012 12:42 PM
> To: NT System Admin Issues
> Subject: Re: So...we broke SMS and Lice Communcations Server 2005
>
>
>
> I'd call Microsoft. However if the SQL server was updated, then make sure
> things like compatibility mode are on and such (and beat the SQL guys for
> not having people check app compatilibity first).
>
>
>
> In general, it LCS either works or is just broken.  LCS (and SCOM) seriously
> rely on weird access to SQL so they need rights most SQL DBA's like to take
> away and never give back.  It may be the Upgrade broke something with
> permissions.
>
> On Sat, Feb 18, 2012 at 7:56 PM, David Lum  wrote:
>
> LCS service (rtcsrv) does not start.
>
> Event Type:    Error
>
> Event Source:    Live Communications Server Snap-in
>
> Event Category:    (1004)
>
> Event ID:  30710
>
> Date: 2/18/2012
>
> Time:    4:24:55 PM
>
> User: N/A
>
> Computer:  LCS
>
> Description:
>
> Live Communications Server Snap-in failed to start service:
>
>  Service Name = RtcSrv
>
>  Machine Name = lcs.americas.nwea.pvt
>
>  HRESULT = 8007042a
>
>  Error Description = The service has returned a service-specific

Re: So here's a new one for me...

2012-02-19 Thread Richard Stovall

Thanks, guys.

On Sun, Feb 19, 2012 at 1:47 PM, Michael B. Smith wrote:

>  +1
>
> ** **
>
> *From:* Brian Desmond [mailto:br...@briandesmond.com]
> *Sent:* Sunday, February 19, 2012 1:36 PM
>
> *To:* NT System Admin Issues
> *Subject:* RE: So here's a new one for me...
>
>  ** **
>
> *I wouldn’t chance it – get the motherboard or memory riser replaced.***
>
> * *
>
> *You’re just asking for an outage when the chip does come loose and the
> fact that you knew about it before hand isn’t really going to look that
> great on an RCA. *
>
> * *
>
> *Thanks,*
>
> *Brian Desmond*
>
> *br...@briandesmond.com*
>
> * *
>
> *w – 312.625.1438 | c   – 312.731.3132*
>
> * *
>
> *From:* Richard Stovall [mailto:rich...@gmail.com]
> *Sent:* Sunday, February 19, 2012 11:42 AM
> *To:* NT System Admin Issues
> *Subject:* So here's a new one for me...
>
> ** **
>
> I went into work today to replace some RAM in an HP BL460c blade server.
> I began to remove one of the smaller capacity FBDIMMS and the clip broke
> off in my hand.  I've never had that happen before.  I chose to replace a
> different pair and leave the one with the broken clip in place.
>
>  
>
> My question is whether or not the FBDIMM might eventually vibrate out of
> its slot because of the broken clip.  One clip is still there.
>
>  
>
> Any thoughts about or experience with a situation like this?
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: So here's a new one for me...

2012-02-19 Thread Michael B. Smith

+1

From: Brian Desmond [mailto:br...@briandesmond.com]
Sent: Sunday, February 19, 2012 1:36 PM
To: NT System Admin Issues
Subject: RE: So here's a new one for me...

I wouldn’t chance it – get the motherboard or memory riser replaced.

You’re just asking for an outage when the chip does come loose and the fact 
that you knew about it before hand isn’t really going to look that great on an 
RCA.

Thanks,
Brian Desmond
br...@briandesmond.com

w – 312.625.1438 | c   – 312.731.3132

From: Richard Stovall 
[mailto:rich...@gmail.com]
Sent: Sunday, February 19, 2012 11:42 AM
To: NT System Admin Issues
Subject: So here's a new one for me...

I went into work today to replace some RAM in an HP BL460c blade server.  I 
began to remove one of the smaller capacity FBDIMMS and the clip broke off in 
my hand.  I've never had that happen before.  I chose to replace a different 
pair and leave the one with the broken clip in place.

My question is whether or not the FBDIMM might eventually vibrate out of its 
slot because of the broken clip.  One clip is still there.

Any thoughts about or experience with a situation like this?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: So here's a new one for me...

2012-02-19 Thread Richard Stovall

Quick update.

The FBDIMM seems to be in the slot very securely.  Pulling up with a small
amount of measured but firm force on the side of the module with the broken
clip does not even begin to dislodge it.

On Sun, Feb 19, 2012 at 12:42 PM, Richard Stovall  wrote:

> I went into work today to replace some RAM in an HP BL460c blade server.
> I began to remove one of the smaller capacity FBDIMMS and the clip broke
> off in my hand.  I've never had that happen before.  I chose to replace a
> different pair and leave the one with the broken clip in place.
>
> My question is whether or not the FBDIMM might eventually vibrate out of
> its slot because of the broken clip.  One clip is still there.
>
> Any thoughts about or experience with a situation like this?
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: So here's a new one for me...

2012-02-19 Thread Brian Desmond

I wouldn’t chance it – get the motherboard or memory riser replaced.

You’re just asking for an outage when the chip does come loose and the fact 
that you knew about it before hand isn’t really going to look that great on an 
RCA.

Thanks,
Brian Desmond
br...@briandesmond.com

w – 312.625.1438 | c   – 312.731.3132

From: Richard Stovall [mailto:rich...@gmail.com]
Sent: Sunday, February 19, 2012 11:42 AM
To: NT System Admin Issues
Subject: So here's a new one for me...

I went into work today to replace some RAM in an HP BL460c blade server.  I 
began to remove one of the smaller capacity FBDIMMS and the clip broke off in 
my hand.  I've never had that happen before.  I chose to replace a different 
pair and leave the one with the broken clip in place.

My question is whether or not the FBDIMM might eventually vibrate out of its 
slot because of the broken clip.  One clip is still there.

Any thoughts about or experience with a situation like this?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: So...we broke SMS and Lice Communcations Server 2005

2012-02-19 Thread David Lum

FYI the new SQL server has the same name as the previous one and I found it 
also has the same version of SQL. Looking at the LCS console it gives me a red 
"x" for default certificate settings. I've read somewhere that that's required 
but we haven't made any changes to the LCS server.

RtcSrv does not start:
Event Type:Error
Event Source:Service Control Manager
Event Category:None
Event ID:  7024
Date: 2/18/2012
Time: 10:04:00 PM
User: N/A
Computer:  
Description:
The Live Communications Server service terminated with service-specific error 
2147942487 (0x80070057).

Event Type:Error
Event Source:Live Communications Server Snap-in
Event Category:(1004)
Event ID:  30710
Date: 2/18/2012
Time: 9:37:42 PM
User: N/A
Computer:  
Description:
Live Communications Server Snap-in failed to start service:
 Service Name = RtcSrv
 Machine Name = 
 HRESULT = 8007042a
 Error Description = The service has returned a service-specific error code.


Event Type:Error
Event Source:Live Communications User Services
Event Category:(1006)
Event ID:  30961
Date: 2/17/2012
Time: 6:22:29 PM
User: N/A
Computer:  
Description:
Failed to connect to backend database.  Live Communications Server will 
continuously attempt to reconnect to the backend.  While this condition 
persists, incoming messages will receive error responses.

Backend Server: OurSQLServer   Database: LCSDb  Connection string of:
driver={SQL 
Server};Trusted_Connection=yes;AutoTranslate=no;server=OurSQLServer;database=LCSDb;
Cause: Possible issues with backend database.
Resolution:
Ensure the backend is functioning correctly.

From: Ken Schaefer [mailto:k...@adopenstatic.com]
Sent: Sunday, February 19, 2012 4:27 AM
To: NT System Admin Issues
Subject: RE: So...we broke SMS and Lice Communcations Server 2005

SCOM doesn't require any "weird" access to SQL Server. Any access denied is 
traceable via Profiler. Dunno about LCS.

If you manually try to start the rtcsrv, do you get an error code back?

Cheers
Ken


From: Steven Peck [mailto:sep...@gmail.com]
Sent: Sunday, 19 February 2012 12:42 PM
To: NT System Admin Issues
Subject: Re: So...we broke SMS and Lice Communcations Server 2005

I'd call Microsoft. However if the SQL server was updated, then make sure 
things like compatibility mode are on and such (and beat the SQL guys for not 
having people check app compatilibity first).

In general, it LCS either works or is just broken.  LCS (and SCOM) seriously 
rely on weird access to SQL so they need rights most SQL DBA's like to take 
away and never give back.  It may be the Upgrade broke something with 
permissions.
On Sat, Feb 18, 2012 at 7:56 PM, David Lum 
mailto:david@nwea.org>> wrote:
LCS service (rtcsrv) does not start.
Event Type:Error
Event Source:Live Communications Server Snap-in
Event Category:(1004)
Event ID:  30710
Date: 2/18/2012
Time:4:24:55 PM
User: N/A
Computer:  LCS
Description:
Live Communications Server Snap-in failed to start service:
 Service Name = RtcSrv
 Machine Name = lcs.americas.nwea.pvt
 HRESULT = 8007042a
 Error Description = The service has returned a service-specific error code.




~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: So...we broke SMS and Lice Communcations Server 2005

2012-02-19 Thread Ken Schaefer

SCOM doesn't require any "weird" access to SQL Server. Any access denied is 
traceable via Profiler. Dunno about LCS.

If you manually try to start the rtcsrv, do you get an error code back?

Cheers
Ken


From: Steven Peck [mailto:sep...@gmail.com]
Sent: Sunday, 19 February 2012 12:42 PM
To: NT System Admin Issues
Subject: Re: So...we broke SMS and Lice Communcations Server 2005

I'd call Microsoft. However if the SQL server was updated, then make sure 
things like compatibility mode are on and such (and beat the SQL guys for not 
having people check app compatilibity first).

In general, it LCS either works or is just broken.  LCS (and SCOM) seriously 
rely on weird access to SQL so they need rights most SQL DBA's like to take 
away and never give back.  It may be the Upgrade broke something with 
permissions.
On Sat, Feb 18, 2012 at 7:56 PM, David Lum 
mailto:david@nwea.org>> wrote:
LCS service (rtcsrv) does not start.
Event Type:Error
Event Source:Live Communications Server Snap-in
Event Category:(1004)
Event ID:  30710
Date: 2/18/2012
Time:4:24:55 PM
User: N/A
Computer:  LCS
Description:
Live Communications Server Snap-in failed to start service:
 Service Name = RtcSrv
 Machine Name = lcs.americas.nwea.pvt
 HRESULT = 8007042a
 Error Description = The service has returned a service-specific error code.




~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: So...we broke SMS and Lice Communcations Server 2005

2012-02-19 Thread Ken Schaefer

No - it doesn't matter. Unless someone configured a SQL alias, and is using 
that to connect to the SQL Server. The alias should point to the FQDN of the 
SQL Server, but maybe it points to the IP.

When you say "you upgraded the SQL Server", what exactly was done?

If you enable audit logging in SQL Server (or run Profiler), are you even 
seeing any attempts to connect? If so, what is happening to those connections?

What other troubleshooting have you done? And what are the results?

Cheers
Ken

From: David Lum [mailto:david@nwea.org]
Sent: Sunday, 19 February 2012 1:26 PM
To: NT System Admin Issues
Subject: RE: So...we broke SMS and Lice Communcations Server 2005


I did find the new SQL server has the same name but different IP. Not sure if 
that should matter, but I know it can sometimes..

Dave

From: Rankin, James R 
[mailto:kz2...@googlemail.com]
Sent: Saturday, February 18, 2012 9:17 PM
To: NT System Admin Issues
Subject: Re: So...we broke SMS and Lice Communcations Server 2005

Those lice can do without for now
Sent from my SR-71 Blackbird

From: David Lum mailto:david@nwea.org>>
Date: Sat, 18 Feb 2012 23:50:40 +
To: NT System Admin 
Issuesmailto:ntsysadmin@lyris.sunbelt-software.com>>
ReplyTo: "NT System Admin Issues" 
mailto:ntsysadmin@lyris.sunbelt-software.com>>
Subject: So...we broke SMS and Lice Communcations Server 2005

Our DBA's upgraded our SQL server to a SQL box of the same name but now SMS and 
LCS are broken. As I have never configured either of these from scratch do you 
guys happen to have any pointers? Some of our other SQL-dependant apps came 
back fine (Sharepoint, McAfee), but LCS and SMS now no worky.

The consoles I do have up for both apps aren't much help. SMS has site repair 
and site setup options, but I am not sure what they do and if they'll make 
things worse. LCS I have even less options to look at.

I guess I should look at this as a DR issue and pretend we have to reconnect to 
DB's that were restored from backup onto a different server, and this server 
just happens to have the same name?
David Lum
Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 503.267.9764


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Moxie Marlinspike's CloudCracker Aims For Speedier, Cheaper Password Cracking

RE: dns issue with browser (OS X)

RE: So...we broke SMS and Lice Communcations Server 2005

RE: So...we broke SMS and Lice Communcations Server 2005

Re: So...we broke SMS and Lice Communcations Server 2005

Re: So here's a new one for me...

RE: So here's a new one for me...

Re: So here's a new one for me...

RE: So here's a new one for me...

RE: So...we broke SMS and Lice Communcations Server 2005

RE: So...we broke SMS and Lice Communcations Server 2005

RE: So...we broke SMS and Lice Communcations Server 2005

12 matches

Site Navigation

Mail list logo

Footer information