<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SQL Website</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/sql-website/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/sql-website/</link>
	<description></description>
	<pubDate>Sat, 26 May 2012 11:34:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: schuit</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/sql-website/#comment-42065</link>
		<dc:creator>schuit</dc:creator>
		<pubDate>Thu, 30 Dec 2004 12:31:13 +0000</pubDate>
		<guid isPermaLink="false">#comment-42065</guid>
		<description>thanks,
  As an admin i tried to create an odbc connection to the sqlbox on the dmz and it times out. I can ping the sql box fine.
any other ideas and thanks for the help so far</description>
		<content:encoded><![CDATA[<p>thanks,<br />
  As an admin i tried to create an odbc connection to the sqlbox on the dmz and it times out. I can ping the sql box fine.<br />
any other ideas and thanks for the help so far</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taney2000</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/sql-website/#comment-42066</link>
		<dc:creator>Taney2000</dc:creator>
		<pubDate>Thu, 30 Dec 2004 11:21:36 +0000</pubDate>
		<guid isPermaLink="false">#comment-42066</guid>
		<description>That should work. I would first check the network settings on you SQL server and verify first that you are using IP and your port is set for 1433. Not knowing how you are connecting I would setup an ODBC and verify connectivity that way. You can also try and telnet to 1433 so see if it repsonds. you can also do a netstat -a on the sql server to verify what ports it is listening on.</description>
		<content:encoded><![CDATA[<p>That should work. I would first check the network settings on you SQL server and verify first that you are using IP and your port is set for 1433. Not knowing how you are connecting I would setup an ODBC and verify connectivity that way. You can also try and telnet to 1433 so see if it repsonds. you can also do a netstat -a on the sql server to verify what ports it is listening on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melvin</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/sql-website/#comment-42067</link>
		<dc:creator>Melvin</dc:creator>
		<pubDate>Thu, 30 Dec 2004 09:45:47 +0000</pubDate>
		<guid isPermaLink="false">#comment-42067</guid>
		<description>Melvin,

Could be several things.

I assume since the SQL server is in the DMZ, you have some type of 192.xxx.xxx.xxx IP scheme going on.  If this is so, make sure your workstations can ping it.  If they cant, a simple route add command to the workstation route table is neccesary.

Secondly, do the users have the correct rights to the server and/or database where the tables are stored?  These rights are from you AD, not necessarily from rights to the SQL table.  If the users do not have read/write access to the physical resource, they will not be able to update the tables.</description>
		<content:encoded><![CDATA[<p>Melvin,</p>
<p>Could be several things.</p>
<p>I assume since the SQL server is in the DMZ, you have some type of 192.xxx.xxx.xxx IP scheme going on.  If this is so, make sure your workstations can ping it.  If they cant, a simple route add command to the workstation route table is neccesary.</p>
<p>Secondly, do the users have the correct rights to the server and/or database where the tables are stored?  These rights are from you AD, not necessarily from rights to the SQL table.  If the users do not have read/write access to the physical resource, they will not be able to update the tables.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->
