June 15, 2009 at 1:30 am
Dear All,
How to redirect a port in sql server
Thanx
Thanks
June 15, 2009 at 3:58 am
guptaajay1985 (6/15/2009)
Dear All,How to redirect a port in sql server
Thanx
Not sure if I understand your question correct, but if you want to change the port which is used by SQL server you can do t thisway:
1. Open the SQL Server Configuration Manager
2. Go to Network Configuration and select TCP/ip for your instance
3. Open the properties of TCP\Ip and go to the tab IP addresses.
4. Under IP all change the prot to the number you want.
5. Restart SQL Server
[font="Verdana"]Markus Bohse[/font]
June 15, 2009 at 4:01 am
Dear,
Thancs for response.My requirement is that sql server will work on 1433 but the port which the developer use is not 1433 other than this.
Thanks
June 15, 2009 at 4:02 am
can u elaborate ur requirement ?
June 15, 2009 at 4:05 am
I'm also not sure if I understood you. If your developers are on same SQL Server as your production system it's not possible to configure two different ports for one instance. Either install an additional SQL Server instance on your server or use a second server.
Flo
June 15, 2009 at 4:05 am
Do u want SQL server to listen to two TCP/IP ports or u need to cnfigure ur client PC connect using a port ?
June 15, 2009 at 4:08 am
Its possible to configure a single SQL server(default ) to listen two TCP/Ip ports 🙂
June 15, 2009 at 4:12 am
rajganesh.dba (6/15/2009)
Its possible to configure a single SQL server(default ) to listen two TCP/Ip ports 🙂
Really? From SQL Server (not NAT)? Well, learned something new.
My DBAs doin' this for me. :hehe:
June 15, 2009 at 4:39 am
Redirect means if request is coming on 1433 then I will redirect it to 1436
Thanks
June 15, 2009 at 5:20 am
port forwarding is not handled by SQL Server, it is typically handled by a router that establishes the firewall between your internal network and the internet.
here's a screen shot of an example:
this is a list of the typical ports that are being passed thru to an internal network. this happens to be a netgear home network.
In this case, there's no passthru to SQL server,but all I would do is decide which port sql server will listen to on my internal network(say 4436, change it, and then add an item to my firewall to direct any port traffic on 4436 to a specific IP address on my internal network.
It's outside of SQL server, which is where the confusion is coming from.
Does that help?
Lowell
June 15, 2009 at 5:23 am
Then why we use alias can anyone clarify
Thanks
June 15, 2009 at 5:41 am
guptaajay1985 (6/15/2009)
Then why we use alias can anyone clarify
alias? I'm not clear on your question. which alias are you referring to?
You might use port forwarding because you have 10 servers on your network, but only one external IP address. In that case, you might redirect port 4413 to one server, 4436 to yet another, and so on,if you really needed them exposed to the internet. that way different services on multiple servers can be exposed through the firewall.
Lowell
June 15, 2009 at 6:03 am
Dear Lowell
May be it is called port forwarding, I just want to give my developers other port than 1433 yet sql server service should run on 1433 as it is...
Thanks
June 15, 2009 at 6:17 am
if your developers are on the same network, then I don't believe it can be done.
each instance of SQL server listens to one port...no problem.
a router can take traffic from port 4436, and point it at your SQL servers 4413, sure....but the traffic has to come from some other network.
If your network is set like my example, so that my network occupies 255 IP addresses, from 192.168.1.1 thru .254, then my router will consider anything outside that range as IP's that have to go thru the Network Address Translation and port forwarding scheme.
if the developers IP's are inside that IP range, due to the way networking is handled, they will not be port forwarded.
double check: do you have two instances of SQL installed, a default and a named instance, and you want the developers to use the named instance(which is on a different port) instead of the default "production" instance? is THAT the question?
can you explain WHY you want developers to go thru a different port? that might clarify any solutions we can offer, if we understand what you are trying to do, instead of how you are trying to do it.
Lowell
June 15, 2009 at 10:21 pm
In my scenario actually the customers are the developers and we have given them the freedom to design queries and DB as they want yet We don't want to give use of 1433 to them...
Thanks
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply