A Couple of months ago I came with the issue of connecting to a SQL server instance from my vista machine (which is my dev machine)
It always gave me errors, and even after following microsofts instructions , couldnt get it to work.
However some fine print in some site (cant recall which site) instructed to turn off the windows firewall while connecting to sql server.
Has anyone come across this , and has found an alternative to this?
Seems if my clients turn to vista (Which unfortunately they are very keen to) might have to keep their firewalls off all the time.
ThanksUnfortunately I am not a network engineer but I think there is a possibility to configure a port through which connection should be established. Each server has a default port to go through but it possibly could be configured.
Don't ask me how to do it because I don't know... :)|||Sounds fair enough.
So now My target is to find which port is used to connect to the remote sql server. I presume I would have to look into network packet analyserz to find it out.
I can feel that i need to face my weakest problems (networking)
thanks a lot for that...sounds like a good direction|||Hi Again,
Followed your direction,
And installled wireshark, and got a few porst that ms sql server was trying to call. - around 3- 4 differetn ones
So went to the firewall and opened them.
Now when i retried connecting to sql server...it started to use some completely different ports...(so it port hopping or something)
There is this other wthing that i discovered, Once you turn your firewall off and connect to the remote sql, you can turn the firewall back on.
and it still works. Now if you disconnect the connection to the server, and then try to connect once again, it works fine
however if you close the management studio, then on restarting the studio, and then try connecting to the remote server, that fails.
So .... Anything that anyone can see?
Or do i post a topic on the networking forum?
cheers|||When you create DSN to the server it does show you port which server is using but I am not sure how it can help you.
I will go to work tomorrow (it is night in NY) and will ask couple of people who deal with it. If I will get more info I will get back to you.
Sorry I am not a big help here just trying to support you... :(|||Oh no...its not an issue
I have been very successful at letting my clients stick to XP, by the time the development time finishes they will still be using XP, so there isint really an issue.
But yea, thanks for your help in giving new a different perspective to this solution.|||
Quote:
Originally Posted by iburyak
When you create DSN to the server it does show you port which server is using but I am not sure how it can help you.
I will go to work tomorrow (it is night in NY) and will ask couple of people who deal with it. If I will get more info I will get back to you.
Sorry I am not a big help here just trying to support you... :(
Hi iburyak
Thanks for your reply, i chased this issue with your direction and found out the way out of it.
I have put it into an article (Waiting for the moderator to move it to the SQL server article -- yes im dumb, i put it into the .Net articles)
Connect Remote SQL instance from Vista Client
thanks a lot for the help :)|||Hey thanks for your respond.
I knew it could be done through port. :)
Be careful thou giving away port number even thou it is 1433 for SQL servers but not for Sybase, Oracle or as you said in cases when port has been changed.
I found easy way of finding port when you create a valid DSN to the server and go back to edit it in advanced screen it does show you a port number. :)
Anyway I am very happy that you solved this problem and didnt have to put your firewall down.
I knew about a port because I had to change some of my applications to Web Services which use a different port because my network administrators didnt wanted to open that port for a database access on servers.
No comments:
Post a Comment