Hi Guys - This may fall into a connection category, but I was wondering
if you had the same problem specially when dealing with replication.
One of our clients is having the following problems:
1) My client computers can see the server computer by name and/or by IP
address
2) My server computer cannot see my client computers by name, only by IP
address which is dynamic
3) Client computers have a dynamic IP address
4) Client computers have a machine name but this name cannot be resolved by
a DNS server
Is there any way around this problem? How does SQL Server's name get
resolved in this scenario?
Since we are using merge replication and we cannot configure it if the IP on
the client is dynamic, then the name must be resolved somehow, right?
Any help will be appreciated,
Maer
Maer,
AFAIK what you're talking about should be possible using pull subscriptions.
If there are any IP issues during setup you could use a HOSTS file (on the
publisher/distributor) to help out.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||The absolute best way to do this is to
1) configure your publication for anonymous subscribers
2) use ActiveX Controls to pull your subscription. ActiveX Controls have
DistributorNetwork/DistributorAddress and PublisherNetwork/PublisherAddress
properties which allow your Subscriber to connect to your Publisher on the
fly without having to use hosts files or Client Network Utility on each
Subscriber.
"Maer" <maer@.auditleverage.com> wrote in message
news:uZ9xkrS6FHA.3976@.TK2MSFTNGP15.phx.gbl...
> Hi Guys - This may fall into a connection category, but I was wondering
> if you had the same problem specially when dealing with replication.
> One of our clients is having the following problems:
> 1) My client computers can see the server computer by name and/or by IP
> address
> 2) My server computer cannot see my client computers by name, only by IP
> address which is dynamic
> 3) Client computers have a dynamic IP address
> 4) Client computers have a machine name but this name cannot be resolved
> by a DNS server
> Is there any way around this problem? How does SQL Server's name get
> resolved in this scenario?
> Since we are using merge replication and we cannot configure it if the IP
> on the client is dynamic, then the name must be resolved somehow, right?
> Any help will be appreciated,
> Maer
>
>
|||I think you got a DNS problem.
If you are using VPN you can consider changing your VPN properties so it
registers in the DNS server or fixing the IP Address for the dial up user.
Also, using pull anonymous subscriptions your publisher does not need to be
to 'get' to your subscribers.
Jos.
"Maer" <maer@.auditleverage.com> wrote in message
news:uZ9xkrS6FHA.3976@.TK2MSFTNGP15.phx.gbl...
> Hi Guys - This may fall into a connection category, but I was
wondering
> if you had the same problem specially when dealing with replication.
> One of our clients is having the following problems:
> 1) My client computers can see the server computer by name and/or by IP
> address
> 2) My server computer cannot see my client computers by name, only by IP
> address which is dynamic
> 3) Client computers have a dynamic IP address
> 4) Client computers have a machine name but this name cannot be resolved
by
> a DNS server
> Is there any way around this problem? How does SQL Server's name get
> resolved in this scenario?
> Since we are using merge replication and we cannot configure it if the IP
on
> the client is dynamic, then the name must be resolved somehow, right?
> Any help will be appreciated,
> Maer
>
>
Showing posts with label resolution. Show all posts
Showing posts with label resolution. Show all posts
Friday, March 23, 2012
name resolution (WINS/DNS)
How does the name of a datasource get resolved?
I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links
. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location.
For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged.
However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advanceRE:
How does the name of a datasource get resolved? I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location. For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged. However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advance
S1: Aspects of the situation strike me as potentially 'radioactive'.
S2: I strongly suggest you work closely with your friendly network engineer e.g. (look out for looping and things like that), and carefully test whatever schemes you test / work out (working toghther). What will work depends on how the entire environment is configured. Be sure to take into full consideration any and all things that might be involved or interact with potential solutions at any level, e.g.(like VPNs, dial ups, and other connections between sites).
S3: Alternative general approaches that may be workable (or not, and in any event potentially reckless, if you just 'dive in'):
i) Add site logon scripts that strip any locally cached and/or stored references to DBServer from when the (roaming laptop) was at other sites e.g.(including dsns, added routes, Hosts, lmhosts, arp, etc. data and other entries that may be applicable in your environment).
ii) Bind all the ips of the various DBServers to each and every DBServer.sql
I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links
. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location.
For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged.
However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advanceRE:
How does the name of a datasource get resolved? I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location. For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged. However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advance
S1: Aspects of the situation strike me as potentially 'radioactive'.
S2: I strongly suggest you work closely with your friendly network engineer e.g. (look out for looping and things like that), and carefully test whatever schemes you test / work out (working toghther). What will work depends on how the entire environment is configured. Be sure to take into full consideration any and all things that might be involved or interact with potential solutions at any level, e.g.(like VPNs, dial ups, and other connections between sites).
S3: Alternative general approaches that may be workable (or not, and in any event potentially reckless, if you just 'dive in'):
i) Add site logon scripts that strip any locally cached and/or stored references to DBServer from when the (roaming laptop) was at other sites e.g.(including dsns, added routes, Hosts, lmhosts, arp, etc. data and other entries that may be applicable in your environment).
ii) Bind all the ips of the various DBServers to each and every DBServer.sql
Subscribe to:
Posts (Atom)