I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.
I would try to connect to it via its IP address using a SQL Server login just
in case it is a DNS issue. Just a thought...
Thomas
"Steve Z" wrote:
> I just installed developer's edition on a new laptop. Other machines in the
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instance
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.
|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
[vbcol=seagreen]
> I would try to connect to it via its IP address using a SQL Server login just
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
Showing posts with label machines. Show all posts
Showing posts with label machines. Show all posts
Tuesday, March 27, 2012
Authorization problems with SQL Developer's edition
I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login just
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:
> I just installed developer's edition on a new laptop. Other machines in the
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instance
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
> I would try to connect to it via its IP address using a SQL Server login just
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
> > I just installed developer's edition on a new laptop. Other machines in the
> > network cannot connect to this new instance.
> >
> > At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> > (we are inside a small network anyway - no need for local firewalls - I
> > guess).
> >
> > Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> > username under COMPUTER MANAGEMENT and disabled it.
> >
> > Now it's getting login failed for user NULL.
> >
> > Seems it's not on the network like the old laptop was. The old laptop did
> > not authenticate to the network, it logged in locally, but the SQL instance
> > was visible and connectable.
> >
> > I cannot seem to add DOMAIN\usernames to this instance.
> >
> > Any direction would be greatly appreciated.
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login just
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:
> I just installed developer's edition on a new laptop. Other machines in the
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instance
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
> I would try to connect to it via its IP address using a SQL Server login just
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
> > I just installed developer's edition on a new laptop. Other machines in the
> > network cannot connect to this new instance.
> >
> > At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> > (we are inside a small network anyway - no need for local firewalls - I
> > guess).
> >
> > Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> > username under COMPUTER MANAGEMENT and disabled it.
> >
> > Now it's getting login failed for user NULL.
> >
> > Seems it's not on the network like the old laptop was. The old laptop did
> > not authenticate to the network, it logged in locally, but the SQL instance
> > was visible and connectable.
> >
> > I cannot seem to add DOMAIN\usernames to this instance.
> >
> > Any direction would be greatly appreciated.
Authorization problems with SQL Developer's edition
I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login jus
t
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:
> I just installed developer's edition on a new laptop. Other machines in t
he
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall featur
e
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instanc
e
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
[vbcol=seagreen]
> I would try to connect to it via its IP address using a SQL Server login j
ust
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
>sql
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login jus
t
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:
> I just installed developer's edition on a new laptop. Other machines in t
he
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall featur
e
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instanc
e
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
[vbcol=seagreen]
> I would try to connect to it via its IP address using a SQL Server login j
ust
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
>sql
Monday, March 19, 2012
Authenticating between Webserver and database Server
Not sure if this is an ASP.NET or a SQL issue...
Environment:
Webserver on Server1
SqlServer on Server 2
Both machines in the same domain. I have followed the steps in the to create
a domain level account to run the ASPNET process that has access to the
database.
When I try to retrieve data from the DB, i get:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection. 18452
Any guidence would be appriciated.See "Security Account Delegation" in BOL.
AMB
"PublicRick" wrote:
> Not sure if this is an ASP.NET or a SQL issue...
> Environment:
> Webserver on Server1
> SqlServer on Server 2
> Both machines in the same domain. I have followed the steps in the to crea
te
> a domain level account to run the ASPNET process that has access to the
> database.
> When I try to retrieve data from the DB, i get:
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection. 18452
> Any guidence would be appriciated.
>|||http://msdn.microsoft.com/library/default.asp?
AND
http://msdn.microsoft.com/library/d...
d19.asp
HTH, Jens SUessmeyer.
"PublicRick" <publicrick@.nospam.nospam> schrieb im Newsbeitrag
news:EE873E20-AA3E-41B5-9030-9F0A2C360A41@.microsoft.com...
> Not sure if this is an ASP.NET or a SQL issue...
> Environment:
> Webserver on Server1
> SqlServer on Server 2
> Both machines in the same domain. I have followed the steps in the to
> create
> a domain level account to run the ASPNET process that has access to the
> database.
> When I try to retrieve data from the DB, i get:
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection. 18452
> Any guidence would be appriciated.
>
Environment:
Webserver on Server1
SqlServer on Server 2
Both machines in the same domain. I have followed the steps in the to create
a domain level account to run the ASPNET process that has access to the
database.
When I try to retrieve data from the DB, i get:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection. 18452
Any guidence would be appriciated.See "Security Account Delegation" in BOL.
AMB
"PublicRick" wrote:
> Not sure if this is an ASP.NET or a SQL issue...
> Environment:
> Webserver on Server1
> SqlServer on Server 2
> Both machines in the same domain. I have followed the steps in the to crea
te
> a domain level account to run the ASPNET process that has access to the
> database.
> When I try to retrieve data from the DB, i get:
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection. 18452
> Any guidence would be appriciated.
>|||http://msdn.microsoft.com/library/default.asp?
AND
http://msdn.microsoft.com/library/d...
d19.asp
HTH, Jens SUessmeyer.
"PublicRick" <publicrick@.nospam.nospam> schrieb im Newsbeitrag
news:EE873E20-AA3E-41B5-9030-9F0A2C360A41@.microsoft.com...
> Not sure if this is an ASP.NET or a SQL issue...
> Environment:
> Webserver on Server1
> SqlServer on Server 2
> Both machines in the same domain. I have followed the steps in the to
> create
> a domain level account to run the ASPNET process that has access to the
> database.
> When I try to retrieve data from the DB, i get:
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection. 18452
> Any guidence would be appriciated.
>
Subscribe to:
Posts (Atom)