sql server 2005 error 65535 when connecting with sql agent

I'm trying to get SQL server agent running on my sql server 2005.  It appears to start up fine, but when I try to run a job, I get the following errors:
[298] SQLServer Error: 65535, SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]

[165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]

 [298] SQLServer Error: 65535, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]

[382] Logon to server 'COMPUTERNAME' failed (ConnAttemptCachableOp)

I've looked at the server and it does appear to allow remote connections.  I'm wondering why I'd get this message though since sql agent is on the local server.

I've tried changing the account that SQL Server Agent uses and it doesn't seem to matter.  Does anyone has any suggestions?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

who is the owner of the "job"?
does that owner have sysadmin rights on the server?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
leos_Author Commented:
the owner of the job does have sysadmin rights on the server
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

leos_Author Commented:
the article http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx did pose some interesting questions.  I'm not sure whether or not things are connecting right.  So I went into ODBC connections and tried to make a System DNS connection.  I noticed there that one of the connections to the server had "/sql2005" appended to it.  Since this server only runs sql2005 we don't need this, so I removed it.  Now I'm getting a whole new set of errors:

[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]

[382] Logon to server 'COMPUTERNAME' failed (ConnAttemptCachableOp)

leos_Author Commented:
OK, so I solved the issue.  Somehow in the SQL server Configuration Manager, an alias got made pointing our machine name to the DNS we used to connect remotely to the machine.  Once this was removed, everything worked fine.  I'm not sure how this was added since I wasn't the one who installed and initially configured the database.  Thanks for your help.
leos_Author Commented:
Thanks for your help.  The website you directed me to eventually led me the the answer.
What did it for me was deleting/renaming the 'SQLAGENT.OUT' file and then restarting the SQL Server Agent service. After the succesfull restart, a new file was created.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.