Re: Help with NAT and DSN setups in CF Admin
Thanks for the reply Dave. You always have great suggestions. At this point, I cannot even connect to a local SQL Server, on the same "10 dot" network as the CF box. I verified that both TCP/IP and Named Pipes are enabled in the Server Network Utility, and that both Windows and SQL Server logins are enabled on the SQL Server Configuration\Security Tab. I can type \\SERVERNAME\c$ for the SQLbox - from the webserver - and I get access no problem. I am unable to connect from the CF Admin and get the same error when I use either the public IP or the "10 dot" IP for the SQL Server (instead of the name). Any ideas? Dave Watts wrote: >>Our IIS 6/CF server is on a "10 dot" network, and mapped to >>an external IP via our firewall appliance. >> >>When trying to set up a DSN to our MS SQL Server, I keep >>getting a "connection refused" error message. I am using the >>server name (UNC >>name) and the correct username/password. The SQL server is >>across the 'net on another network. The CF/Web server's >>public IP has open access through the firewall into the >>network where the SQL server is kept. >> >>What's strange, is that I created a system datasource in the >>ODBC control panel applet, and I connect to the SQL server >>just fine. I then used the CF Admin to create an ODBC socket >>DSN to connect to the local DSN on the web server. >> >>Any ideas on why I can connect to the remote SQL server via a >>Microsoft local system DSN, but not directly to the SQL box >>from CF Admin using the stock SQL server drivers? >> >> > >When you connect via ODBC, are you using TCP/IP, or Named Pipes? (Named >Pipes uses Windows Networking (NetBIOS) on top of whatever protocol you're >using, which is typically TCP/IP.) Named Pipes is the default, and JDBC >doesn't support that. You may need to configure your SQL Server's network >listeners to include TCP/IP. You can do this using the Server Network >Utility from the SQL Server console. > >Also, is your SQL Server configured to allow native SQL logins (untrusted >connections)? By default, SQL Server only accepts trusted connections that >use Windows authentication. The JDBC drivers that come with CFMX don't >support this, although apparently some third-party drivers like jTDS >(http://jtds.sourceforge.net/) do. > >Dave Watts, CTO, Fig Leaf Software >http://www.figleaf.com/ > >Fig Leaf Software provides the highest caliber vendor-authorized >instruction at our training centers in Washington DC, Atlanta, >Chicago, Baltimore, Northern Virginia, or on-site at your location. >Visit http://training.figleaf.com/ for more information! > > > ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201577 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Help with NAT and DSN setups in CF Admin
> Our IIS 6/CF server is on a "10 dot" network, and mapped to > an external IP via our firewall appliance. > > When trying to set up a DSN to our MS SQL Server, I keep > getting a "connection refused" error message. I am using the > server name (UNC > name) and the correct username/password. The SQL server is > across the 'net on another network. The CF/Web server's > public IP has open access through the firewall into the > network where the SQL server is kept. > > What's strange, is that I created a system datasource in the > ODBC control panel applet, and I connect to the SQL server > just fine. I then used the CF Admin to create an ODBC socket > DSN to connect to the local DSN on the web server. > > Any ideas on why I can connect to the remote SQL server via a > Microsoft local system DSN, but not directly to the SQL box > from CF Admin using the stock SQL server drivers? When you connect via ODBC, are you using TCP/IP, or Named Pipes? (Named Pipes uses Windows Networking (NetBIOS) on top of whatever protocol you're using, which is typically TCP/IP.) Named Pipes is the default, and JDBC doesn't support that. You may need to configure your SQL Server's network listeners to include TCP/IP. You can do this using the Server Network Utility from the SQL Server console. Also, is your SQL Server configured to allow native SQL logins (untrusted connections)? By default, SQL Server only accepts trusted connections that use Windows authentication. The JDBC drivers that come with CFMX don't support this, although apparently some third-party drivers like jTDS (http://jtds.sourceforge.net/) do. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201549 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Help with NAT and DSN setups in CF Admin
For the time being, all ports on both boxes are open. If the port weren't open on the SQL server's network, then the local system DSN wouldn't be able to connect either, but it does! -- Alex Connie DeCinko wrote: >Make sure you have the correct port open. > > >-Original Message- >From: Alex Sherwood [mailto:[EMAIL PROTECTED] >Sent: Tuesday, April 05, 2005 10:30 AM >To: CF-Talk >Subject: Help with NAT and DSN setups in CF Admin > >Greetings. > >Our IIS 6/CF server is on a "10 dot" network, and mapped to an external >IP via our firewall appliance. > >When trying to set up a DSN to our MS SQL Server, I keep getting a >"connection refused" error message. I am using the server name (UNC >name) and the correct username/password. The SQL server is across the >'net on another network. The CF/Web server's public IP has open access >through the firewall into the network where the SQL server is kept. > >What's strange, is that I created a system datasource in the ODBC >control panel applet, and I connect to the SQL server just fine. I then >used the CF Admin to create an ODBC socket DSN to connect to the local >DSN on the web server. > > >Any ideas on why I can connect to the remote SQL server via a Microsoft >local system DSN, but not directly to the SQL box from CF Admin using >the stock SQL server drivers? > >Any help would be greatly appreciated! > >-- >Alex Sherwood > > > ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201540 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Help with NAT and DSN setups in CF Admin
Make sure you have the correct port open. -Original Message- From: Alex Sherwood [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 05, 2005 10:30 AM To: CF-Talk Subject: Help with NAT and DSN setups in CF Admin Greetings. Our IIS 6/CF server is on a "10 dot" network, and mapped to an external IP via our firewall appliance. When trying to set up a DSN to our MS SQL Server, I keep getting a "connection refused" error message. I am using the server name (UNC name) and the correct username/password. The SQL server is across the 'net on another network. The CF/Web server's public IP has open access through the firewall into the network where the SQL server is kept. What's strange, is that I created a system datasource in the ODBC control panel applet, and I connect to the SQL server just fine. I then used the CF Admin to create an ODBC socket DSN to connect to the local DSN on the web server. Any ideas on why I can connect to the remote SQL server via a Microsoft local system DSN, but not directly to the SQL box from CF Admin using the stock SQL server drivers? Any help would be greatly appreciated! -- Alex Sherwood ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201536 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
