| SQL Dev- connect to Win Server 2012 [message #620262] |
Wed, 30 July 2014 14:23  |
 |
oragami
Messages: 16
Registered: July 2014
|
Junior Member |
|
|
Hi.
Can anyone help me please. I am trying to connect as a client to my win 2012 server. I establish a connection np as localhost on my production box as sysdba
by when I try to connect as sysdba via the client it doesn't recognize my user name/password. I connect in the same manner in SQL Dev as SYSDBA (which is the role I chose).
I have port forwarded (in/out going ports) 1521 on my router.
What exactly should I choose when I login as a client in Developer as far a a Connection? Basic/tns/advanced. If tns or advanced (which asks for jdbc driver??) how can I set that up?
Do I need to tweak any tns or listener ora files on my server box?
Many, many thanks for any help!
-oragami
|
|
|
|
|
|
|
|
|
|
| Re: SQL Dev- connect to Win Server 2012 [message #620955 is a reply to message #620280] |
Thu, 07 August 2014 08:07  |
 |
EdStevens
Messages: 1376
Registered: September 2013
|
Senior Member |
|
|
BlackSwan
In general yes, however ..
ping uses icmp and not tcp, and a different port. So it is possible that ping will fail while a sqlnet connect could still work. I have had networks where the NA blocked ping in an effort to foil network probing.
Probably a better test would be to telnet on port 1521.
The fact that the OP reported "when I try to connect as sysdba via the client it doesn't recognize my user name/password." seems to suggest the tns traffic on tcp IS going through, else it would not have gotten far enough to reject a password.
[Updated on: Thu, 07 August 2014 08:08] Report message to a moderator |
|
|
|
| Re: SQL Dev- connect to Win Server 2012 [message #620958 is a reply to message #620262] |
Thu, 07 August 2014 08:15 |
|
EdStevens
Messages: 1376
Registered: September 2013
|
Senior Member |
|
|
oragami wrote on Wed, 30 July 2014 14:23Hi.
Can anyone help me please. I am trying to connect as a client to my win 2012 server. I establish a connection np as localhost on my production box as sysdba
by when I try to connect as sysdba via the client it doesn't recognize my user name/password.
The fact that it got far enough to reject a password suggests the network config is ok, in spite of your ping results. See my reply to Black Swan on that.
Quote:I connect in the same manner in SQL Dev as SYSDBA (which is the role I chose).
I have port forwarded (in/out going ports) 1521 on my router.
Many, most DBAs consider a remote client connection as SYSDBA to be a security hole and do not allow it. I'm in that camp myself.
Quote:What exactly should I choose when I login as a client in Developer as far a a Connection? Basic/tns/advanced. If tns or advanced (which asks for jdbc driver??) how can I set that up?
Do I need to tweak any tns or listener ora files on my server box?
Which method you choose is your choice. You have to supply the requested fields with values that are appropriate to your situation. If you choose tns, you have to supply a value that is listed in your tnsnames.ora. There will be a drop-down list to choose from. If the database you need is not in the list, you need to add it to your tnsnames.ora file first. If you choose 'basic', you have to supply host name, port, and sid or service name, as is appropriate. I can't tell you what those values are, because they are specific to your installation. I can tell you that 'localhost' is NOT correct.
Many, many thanks for any help!
-oragami[/quote]
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
