| Author |
Topic |
|
rrb
SQLTeam Poet Laureate
1479 Posts |
 Posted - 2003-12-07 : 19:49:37
|
| Dearest,Another little foray into the evil world of Administration....Please excuse my total ignorance of this area...For many and various reasons (this is not your typical SQL Server application), the IP address of the server needs to be changed from time to time. When this happens, users who connect via an explicit IP address cannot connect to SQL Server using either the old or new IP Address, unless I restart SQL Server.In OSQL, after an initial failure to connect, the local user can connect using the new IP address, but still can't connect using ADO even on the local machine (when stating either the old or new IP address explicitly).Any ideas?Is there any way to make SQL Server recognise the new IP address, and why is ADO not able to?--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-12-08 : 02:53:31
|
| The net libraries are enumerated on server startup (those listening on.... messages in the SQL error log) and SQL will not dynamically bind to the new IP/Port without a restart. I'm guessing that osql might be falling back onto Shared Memory to connect locally, not sure why ADO won't unless you are specifying the net lib in the connection string (or it fixes on TCP/IP when an IP address is specified) ? |
 |
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2003-12-08 : 21:18:14
|
| Hi JasApparently (so my integration team guy says) applying SP2 (for SQL Server 2000) fixed the problem. You can now change the IP Address on the fly and reconnect no problems.[picture of happy guy who just wishes it was christmas break already]--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-12-09 : 03:34:21
|
| How bizarre. We're running SP3 here and changing the IP yesterday stopped connections.Ho-hum.-------Moo. :) |
|
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2003-12-09 : 20:49:33
|
| Yes, stopped the connections. But were you able to restart them? That was our issue.--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-12-10 : 06:23:52
|
| Sorry I meant, as in, prevented further connections until the machine / sql server was restarted.-------Moo. :) |
|
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2003-12-10 : 17:18:13
|
| Well that is interesting. Because now we have SP2 running, we can definitely change IP address on the fly....sounds like someone undid something they shouldn't have....--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2003-12-11 : 00:14:53
|
| I'm curious as to why you need to change the IP address of your SQL Server. If you are able to elaborate on this please do.-ec |
|
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2003-12-11 : 17:48:49
|
| You can be as curious as you like. Basically MSDE is on every laptop. Each laptop can join any network and begin serving info. Pretty straight forward really.cheers--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
|
|
Changing IP address and timeout