| Author |
Message |
Phil
Guest
|
 Posted:
Mon Jan 10, 2005 5:22 pm Post subject:
Adding Bluetooth to a SBS2003 network |
|
|
Hi,
I manage a client's network which is composed of an SBS2003 server with XP
clients. The network looks like this:
Clients DC Server NAT/router
|------| |---| |---|
|-----------| ->public internet
192.x network <- NAT -> 172.x network
DHCP
So all client traffic runs through the multi-homed sbs server first, then on
through the edge firewall/router. This all works just fine, but the client
has asked for the ability to use a bluetooth PDA to access the internet &
sync with outlook. I have a bluetooth dongle that could be used for that
purpose.
So now the question(s):
1) How best to do this? My first thought was to install the dongle on a
client, and use activesync in the normal way...but it appears that ICS
cannot be enabled on client machines as it would fix the IP of the NIC (the
clients currently use dynamic addresses).
2) If I can't do this on the client PC, can I install the dongle on the
server? What do I need to do?
3) following on from point 2, from a security point of view, is this a sane
thing to do? It appears that the connection can be locked down to some
degree, but my experience is limited with bluetooth, so anyone know better?
Help and comments much appreciated!
Phil |
|
| Back to top |
|
 |
Dmitry Korolyov [MVP]
Guest
|
| Posted:
Mon Jan 10, 2005 7:06 pm Post subject:
Re: Adding Bluetooth to a SBS2003 network |
|
|
Try installing the bluetooth device on the client machine, configuring the
current network connection as a shared connection, and newly-installed
bluetooth network connection as a private network for that shared
connection. The IP configuration of the private network would be changed to
use 192.168.0.1 on the ICS host machine, while any connecting bluetooth
clients will automatically receive IP configuration from 192.168.0.0/24
network and will connect through ICS.
--
Dmitry Korolyov [d__k@removethispart.mail.ru]
MVP: Windows Server - Directory Services
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:VztEd.197$SN.73@newsfe6-gui.ntli.net...
| Quote: | Hi,
I manage a client's network which is composed of an SBS2003 server with XP
clients. The network looks like this:
Clients DC Server NAT/router
|------| |---| |---|
|-----------| ->public internet
192.x network <- NAT -> 172.x network
DHCP
So all client traffic runs through the multi-homed sbs server first, then
on
through the edge firewall/router. This all works just fine, but the client
has asked for the ability to use a bluetooth PDA to access the internet &
sync with outlook. I have a bluetooth dongle that could be used for that
purpose.
So now the question(s):
1) How best to do this? My first thought was to install the dongle on a
client, and use activesync in the normal way...but it appears that ICS
cannot be enabled on client machines as it would fix the IP of the NIC
(the
clients currently use dynamic addresses).
2) If I can't do this on the client PC, can I install the dongle on the
server? What do I need to do?
3) following on from point 2, from a security point of view, is this a
sane
thing to do? It appears that the connection can be locked down to some
degree, but my experience is limited with bluetooth, so anyone know
better?
Help and comments much appreciated!
Phil
|
|
|
| Back to top |
|
|
Phil
Guest
|
| Posted:
Mon Jan 10, 2005 8:25 pm Post subject:
Re: Adding Bluetooth to a SBS2003 network |
|
|
Dmitry,
That was pretty much the line I was going down initially, but I see a few
problems here:
- if ICS can only use 192.168.0.1 as the NIC address, that presumably means
that only one ICS PC can be on that network, and only one dongle can be
used..? Can the fixed IP used by ICS be changed?
- my ignorance here, but the ICS tab on the client is disabled ('disabled by
group policy'). How can I reenable this? I couldn't find any policy setting
for this on the server.
Thanks for your help.
Phil
"Dmitry Korolyov [MVP]" <d__k@removethispart.mail.ru> wrote in message
news:eJbBDVx9EHA.2804@TK2MSFTNGP15.phx.gbl...
| Quote: | Try installing the bluetooth device on the client machine, configuring the
current network connection as a shared connection, and newly-installed
bluetooth network connection as a private network for that shared
connection. The IP configuration of the private network would be changed
to
use 192.168.0.1 on the ICS host machine, while any connecting bluetooth
clients will automatically receive IP configuration from 192.168.0.0/24
network and will connect through ICS.
--
Dmitry Korolyov [d__k@removethispart.mail.ru]
MVP: Windows Server - Directory Services
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:VztEd.197$SN.73@newsfe6-gui.ntli.net...
Hi,
I manage a client's network which is composed of an SBS2003 server with
XP
clients. The network looks like this:
Clients DC Server NAT/router
|------| |---| |---|
|-----------| ->public internet
192.x network <- NAT -> 172.x network
DHCP
So all client traffic runs through the multi-homed sbs server first,
then
on
through the edge firewall/router. This all works just fine, but the
client
has asked for the ability to use a bluetooth PDA to access the internet
&
sync with outlook. I have a bluetooth dongle that could be used for that
purpose.
So now the question(s):
1) How best to do this? My first thought was to install the dongle on a
client, and use activesync in the normal way...but it appears that ICS
cannot be enabled on client machines as it would fix the IP of the NIC
(the
clients currently use dynamic addresses).
2) If I can't do this on the client PC, can I install the dongle on the
server? What do I need to do?
3) following on from point 2, from a security point of view, is this a
sane
thing to do? It appears that the connection can be locked down to some
degree, but my experience is limited with bluetooth, so anyone know
better?
Help and comments much appreciated!
Phil
|
|
|
| Back to top |
|
|
Dmitry Korolyov [MVP]
Guest
|
| Posted:
Tue Jan 11, 2005 6:44 pm Post subject:
Re: Adding Bluetooth to a SBS2003 network |
|
|
ICS uses 192.168.0.1 on the private interface of the host computer only.
That means you can use all remaining 253 IP addresses from 192.168.0.0/24
subnet for your client devices on that private subnet. Also, you can enable
more than one pc as a ICS host on the network, because they use the same
addressing for private network segments only, and this will not affect
connectivity on the physical network segment where all these computers
reside.
ICS setting is located at the following section of the group policy:
Computer COnfiguration\Administrative templates\Windows
components\Network\Network connections
--
Dmitry Korolyov [d__k@removethispart.mail.ru]
MVP: Windows Server - Directory Services
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:zfwEd.295$SN.50@newsfe6-gui.ntli.net...
| Quote: | Dmitry,
That was pretty much the line I was going down initially, but I see a few
problems here:
- if ICS can only use 192.168.0.1 as the NIC address, that presumably
means
that only one ICS PC can be on that network, and only one dongle can be
used..? Can the fixed IP used by ICS be changed?
- my ignorance here, but the ICS tab on the client is disabled ('disabled
by
group policy'). How can I reenable this? I couldn't find any policy
setting
for this on the server.
Thanks for your help.
Phil
"Dmitry Korolyov [MVP]" <d__k@removethispart.mail.ru> wrote in message
news:eJbBDVx9EHA.2804@TK2MSFTNGP15.phx.gbl...
Try installing the bluetooth device on the client machine, configuring
the
current network connection as a shared connection, and newly-installed
bluetooth network connection as a private network for that shared
connection. The IP configuration of the private network would be changed
to
use 192.168.0.1 on the ICS host machine, while any connecting bluetooth
clients will automatically receive IP configuration from 192.168.0.0/24
network and will connect through ICS.
--
Dmitry Korolyov [d__k@removethispart.mail.ru]
MVP: Windows Server - Directory Services
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:VztEd.197$SN.73@newsfe6-gui.ntli.net...
Hi,
I manage a client's network which is composed of an SBS2003 server with
XP
clients. The network looks like this:
Clients DC Server NAT/router
|------| |---| |---|
|-----------| ->public internet
192.x network <- NAT -> 172.x network
DHCP
So all client traffic runs through the multi-homed sbs server first,
then
on
through the edge firewall/router. This all works just fine, but the
client
has asked for the ability to use a bluetooth PDA to access the internet
&
sync with outlook. I have a bluetooth dongle that could be used for
that
purpose.
So now the question(s):
1) How best to do this? My first thought was to install the dongle on a
client, and use activesync in the normal way...but it appears that ICS
cannot be enabled on client machines as it would fix the IP of the NIC
(the
clients currently use dynamic addresses).
2) If I can't do this on the client PC, can I install the dongle on the
server? What do I need to do?
3) following on from point 2, from a security point of view, is this a
sane
thing to do? It appears that the connection can be locked down to some
degree, but my experience is limited with bluetooth, so anyone know
better?
Help and comments much appreciated!
Phil
|
|
|
| Back to top |
|
|
Phil
Guest
|
| Posted:
Tue Jan 11, 2005 7:52 pm Post subject:
Re: Adding Bluetooth to a SBS2003 network |
|
|
Ah, I see what you mean. Thanks - will give this a try tomorrow!
Phil
"Dmitry Korolyov [MVP]" <d__k@removethispart.mail.ru> wrote in message
news:e8FWEt99EHA.2012@TK2MSFTNGP15.phx.gbl...
| Quote: | ICS uses 192.168.0.1 on the private interface of the host computer only.
That means you can use all remaining 253 IP addresses from 192.168.0.0/24
subnet for your client devices on that private subnet. Also, you can
enable
more than one pc as a ICS host on the network, because they use the same
addressing for private network segments only, and this will not affect
connectivity on the physical network segment where all these computers
reside.
ICS setting is located at the following section of the group policy:
Computer COnfiguration\Administrative templates\Windows
components\Network\Network connections
--
Dmitry Korolyov [d__k@removethispart.mail.ru]
MVP: Windows Server - Directory Services
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:zfwEd.295$SN.50@newsfe6-gui.ntli.net...
Dmitry,
That was pretty much the line I was going down initially, but I see a
few
problems here:
- if ICS can only use 192.168.0.1 as the NIC address, that presumably
means
that only one ICS PC can be on that network, and only one dongle can be
used..? Can the fixed IP used by ICS be changed?
- my ignorance here, but the ICS tab on the client is disabled
('disabled
by
group policy'). How can I reenable this? I couldn't find any policy
setting
for this on the server.
Thanks for your help.
Phil
"Dmitry Korolyov [MVP]" <d__k@removethispart.mail.ru> wrote in message
news:eJbBDVx9EHA.2804@TK2MSFTNGP15.phx.gbl...
Try installing the bluetooth device on the client machine, configuring
the
current network connection as a shared connection, and newly-installed
bluetooth network connection as a private network for that shared
connection. The IP configuration of the private network would be
changed
to
use 192.168.0.1 on the ICS host machine, while any connecting bluetooth
clients will automatically receive IP configuration from 192.168.0.0/24
network and will connect through ICS.
--
Dmitry Korolyov [d__k@removethispart.mail.ru]
MVP: Windows Server - Directory Services
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:VztEd.197$SN.73@newsfe6-gui.ntli.net...
Hi,
I manage a client's network which is composed of an SBS2003 server
with
XP
clients. The network looks like this:
Clients DC Server NAT/router
|------| |---| |---|
|-----------| ->public internet
192.x network <- NAT -> 172.x network
DHCP
So all client traffic runs through the multi-homed sbs server first,
then
on
through the edge firewall/router. This all works just fine, but the
client
has asked for the ability to use a bluetooth PDA to access the
internet
&
sync with outlook. I have a bluetooth dongle that could be used for
that
purpose.
So now the question(s):
1) How best to do this? My first thought was to install the dongle on
a
client, and use activesync in the normal way...but it appears that
ICS
cannot be enabled on client machines as it would fix the IP of the
NIC
(the
clients currently use dynamic addresses).
2) If I can't do this on the client PC, can I install the dongle on
the
server? What do I need to do?
3) following on from point 2, from a security point of view, is this
a
sane
thing to do? It appears that the connection can be locked down to
some
degree, but my experience is limited with bluetooth, so anyone know
better?
Help and comments much appreciated!
Phil
|
|
|
| Back to top |
|
|
Rany ElHousieny [MSFT]
Guest
|
| Posted:
Wed Jan 12, 2005 1:47 am Post subject:
Re: Adding Bluetooth to a SBS2003 network |
|
|
Did you try using Blue tooth PAN in SP2?
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:VztEd.197$SN.73@newsfe6-gui.ntli.net...
| Quote: | Hi,
I manage a client's network which is composed of an SBS2003 server with XP
clients. The network looks like this:
Clients DC Server NAT/router
|------| |---| |---|
|-----------| ->public internet
192.x network <- NAT -> 172.x network
DHCP
So all client traffic runs through the multi-homed sbs server first, then
on
through the edge firewall/router. This all works just fine, but the client
has asked for the ability to use a bluetooth PDA to access the internet &
sync with outlook. I have a bluetooth dongle that could be used for that
purpose.
So now the question(s):
1) How best to do this? My first thought was to install the dongle on a
client, and use activesync in the normal way...but it appears that ICS
cannot be enabled on client machines as it would fix the IP of the NIC
(the
clients currently use dynamic addresses).
2) If I can't do this on the client PC, can I install the dongle on the
server? What do I need to do?
3) following on from point 2, from a security point of view, is this a
sane
thing to do? It appears that the connection can be locked down to some
degree, but my experience is limited with bluetooth, so anyone know
better?
Help and comments much appreciated!
Phil
|
|
|
| Back to top |
|
|
Phil
Guest
|
| Posted:
Wed Jan 12, 2005 2:07 pm Post subject:
Re: Adding Bluetooth to a SBS2003 network |
|
|
That's a new one on me. Is this new functionality in SP2 above and beyond
ICS via bluetooth?
"Rany ElHousieny [MSFT]" <ranyel@online.microsoft.com> wrote in message
news:ed0nnZB%23EHA.3368@TK2MSFTNGP15.phx.gbl...
| Quote: | Did you try using Blue tooth PAN in SP2?
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Phil" <comp (plus number1)@ntlworld.com> wrote in message
news:VztEd.197$SN.73@newsfe6-gui.ntli.net...
Hi,
I manage a client's network which is composed of an SBS2003 server with
XP
clients. The network looks like this:
Clients DC Server NAT/router
|------| |---| |---|
|-----------| ->public internet
192.x network <- NAT -> 172.x network
DHCP
So all client traffic runs through the multi-homed sbs server first,
then
on
through the edge firewall/router. This all works just fine, but the
client
has asked for the ability to use a bluetooth PDA to access the internet
&
sync with outlook. I have a bluetooth dongle that could be used for that
purpose.
So now the question(s):
1) How best to do this? My first thought was to install the dongle on a
client, and use activesync in the normal way...but it appears that ICS
cannot be enabled on client machines as it would fix the IP of the NIC
(the
clients currently use dynamic addresses).
2) If I can't do this on the client PC, can I install the dongle on the
server? What do I need to do?
3) following on from point 2, from a security point of view, is this a
sane
thing to do? It appears that the connection can be locked down to some
degree, but my experience is limited with bluetooth, so anyone know
better?
Help and comments much appreciated!
Phil
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in