Ok, I'm knee-deep in replication-hell.
I'm trying to set up snapshot replication between two SQL Server 2000 databases over the internet. Both servers run Windows 2000 server edition and SQL server 2000. The idea is to send certain local information, stored in database tables to a database from which the information is published on a website.
I've set up the distribution database (with the original name: distribution) and connected a publisher to it (let's call that one "source_database") using the sp_adddistpublisher stored procedure. No problems there...
Next step, I added a publication, the tables in source_database, and a subscriber, the website database. I've opened up port 1433 on both servers, but still it won't send anything from the source_database to the website database...
It gives no errors, but just doesn't do anything...
Now, I've looked for possible problems and I think these problems might be able to cause problems:
- The initial snapshot is not reaching the subscriber
- I've made a push subscription which may has to become a pull subscription
- The RPC's aren't available, because both servers are highly secured
- The wrong serverpack is installed (this one is a wild guess)
Does anybody have any idea on how I can get my distribution working or solve any of the problems above, cause I'm running out of idea's...
(P.S. I'm a bit of a noobie to replication, I've set it up in a test environment before and it just worked perfectly, but the real thing isn't)You may have already done it, but just to make sure that you have define the publisher and the subscriber in the source server, right? Does your source server know the network id of the target server? Simply try to register the target server's name on EM of the source to see.|||Service pack will get you bad. I experimented with 2 servers running 194 and 818 builds, and was getting nothing, no matter what I tried. And when you apply SP3 you'd notice that there are scripts that directly affect replication (repl*.sql)|||I solved the problem...
It did turn out to be the service pack.
Sp3a was installed by a sys-admin, but not correctly.
After re-installing Sp3a everything just started working.
Man, I'm glad that one's solved, I had like 5 minutes left till insanity... :cool:
Anyhow, thanx for the help...|||Man, I'm glad that one's solved, I had like 5 minutes left till insanity... :cool: Oh, so you aren't really a dba yet? Actually, once I gave up on the sanity part, the rest seemed a lot easier!
-PatP
Showing posts with label internet. Show all posts
Showing posts with label internet. Show all posts
Monday, March 26, 2012
Tuesday, March 20, 2012
Replication and security..is it really this UNSECURE!
Hi Guys
I need to create an anonymous pull subscription over the Internet.
I've got everything working but I don't want my subscribers to be able
to connect to the publisher/distributor via Enterprise Manager or
ISQLW or anything else for that matter!! Basically they should only
be able to talk to the Publishing SQL Server through replication
methods. How is this achieved?
I'm currently using SQL Security because I don't want an anonymous
subscriber to impersonate my publishers sqlserver agent account, the
agent on the publisher is used for other scheduled tasks that needs
Domain Admin privileges, am I missing something here!!'
Currently I've got it secure-ish. I've used a specific sql account
and given it access in the PAL and removed the guest account from
other DBs, however you cannot remove the guest account from Master or
Msdb and said account must also be a member of the db_owner role. The
most they can do is issue select statements against tables but I think
that is even too much, for instance they can query sysservers which
would allow them to see other subscribers that we do business with.
Even if I use a secure VPN between publisher and subscriber what's to
stop an inquistive subscriber, using the SQL account that I've told
them to use for their subscription, connecting using EM or ISQLW
through the VPN? Surely there must be a way to give ONLY replication
access but nothing else?
Please help!!What type of Replication are you implementing? Snapshot/Transactional or
Merge ?
If they have the data on the Subscriber, there would really be no need to
connect to the Publisher. So, if the users are connecting to the
Subscribing database, that's all they should need.
Are you attempting to restrict access to the Subscribed database?
There isn't a way to restrict access FROM a particular application. So, if
you allow the user to connect to the Server and grant them access to the
database, then they have access from *any* odbc or oledb application.
There isn't a way to restrict this.
Replication works using the accounts designated with the Agents. It
doesn't rely on what permissions the users have.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
I need to create an anonymous pull subscription over the Internet.
I've got everything working but I don't want my subscribers to be able
to connect to the publisher/distributor via Enterprise Manager or
ISQLW or anything else for that matter!! Basically they should only
be able to talk to the Publishing SQL Server through replication
methods. How is this achieved?
I'm currently using SQL Security because I don't want an anonymous
subscriber to impersonate my publishers sqlserver agent account, the
agent on the publisher is used for other scheduled tasks that needs
Domain Admin privileges, am I missing something here!!'
Currently I've got it secure-ish. I've used a specific sql account
and given it access in the PAL and removed the guest account from
other DBs, however you cannot remove the guest account from Master or
Msdb and said account must also be a member of the db_owner role. The
most they can do is issue select statements against tables but I think
that is even too much, for instance they can query sysservers which
would allow them to see other subscribers that we do business with.
Even if I use a secure VPN between publisher and subscriber what's to
stop an inquistive subscriber, using the SQL account that I've told
them to use for their subscription, connecting using EM or ISQLW
through the VPN? Surely there must be a way to give ONLY replication
access but nothing else?
Please help!!What type of Replication are you implementing? Snapshot/Transactional or
Merge ?
If they have the data on the Subscriber, there would really be no need to
connect to the Publisher. So, if the users are connecting to the
Subscribing database, that's all they should need.
Are you attempting to restrict access to the Subscribed database?
There isn't a way to restrict access FROM a particular application. So, if
you allow the user to connect to the Server and grant them access to the
database, then they have access from *any* odbc or oledb application.
There isn't a way to restrict this.
Replication works using the accounts designated with the Agents. It
doesn't rely on what permissions the users have.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Replication and security..is it really this UNSECURE!
Hi Guys
I need to create an anonymous pull subscription over the Internet.
I've got everything working but I don't want my subscribers to be able
to connect to the publisher/distributor via Enterprise Manager or
ISQLW or anything else for that matter!! Basically they should only
be able to talk to the Publishing SQL Server through replication
methods. How is this achieved?
I'm currently using SQL Security because I don't want an anonymous
subscriber to impersonate my publishers sqlserver agent account, the
agent on the publisher is used for other scheduled tasks that needs
Domain Admin privileges, am I missing something here!!?
Currently I've got it secure-ish. I've used a specific sql account
and given it access in the PAL and removed the guest account from
other DBs, however you cannot remove the guest account from Master or
Msdb and said account must also be a member of the db_owner role. The
most they can do is issue select statements against tables but I think
that is even too much, for instance they can query sysservers which
would allow them to see other subscribers that we do business with.
Even if I use a secure VPN between publisher and subscriber what's to
stop an inquistive subscriber, using the SQL account that I've told
them to use for their subscription, connecting using EM or ISQLW
through the VPN? Surely there must be a way to give ONLY replication
access but nothing else?
Please help!!
The problem is not with replication and security, but rather a larger one
with SQL Server security in general. Anytime you create an account on that
server, and give that account rights to only one user database, this account
can query system tables on the master database.
I suggest you post this question to the microsoft.public.sqlserver.security
newsgroup.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"greedo" <d8rrylf@.msn.com> wrote in message
news:f0badc7a.0408170010.47baef00@.posting.google.c om...
> Hi Guys
> I need to create an anonymous pull subscription over the Internet.
> I've got everything working but I don't want my subscribers to be able
> to connect to the publisher/distributor via Enterprise Manager or
> ISQLW or anything else for that matter!! Basically they should only
> be able to talk to the Publishing SQL Server through replication
> methods. How is this achieved?
> I'm currently using SQL Security because I don't want an anonymous
> subscriber to impersonate my publishers sqlserver agent account, the
> agent on the publisher is used for other scheduled tasks that needs
> Domain Admin privileges, am I missing something here!!?
> Currently I've got it secure-ish. I've used a specific sql account
> and given it access in the PAL and removed the guest account from
> other DBs, however you cannot remove the guest account from Master or
> Msdb and said account must also be a member of the db_owner role. The
> most they can do is issue select statements against tables but I think
> that is even too much, for instance they can query sysservers which
> would allow them to see other subscribers that we do business with.
> Even if I use a secure VPN between publisher and subscriber what's to
> stop an inquistive subscriber, using the SQL account that I've told
> them to use for their subscription, connecting using EM or ISQLW
> through the VPN? Surely there must be a way to give ONLY replication
> access but nothing else?
> Please help!!
I need to create an anonymous pull subscription over the Internet.
I've got everything working but I don't want my subscribers to be able
to connect to the publisher/distributor via Enterprise Manager or
ISQLW or anything else for that matter!! Basically they should only
be able to talk to the Publishing SQL Server through replication
methods. How is this achieved?
I'm currently using SQL Security because I don't want an anonymous
subscriber to impersonate my publishers sqlserver agent account, the
agent on the publisher is used for other scheduled tasks that needs
Domain Admin privileges, am I missing something here!!?
Currently I've got it secure-ish. I've used a specific sql account
and given it access in the PAL and removed the guest account from
other DBs, however you cannot remove the guest account from Master or
Msdb and said account must also be a member of the db_owner role. The
most they can do is issue select statements against tables but I think
that is even too much, for instance they can query sysservers which
would allow them to see other subscribers that we do business with.
Even if I use a secure VPN between publisher and subscriber what's to
stop an inquistive subscriber, using the SQL account that I've told
them to use for their subscription, connecting using EM or ISQLW
through the VPN? Surely there must be a way to give ONLY replication
access but nothing else?
Please help!!
The problem is not with replication and security, but rather a larger one
with SQL Server security in general. Anytime you create an account on that
server, and give that account rights to only one user database, this account
can query system tables on the master database.
I suggest you post this question to the microsoft.public.sqlserver.security
newsgroup.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"greedo" <d8rrylf@.msn.com> wrote in message
news:f0badc7a.0408170010.47baef00@.posting.google.c om...
> Hi Guys
> I need to create an anonymous pull subscription over the Internet.
> I've got everything working but I don't want my subscribers to be able
> to connect to the publisher/distributor via Enterprise Manager or
> ISQLW or anything else for that matter!! Basically they should only
> be able to talk to the Publishing SQL Server through replication
> methods. How is this achieved?
> I'm currently using SQL Security because I don't want an anonymous
> subscriber to impersonate my publishers sqlserver agent account, the
> agent on the publisher is used for other scheduled tasks that needs
> Domain Admin privileges, am I missing something here!!?
> Currently I've got it secure-ish. I've used a specific sql account
> and given it access in the PAL and removed the guest account from
> other DBs, however you cannot remove the guest account from Master or
> Msdb and said account must also be a member of the db_owner role. The
> most they can do is issue select statements against tables but I think
> that is even too much, for instance they can query sysservers which
> would allow them to see other subscribers that we do business with.
> Even if I use a secure VPN between publisher and subscriber what's to
> stop an inquistive subscriber, using the SQL account that I've told
> them to use for their subscription, connecting using EM or ISQLW
> through the VPN? Surely there must be a way to give ONLY replication
> access but nothing else?
> Please help!!
Monday, March 12, 2012
Replication across the internet
Hi,
I want to replicate my data with a sql server in internet(via dial-up
connection).
Do I necessarily need to use FTP for transferring the initial snapshots or
it is an alternate solution?
I saw this in article number '321822' in Microsoft's site, the second
example in this article mentions:
Example 2: The Subscriber Does Not Have the Schema and Data, and the Initial
Subscription from the Publisher Is Required.
This example requires you to configure the FTP service at the Publisher, and
then configure the Subscriber to download the initial snapshot from the FTP
site. For more information, see the following topics in SQL Server Books
Online...
Thanks in advance,
Amin
you don't need to. Somehow you need to get the schema and data to the
subscriber. You can't use a UNC, so you have to use FTP, or get them there
via mail, courier or some other system.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Amin Sobati" <amins@.morva.net> wrote in message
news:OddhXyBXEHA.3640@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I want to replicate my data with a sql server in internet(via dial-up
> connection).
> Do I necessarily need to use FTP for transferring the initial snapshots or
> it is an alternate solution?
> I saw this in article number '321822' in Microsoft's site, the second
> example in this article mentions:
> --
> Example 2: The Subscriber Does Not Have the Schema and Data, and the
Initial
> Subscription from the Publisher Is Required.
> This example requires you to configure the FTP service at the Publisher,
and
> then configure the Subscriber to download the initial snapshot from the
FTP
> site. For more information, see the following topics in SQL Server Books
> Online...
> --
> Thanks in advance,
> Amin
>
|||Hilary,
If I'm creating a push subscription, and my publisher is distributor too,
then I suppose the snapshot on my local hard drive can be used by merge
agent, is it correct?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OQ#8NYLXEHA.2844@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> you don't need to. Somehow you need to get the schema and data to the
> subscriber. You can't use a UNC, so you have to use FTP, or get them there
> via mail, courier or some other system.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:OddhXyBXEHA.3640@.TK2MSFTNGP11.phx.gbl...
or
> Initial
> and
> FTP
>
|||The distributor doesn't really factor into merge replication other than
being a repository where historical information is held.
You should be using a PULL subscription when you are replicating over the
internet. If you open the NetBIOS (IIRC) necessary for a push subscription
you are exposing your self to hackers.
"Amin Sobati" <amins@.morva.net> wrote in message
news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hilary,
> If I'm creating a push subscription, and my publisher is distributor too,
> then I suppose the snapshot on my local hard drive can be used by merge
> agent, is it correct?
> Thanks,
> Amin
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:OQ#8NYLXEHA.2844@.TK2MSFTNGP11.phx.gbl...
there[vbcol=seagreen]
snapshots[vbcol=seagreen]
> or
Publisher,[vbcol=seagreen]
the[vbcol=seagreen]
Books
>
|||Hilary,
I'm only the owner of the database at subscriber, and there's some errors
while trying to create pull subscription. Our sql server host(subscriber)
has added my publisher name(computer name) as a remote server and mapped all
of our logins(local) to the login which was created at their sql server. But
still there're some error indicating the loss of permissions.
What's the best solution?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:#7ZT5bQXEHA.2364@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> The distributor doesn't really factor into merge replication other than
> being a repository where historical information is held.
> You should be using a PULL subscription when you are replicating over the
> internet. If you open the NetBIOS (IIRC) necessary for a push subscription
> you are exposing your self to hackers.
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...
too,[vbcol=seagreen]
> there
dial-up[vbcol=seagreen]
> snapshots
second
> Publisher,
> the
> Books
>
|||Hilary,
I'm only the owner of the database at subscriber, and there's some errors
while trying to create pull subscription. Our sql server host(subscriber)
has added my publisher name(computer name) as a remote server and mapped all
of our logins(local) to the login which was created at their sql server. But
still there're some error indicating the loss of permissions.
What's the best solution?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:#7ZT5bQXEHA.2364@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> The distributor doesn't really factor into merge replication other than
> being a repository where historical information is held.
> You should be using a PULL subscription when you are replicating over the
> internet. If you open the NetBIOS (IIRC) necessary for a push subscription
> you are exposing your self to hackers.
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...
too,[vbcol=seagreen]
> there
dial-up[vbcol=seagreen]
> snapshots
second
> Publisher,
> the
> Books
>
I want to replicate my data with a sql server in internet(via dial-up
connection).
Do I necessarily need to use FTP for transferring the initial snapshots or
it is an alternate solution?
I saw this in article number '321822' in Microsoft's site, the second
example in this article mentions:
Example 2: The Subscriber Does Not Have the Schema and Data, and the Initial
Subscription from the Publisher Is Required.
This example requires you to configure the FTP service at the Publisher, and
then configure the Subscriber to download the initial snapshot from the FTP
site. For more information, see the following topics in SQL Server Books
Online...
Thanks in advance,
Amin
you don't need to. Somehow you need to get the schema and data to the
subscriber. You can't use a UNC, so you have to use FTP, or get them there
via mail, courier or some other system.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Amin Sobati" <amins@.morva.net> wrote in message
news:OddhXyBXEHA.3640@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I want to replicate my data with a sql server in internet(via dial-up
> connection).
> Do I necessarily need to use FTP for transferring the initial snapshots or
> it is an alternate solution?
> I saw this in article number '321822' in Microsoft's site, the second
> example in this article mentions:
> --
> Example 2: The Subscriber Does Not Have the Schema and Data, and the
Initial
> Subscription from the Publisher Is Required.
> This example requires you to configure the FTP service at the Publisher,
and
> then configure the Subscriber to download the initial snapshot from the
FTP
> site. For more information, see the following topics in SQL Server Books
> Online...
> --
> Thanks in advance,
> Amin
>
|||Hilary,
If I'm creating a push subscription, and my publisher is distributor too,
then I suppose the snapshot on my local hard drive can be used by merge
agent, is it correct?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OQ#8NYLXEHA.2844@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> you don't need to. Somehow you need to get the schema and data to the
> subscriber. You can't use a UNC, so you have to use FTP, or get them there
> via mail, courier or some other system.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:OddhXyBXEHA.3640@.TK2MSFTNGP11.phx.gbl...
or
> Initial
> and
> FTP
>
|||The distributor doesn't really factor into merge replication other than
being a repository where historical information is held.
You should be using a PULL subscription when you are replicating over the
internet. If you open the NetBIOS (IIRC) necessary for a push subscription
you are exposing your self to hackers.
"Amin Sobati" <amins@.morva.net> wrote in message
news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hilary,
> If I'm creating a push subscription, and my publisher is distributor too,
> then I suppose the snapshot on my local hard drive can be used by merge
> agent, is it correct?
> Thanks,
> Amin
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:OQ#8NYLXEHA.2844@.TK2MSFTNGP11.phx.gbl...
there[vbcol=seagreen]
snapshots[vbcol=seagreen]
> or
Publisher,[vbcol=seagreen]
the[vbcol=seagreen]
Books
>
|||Hilary,
I'm only the owner of the database at subscriber, and there's some errors
while trying to create pull subscription. Our sql server host(subscriber)
has added my publisher name(computer name) as a remote server and mapped all
of our logins(local) to the login which was created at their sql server. But
still there're some error indicating the loss of permissions.
What's the best solution?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:#7ZT5bQXEHA.2364@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> The distributor doesn't really factor into merge replication other than
> being a repository where historical information is held.
> You should be using a PULL subscription when you are replicating over the
> internet. If you open the NetBIOS (IIRC) necessary for a push subscription
> you are exposing your self to hackers.
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...
too,[vbcol=seagreen]
> there
dial-up[vbcol=seagreen]
> snapshots
second
> Publisher,
> the
> Books
>
|||Hilary,
I'm only the owner of the database at subscriber, and there's some errors
while trying to create pull subscription. Our sql server host(subscriber)
has added my publisher name(computer name) as a remote server and mapped all
of our logins(local) to the login which was created at their sql server. But
still there're some error indicating the loss of permissions.
What's the best solution?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:#7ZT5bQXEHA.2364@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> The distributor doesn't really factor into merge replication other than
> being a repository where historical information is held.
> You should be using a PULL subscription when you are replicating over the
> internet. If you open the NetBIOS (IIRC) necessary for a push subscription
> you are exposing your self to hackers.
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...
too,[vbcol=seagreen]
> there
dial-up[vbcol=seagreen]
> snapshots
second
> Publisher,
> the
> Books
>
Saturday, February 25, 2012
Replication
We have two systems one that has a domain setup and the other is a workgroup. We have them connected over a non-trusted internet connection. We are using SQL Server 2005 Enterprise version, for Peer-to-Peer transactional replication, the server that hasa domain, is called EXT-FRMAC1 and the other one is FRMAC_DC. FRMAC_DC can subscribe to EXT-FRMAC1's publication, but EXT-FRMAC1 can't subscribe to FRMAC_DC, and the error that we get on FRMAC_DC, is that FRMAC_DC\admin - username or password does not exist. admin exists on FRMAC_DC, I am not sure if we should try and put it on a domain or not.
Thanks.
Have you tried to setup with a SQL server account instead of Windows account?
Gary
Replicating to over 70 databases...why??
Is this reasonable or is this poor design...why not just a few power servers
and all users have high speed internet connections or at least DSL'
Thanks
Ken S.Think you will have to explain your situation a little more to get any good
feedback
Ray Higdon MCSE, MCDBA, CCNA
--
"SMAN" <ksanti@.nycap.rr.com> wrote in message
news:O1ct4n9AEHA.2404@.TK2MSFTNGP11.phx.gbl...
> Is this reasonable or is this poor design...why not just a few power
servers
> and all users have high speed internet connections or at least DSL'
> Thanks
> Ken S.
>
and all users have high speed internet connections or at least DSL'
Thanks
Ken S.Think you will have to explain your situation a little more to get any good
feedback
Ray Higdon MCSE, MCDBA, CCNA
--
"SMAN" <ksanti@.nycap.rr.com> wrote in message
news:O1ct4n9AEHA.2404@.TK2MSFTNGP11.phx.gbl...
> Is this reasonable or is this poor design...why not just a few power
servers
> and all users have high speed internet connections or at least DSL'
> Thanks
> Ken S.
>
Replicating to over 70 databases...why??
Is this reasonable or is this poor design...why not just a few power servers
and all users have high speed internet connections or at least DSL'
Thanks
Ken S.Think you will have to explain your situation a little more to get any good
feedback
--
Ray Higdon MCSE, MCDBA, CCNA
--
"SMAN" <ksanti@.nycap.rr.com> wrote in message
news:O1ct4n9AEHA.2404@.TK2MSFTNGP11.phx.gbl...
> Is this reasonable or is this poor design...why not just a few power
servers
> and all users have high speed internet connections or at least DSL'
> Thanks
> Ken S.
>
and all users have high speed internet connections or at least DSL'
Thanks
Ken S.Think you will have to explain your situation a little more to get any good
feedback
--
Ray Higdon MCSE, MCDBA, CCNA
--
"SMAN" <ksanti@.nycap.rr.com> wrote in message
news:O1ct4n9AEHA.2404@.TK2MSFTNGP11.phx.gbl...
> Is this reasonable or is this poor design...why not just a few power
servers
> and all users have high speed internet connections or at least DSL'
> Thanks
> Ken S.
>
Subscribe to:
Posts (Atom)