Tony: This file you are taking about does not contain any info about port 1433. You can be sure I did a search in microsoft site before going to the list , although I did not find the right keyword combinations at the begining . After making a cousious search in the SQL Errorlog I found the right keyword combination. thanks friend regards Mario
----- Original Message ----- From: <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Thursday, May 30, 2002 2:11 PM Subject: RE: SQL server trouble > just out curiosity. I wonder, if the next time this happens, if you viewed > the services file, (c:\winnt\system32\drivers\etc\services) if it would tell > you what is hooked on that port. if it does, then you know what app is the > culprit. > > Anthony Petruzzi > Webmaster > 954-321-4703 > [EMAIL PROTECTED] > http://www.sheriff.org > > > -----Original Message----- > From: Mario Martinez [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 30, 2002 1:46 PM > To: CF-Talk > Subject: Re: SQL server trouble > > > Thank you for your responses friends. > I finally found the answer in www.microsoft.com in the troubleshouting > section. > The problem was that somehow one winsock service(as the port asiggment is > dinamically on it) was steeling the 1433 port and SQL server could not > listen in 1433 port. What I did was to stop all the services except the > defaults, restart the SQL service and restart the others services again, in > this way SQL server takes this port firts. > I have to work around it because it could happen again anytime > I restart the machine. > > Thanks for your concern > > regards Mario > ----- Original Message ----- > From: "Rob Baxter" <[EMAIL PROTECTED]> > To: "CF-Talk" <[EMAIL PROTECTED]> > Sent: Thursday, May 30, 2002 12:32 PM > Subject: RE: SQL server trouble > > > > check to make sure your SQL server is listening on tcp port 1433 (unless > you > > have changed the default port). You can either do a netstat -an from the > sql > > box or from the client machine try > > > > telnet sql-server-ip 1433 > > > > If you get a response your traffic is getting through. If not you've > either > > got something in the way (firewall) or a problem with your SQL network > > libraries. I actually just had this problem yesterday so if that is it > I'll > > tell you what worked for me. Have you made any configuration changes to > SQL > > recently? > > > > </rob> > > > > -----Original Message----- > > From: Mario Martinez [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, May 30, 2002 12:10 PM > > To: CF-Talk > > Subject: SQL server trouble > > > > > > Hi all friends: > > > > I got a coldfusion system with an SQL server . Today I came in here and I > > realize that I can't connect this SQL server from any other computer > through > > ODBC . I could do that before , now none of my remotly ODBC connections > are > > working > > This is the error I receive when I try to connect remotly: > > Connection failed > > SQLState:'01000' > > SQL Server Error: 10061 > > [Microsoft][ODBC SQL Server Driver ][TCP/IP > > Sockets]ConnectionOpen(connect()). > > Connection failed: > > SQLState: '08001' > > SQL Server Error: 11 > > [Microsoft][ODBC SQL Server Driver]General network error. Check your > network > > documentation. > > > > Any ideas will be more than appreciate. > > regards > > Mario > > > > > > > > ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
