C++/VB - Urgent help!

Asked By ed

27-Jan-10 10:51 AM

Hi all,

windows 2003 sp2/xp sp3

Is there a way to push out ODBC connection to uses through group plicy ? I
did the registry key odbcini in the HKLM\Software\ODBC.  But, we use the
customized port, 2494  It looks like that I can not specify the different
port other than 1433?

Here is the key:
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI]

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Con]

Any one has script for this to use the customized port, not dynamically
determine port?  (we use windows nt authtication, not sql authentication)


Thank you.

28-Jan-10 02:49 AM

Hi ed,

1433 is the default tcp port of SQL server db service, if you want to
change it, you can use the registry entry to modify the port value:

port or dynamic port
http://support.microsoft.com/kb/823938

I am not awared of any particular windows group policy setting that will
control the port entry of SQL server or other ODBC related settings, i
suggest you try posting in the windows server group policy forum for more
ideas on this:

http://social.technet.microsoft.com/Forums/en-US/winserverGP/threads

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.


--------------------

28-Jan-10 02:50 AM

Hi,

I noticed that your question has been solved in TechNet
(http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/4f1120c
5-343c-4a08-a66e-885a8ff8cd19) and since this thread is off-topic in
VBScript discussion, I am going to close this one.

Best regards,
Jie Wang

Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business days is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

28-Jan-10 01:33 PM

microsoft.public.scripting.vbscript:


Dear Jie,

While you are probably right that the Q was OT and/or answered elsewere,
you have no right or power in a unmoderated Usenet NG to close a thread.

The only things you can do is personally withdraw from the thread and/or
advice us not to follow up.

A usenet NG is not a helpdesk.

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

28-Jan-10 01:53 PM

I think Jie just meant the issue was being
closed from the point of view of subscriber
support. Microsoft employees are hired to
shower MSDN subscribers with lavish
solicitousness and concern, while systematically
ignoring all other newsgroup activity. As far
as Jie's concerned, the rest of us are not even here.

The absurd byline "Delighting our customers is
our #1 priority" refers to *paying* MSDN support
customers, not Microsoft customers.