Hi Rick,
I'm not familiar with wireless networking but I guess the wireless port
you're referring to is something used by the machine not just SQL Server.
So, it may not be practical to turn it off.
Does it make more sense to just simply disable TCP/IP protocol for the SQL
Server in your example? My understanding is that if Listen All is Yes, the
IP1 and IP2 settings are ignored and IPAll settings are the only one used.
So, if someone has set something in IP1 and/or IP2 when Listen All is Yes, it
is still OK. However, if just simply change the Listen All to No, it will
mean IP1 and IP2 settings may have effect now. If the person forgets to turn
off the wireless port in your example, the IP1 and IP2 may become security
issues.
I was playing with the TCP/IP properties. If Listen All is Yes and I blank
out everything in IPAll and then restart SQL Server service, the cpu will run
upto 100% and need to end task.
By the way, is there any MS article or webcast to explain how to set IP1,
IP2, and IPAll?
[quoted text, click to view] "Rick Byham, (MSFT)" wrote:
> How about a Sales application running on a salespersons laptop that uses SQL
> Server replication to send orders to the home office. The laptop has a
> wireless port that is on in the coffee shop. Set Listen All to No and then
> set the wireless port to No, to reduce the chance of people sticking their
> fingers into your SQL Server.
> Configure the wired network port to Yes. The laptop can only sync with the
> home office when it has a wired connection back at the office.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Peter" <Peter@discussions.microsoft.com> wrote in message
> news:75E9EE3D-9A4E-412D-B947-BFC1566828F7@microsoft.com...
> >I want to know when someone will change Listen All to No for TCP/IP
> >Protocol
> > and set up individual IP addresses.
Maybe my example is strained. I do run SQL Server on my laptop, I'm probably
not typical.
I don't know about your 100% CPU issue. I'm not getting that.
I don't know of any MS article or webcast about this. The protocol
developers have a blog at
http://blogs.msdn.com/sql_protocols/ There may be
something in there.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "Peter" <Peter@discussions.microsoft.com> wrote in message
news:89EB85E7-771B-43CF-AE8E-98B6BE753116@microsoft.com...
> Hi Rick,
>
> I'm not familiar with wireless networking but I guess the wireless port
> you're referring to is something used by the machine not just SQL Server.
> So, it may not be practical to turn it off.
>
> Does it make more sense to just simply disable TCP/IP protocol for the SQL
> Server in your example? My understanding is that if Listen All is Yes, the
> IP1 and IP2 settings are ignored and IPAll settings are the only one used.
> So, if someone has set something in IP1 and/or IP2 when Listen All is Yes,
> it
> is still OK. However, if just simply change the Listen All to No, it will
> mean IP1 and IP2 settings may have effect now. If the person forgets to
> turn
> off the wireless port in your example, the IP1 and IP2 may become security
> issues.
>
> I was playing with the TCP/IP properties. If Listen All is Yes and I
> blank
> out everything in IPAll and then restart SQL Server service, the cpu will
> run
> upto 100% and need to end task.
>
> By the way, is there any MS article or webcast to explain how to set IP1,
> IP2, and IPAll?
>
> "Rick Byham, (MSFT)" wrote:
>
>> How about a Sales application running on a salespersons laptop that uses
>> SQL
>> Server replication to send orders to the home office. The laptop has a
>> wireless port that is on in the coffee shop. Set Listen All to No and
>> then
>> set the wireless port to No, to reduce the chance of people sticking
>> their
>> fingers into your SQL Server.
>> Configure the wired network port to Yes. The laptop can only sync with
>> the
>> home office when it has a wired connection back at the office.
>> --
>> Rick Byham (MSFT)
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Peter" <Peter@discussions.microsoft.com> wrote in message
>> news:75E9EE3D-9A4E-412D-B947-BFC1566828F7@microsoft.com...
>> >I want to know when someone will change Listen All to No for TCP/IP
>> >Protocol
>> > and set up individual IP addresses.
>>
Don't see what you're looking for? Try a search.