The default port for teradata is 1025. I want to change that.
I have launched the teradata server on ec2. I tried to change it via the "Teradata Administrator Tool", but it does not have such an option.
I could not find any teradata admin tools/tutorials that explains how to change the default port number.
Apparently, we cannot change the port number. (Checked with teradata support)
Related
ERROR [HY000] [Snowflake][Snowflake] (4)
We are running ODBC on a Windows 10 computer. I have posted an image of the error messages below. We are also NOT using a proxy server.
enter image description here
You are connecting from behind a Proxy server, the name of which the driver is not able to resolve.
Try giving the IP address of the proxy server. Check
https://docs.snowflake.com/en/user-guide/odbc-parameters.html#connecting-through-a-proxy-server
for deatails on how to connect.
get the latest odbc driver
Change registry setting in windows to set ssl_default=true,
https_proxy environment variable with proxy serve:port
finally you would have to allow all the url that is emanating from that server to internet. There will be url's to snowflake computing and s3 aws urls while you invoke odbc different from web UI for querying.
Some systems have proxy settings in their environment; this is not documented on the odbc description on the Snowflake website.
So, if the other solution don't work, check this out.
I had the same issue and it was solved by taking out "https://" from the beginning, so that it will be treated as a server as opposed to a URL.
We have oracle oledb connections in SSIS packages that are working well on windows server 2008.
We moved them to windows server 2012 and installed the needed softwares. We installed oracle client (oraoledb driver), moved tnsnames.ora, ldap.ora and sqlnet.ora to %Oracle_Home%\Network\admin path, add %Oracle_Home% and %Oracle_Home%\bin to path variable.
But on server 2012 oracle connections are giving this error ORA-12541: TNS: no listener. Where as on server 2008 same oracle connections are working fine.
Looked so much across internet but found these solutions:
Check tnsnames.ora
Check listener is running
Check path variable contain oracle home, oracle_home\bin
I don't see a problem with tnsnames.ora because same file is present on both window servers. Correct path variables are also set. Listener is also running (since SSIS on server 2008 is connecting). And I am able to ping oracle db server from both machines.
Can anyone suggest anything that we may try.
To put a formal answer in here.
Basic troubleshooting steps with SSIS:
Use the database native tools to check connectivity
In this case for Oracle that is SQLPLUS.EXE
If you have an issue with native tools then it isn't an SSIS issue
Check that you can resolve the host by using PING <hostname>.
If that doesn't work try PING <ip address>
If ping works, check the port with TELNET <host> <port>
If that doesn't work, either the service is not listening or you need to get your network guys to open the port
This goes for any network service
i.e.
SQL Server (default port 1433)
a web server (default port 80 for unencrypted comms)
Our server is hosting a mix of asp and php websites. (windows server)
For months mySQL has been working unhindered and suddenly this has now stopped working.
I've tried connecting to MySql using the correct credentials which results in:
ERROR 2003 (HY000): Can't connect to MySQL server on 'localhost' (10055)
I've tried restarting the service using net stop MySql and net start MySql to no avail.
I have also tried using telnet localhost 3306 and telnet 127.0.0.1 and can confirm that the port is not acessible.
My hosting provider has inspected the step but is at a loss as to how we can remedy the situation. They have also inspected firewall settings and all seems to be correct.
find physical database files on disk.
back them up.
restard host computer.
then follow these steps:
Click Start, click Run, type regedit.exe, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, point to New, and then click DWORD Value.
Type MaxUserPort and then press ENTER.
Double-click the MaxUserPort value, and then type the maximum value in decimal or hexadecimal.
You must type a number in the range of 500065534 (decimal). Setting this parameter to a value outside of the valid range causes the nearest valid value to be used (5000 or 65534).
Click OK.
Quit Registry Editor.
restart host computer again. you should be fine now.
The issue is caused because IIS is complete garbage, and keeps consuming ports to connect to MySQL using ODBC. there is no max port value, so when all prots are used up, application crashes. You can solve this issue by following the stebs above, or by reviewing your asp.net application to use mysql connnect / net, instead of ODBC.
I am able to ping a database server from my machine but am having a hard time connecting. Should I be able to connect or could there be other network features that are getting in the way?
I am trying to connect with Oracle SQL developer to an Oracle 11g R2 database.
Here are the instructions to connect to database using sql developer
Know the port number on which database is listening (by default 1521)
Make sure you can telnet to the host and the port number
There are several ways, you can connect (BASIC, TNS, Advanced etc)
For Basic, you need to give host ip or resolvable name, port and sid or service name as part of the connect string. Similarly for JDBC you need to give valid JDBC url and also you are supposed to ojdbc jar file in the appropriate location of sql developer.
I need to know the default port settings for the following services
SQL Server
SQL Browser
SQL Reporting services
SQL Analysis services
I need to know the port settings for these services for different versions of SQL Server (2000,2005,2008)
Also let me know whether the default port setting will change based on sql server versions.
The default SQL Server port is 1433 but only if it's a default install. Named instances get a random port number.
The browser service runs on port UDP 1434.
Reporting services is a web service - so it's port 80, or 443 if it's SSL enabled.
Analysis services is 2382 but only if it's a default install. Named instances get a random port number.
If you have access to the server then you can use
select local_tcp_port from sys.dm_exec_connections where local_tcp_port is not null
For full details see port number of SQL Server
The default, unnamed instance always gets port 1433 for TCP. UDP port 1434 is used by the SQL Browser service to allow named instances to be located. In SQL Server 2000 the first instance to be started took this role.
Non-default instances get their own dynamically-allocated port, by default. If necessary, for example to configure a firewall, you can set them explicitly. If you don't want to enable or allow access to SQL Browser, you have to either include the instance's port number in the connection string, or set it up with the Alias tab in cliconfg (SQL Server Client Network Utility) on each client machine.
For more information see SQL Server Browser Service on MSDN.
1433
the default port hasn't changed yet
SQL Server default port is 1434.
To allow remote access I had to release those ports on my firewall:
Protocol | Port
---------------------
UDP | 1050
TCP | 1050
TCP | 1433
UDP | 1434
You can use SQL Configuration Manager to set individual IP addresses to use dynamic ports or not (value of 0 = yes, use dynamic port), and to set the TCP port used for each IP.
But be careful: I recommend first mapping out your instances, IPs, and ports, and planning such that no instances or IPs step on each other before starting to make changes willy-nilly.
We can take a look at three different ways you can identify the port used by an instance of SQL Server.
Reading SQL Server Error Logs
Using SQL Server Configuration Manager
Using Windows Application Event Viewer
USE master
GO
xp_readerrorlog 0, 1, N'Server is listening on', 'any', NULL, NULL, N'asc'
GO
Identify Port used by SQL Server Database Engine Using SQL Server
Configuration Manager
Click Start -> Programs -> Microsoft SQL Server 2008 -> Configuration Tools -> SQL Server Configuration Manager
In SQL Server Configuration Manager, expand SQL Server Network Configuration and then select Protocols for on the
left panel. To identify the TCP/IP Port used by the SQL Server
Instance, right click onTCP/IP and select Properties from the drop
down as shown below.
For More Help
http://sqlnetcode.blogspot.com/2011/11/sql-server-identify-tcp-ip-port-being.html