IP Routing problem with Bluetooth..persistent routes?

O

oferns

Hi,
I have a Belkin Wireless router (192.168.2.1) with an ADSL internet
connection going into it. I have 4 PC's; 3 wireless connections and one
hard wired. I have a Bluetooth adapter plugged into the hardwired PC.
All IP address, including Bluetooth adapter and device are not assigned
by DHCP but are static. Here is the IPCONFIG /ALL from the hardwired
PC.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Lanparty
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter NvidiaETH:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networ
Physical Address. . . . . . . . . : 00-01-29-FB-B7-C4
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::201:29ff:fefb:
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth LAN Access
Physical Address. . . . . . . . . : 00-0A-3A-65-19-89
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::20a:3aff:fe65:
Default Gateway . . . . . . . . . : 192.168.2.2
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pse
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling

Physical Address. . . . . . . . . : C0-A8-01-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling

Physical Address. . . . . . . . . : C0-A8-02-02
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS over Tcpip. . . . . . . . : Disabled



....and here is the routing table....

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 01 29 fb b7 c4 ...... NVIDIA nForce Networking Controller
0x10004 ...00 0a 3a 65 19 89 ...... Bluetooth LAN Access Server Driver
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.2
20
0.0.0.0 0.0.0.0 192.168.2.2 192.168.1.1
40
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1
40
192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1
40
192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1
40
192.168.2.0 255.255.255.0 192.168.2.2 192.168.2.2
20
192.168.2.2 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.2.255 255.255.255.255 192.168.2.2 192.168.2.2
20
224.0.0.0 240.0.0.0 192.168.1.1 192.168.1.1
40
224.0.0.0 240.0.0.0 192.168.2.2 192.168.2.2
20
255.255.255.255 255.255.255.255 192.168.1.1 192.168.1.1
1
255.255.255.255 255.255.255.255 192.168.2.2 192.168.2.2
1
Default Gateway: 192.168.2.1
===========================================================================
Persistent Routes:
None


The problem I have is that the Bluetooth device cannot see the LAN or
the Internet. I guess I need some persistent routes. Any help much
appreciated. I am a complete noob to this but otherwise technically
savvy.....

Thx,

OJ


I can ping the Bluetooth Adapter and I can ping the bluetooth device on
192.168.1.1 & 192.168.1.2
 
S

Steve Winograd [MVP]

Hi,
I have a Belkin Wireless router (192.168.2.1) with an ADSL internet
connection going into it. I have 4 PC's; 3 wireless connections and one
hard wired. I have a Bluetooth adapter plugged into the hardwired PC.
All IP address, including Bluetooth adapter and device are not assigned
by DHCP but are static. Here is the IPCONFIG /ALL from the hardwired
PC.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Lanparty
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter NvidiaETH:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networ
Physical Address. . . . . . . . . : 00-01-29-FB-B7-C4
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::201:29ff:fefb:
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth LAN Access
Physical Address. . . . . . . . . : 00-0A-3A-65-19-89
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::20a:3aff:fe65:
Default Gateway . . . . . . . . . : 192.168.2.2
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pse
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling

Physical Address. . . . . . . . . : C0-A8-01-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling

Physical Address. . . . . . . . . : C0-A8-02-02
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS over Tcpip. . . . . . . . : Disabled



...and here is the routing table....

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 01 29 fb b7 c4 ...... NVIDIA nForce Networking Controller
0x10004 ...00 0a 3a 65 19 89 ...... Bluetooth LAN Access Server Driver
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.2
20
0.0.0.0 0.0.0.0 192.168.2.2 192.168.1.1
40
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1
40
192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1
40
192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1
40
192.168.2.0 255.255.255.0 192.168.2.2 192.168.2.2
20
192.168.2.2 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.2.255 255.255.255.255 192.168.2.2 192.168.2.2
20
224.0.0.0 240.0.0.0 192.168.1.1 192.168.1.1
40
224.0.0.0 240.0.0.0 192.168.2.2 192.168.2.2
20
255.255.255.255 255.255.255.255 192.168.1.1 192.168.1.1
1
255.255.255.255 255.255.255.255 192.168.2.2 192.168.2.2
1
Default Gateway: 192.168.2.1
===========================================================================
Persistent Routes:
None


The problem I have is that the Bluetooth device cannot see the LAN or
the Internet. I guess I need some persistent routes. Any help much
appreciated. I am a complete noob to this but otherwise technically
savvy.....

Thx,

OJ


I can ping the Bluetooth Adapter and I can ping the bluetooth device on
192.168.1.1 & 192.168.1.2
Click to expand...

The hardwired PC isn't configured to share its Internet connection via
Bluetooth. Defining persistent routes and enabling IP routing aren't
enough to do the job.

I don't have a Bluetooth network to test this with, but here are two
methods that I think will work. The first one will give Internet
access, but not LAN access, to the Bluetooth device. The second one
will give Internet access and LAN access to the Bluetooth device:

1. Enable Internet Connection Sharing on the hardwired PC's Ethernet
connection. Tell it to use the Bluetooth connection for the home
network. That will set the PC's Bluetooth connection to 192.168.0.1.
Configure the Bluetooth device to obtain an IP address automatically,
or give it these static properties:

IP Address: 192.168.0.x (1<x<255)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Server = 192.168.0.1 or your ISP's DNS server

or:

2. On the hardwired PC, create a network bridge between the Ethernet
connection and the Bluetooth connection. Give the Bluetooth device a
static IP address in the 192.168.2.x subnet.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
O

oferns

Hi Steve,
Thanks for the response; I have read many of your posts researching
this issue. I have tried both of your suggestions previously, and both
have ruined my LAN connection and consequently my internet connection
on the hard wired machine. :blush:( Perhaps I am doing saomething wrong.

I did try giving the Bluetooth Adapter an ip address in the same
range/mask as the LAN and I could ping the adapter (which always said
connected regardless of whether anything was or not) but not the
device. I am using a PocketPC 2003SE BTW. I had given the device an IP
address in the same subnet/mask as well and set its default gate way to
the bluetooth dongle's IP.

With hindsight, I imagine this shows quite a lot of ignorance on the
subject but would you mind attempting a brief explaination as to why
that didn't work? Also, if you have the time could you suggest anything
else to try or anything more info i can give to help?


IP routing is enabled in the windows registry throughout....

Also, why is adding to the route table not enough?

Thanks very much for your time...

Oliver
 
S

Steve Winograd [MVP]

Hi,
I have a Belkin Wireless router (192.168.2.1) with an ADSL internet
connection going into it. I have 4 PC's; 3 wireless connections and one
hard wired. I have a Bluetooth adapter plugged into the hardwired PC.
All IP address, including Bluetooth adapter and device are not assigned
by DHCP but are static. Here is the IPCONFIG /ALL from the hardwired
PC.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Lanparty
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter NvidiaETH:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networ
Physical Address. . . . . . . . . : 00-01-29-FB-B7-C4
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::201:29ff:fefb:
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth LAN Access
Physical Address. . . . . . . . . : 00-0A-3A-65-19-89
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::20a:3aff:fe65:
Default Gateway . . . . . . . . . : 192.168.2.2
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
[snip]

...and here is the routing table.... [snip]

The problem I have is that the Bluetooth device cannot see the LAN or
the Internet. I guess I need some persistent routes. Any help much
appreciated. I am a complete noob to this but otherwise technically savvy.....

I can ping the Bluetooth Adapter and I can ping the bluetooth device on
192.168.1.1 & 192.168.1.2
Click to expand...

The hardwired PC isn't configured to share its Internet connection via
Bluetooth. Defining persistent routes and enabling IP routing aren't
enough to do the job.

I don't have a Bluetooth network to test this with, but here are two
methods that I think will work. The first one will give Internet
access, but not LAN access, to the Bluetooth device. The second one
will give Internet access and LAN access to the Bluetooth device:

1. Enable Internet Connection Sharing on the hardwired PC's Ethernet
connection. Tell it to use the Bluetooth connection for the home
network. That will set the PC's Bluetooth connection to 192.168.0.1.
Configure the Bluetooth device to obtain an IP address automatically,
or give it these static properties:

IP Address: 192.168.0.x (1<x<255)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Server = 192.168.0.1 or your ISP's DNS server

or:

2. On the hardwired PC, create a network bridge between the Ethernet
connection and the Bluetooth connection. Give the Bluetooth device a
static IP address in the 192.168.2.x subnet.
Click to expand...

Hi Steve,
Thanks for the response; I have read many of your posts researching
this issue. I have tried both of your suggestions previously, and both
have ruined my LAN connection and consequently my internet connection
on the hard wired machine. :blush:( Perhaps I am doing saomething wrong.

I did try giving the Bluetooth Adapter an ip address in the same
range/mask as the LAN and I could ping the adapter (which always said
connected regardless of whether anything was or not) but not the
device. I am using a PocketPC 2003SE BTW. I had given the device an IP
address in the same subnet/mask as well and set its default gate way to
the bluetooth dongle's IP.

With hindsight, I imagine this shows quite a lot of ignorance on the
subject but would you mind attempting a brief explaination as to why
that didn't work? Also, if you have the time could you suggest anything
else to try or anything more info i can give to help?

IP routing is enabled in the windows registry throughout....

Also, why is adding to the route table not enough?

Thanks very much for your time...

Oliver[/QUOTE]

You're welcome, Oliver. Since my reply to your first message, I've
found a couple of Bluetooth adapters and tried out the two methods
that I recommended to you. Both of them worked just as I expected,
after I followed the steps in this Microsoft Knowledge Base article to
get the Network Bridge working:

Bridge May Not Work With a Non-Promiscuous Mode Network Adapter
http://support.microsoft.com/kb/302348/en-us

I don't know why those methods don't work for you. Enabling Internet
Connection Sharing shouldn't ruin your LAN connection. To share your
LAN connection over Bluetooth:

1. Create a Bluetooth network connection between the computers.

2. Configure each computer's Bluetooth connection to obtain an IP
address automatically.

3. Right-click the LAN connection and click Properties.

4. Put a check mark in the box "Allow other computers to connect
through this computer's Internet connection".

5. If a box saying "Select a private network connection" appears,
select the Bluetooth connection from the menu.

Configuring the route table and enabling IP routing aren't enough to
give Internet access to the PocketPC. That requires NAT (Network
Address Translation), which is what Internet Connection Sharing does,
and what a typical home broadband router does.

Without NAT, the PocketPC is not accessible by web servers on the
Internet. They have no way to send information to the PocketPC's LAN
address. They can only send information to the main PC's Internet
address, and the main PC has no way of knowing that the data is a
reply from the Internet to the PocketPC, so it has no way of
forwarding the information to the PocketPC.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
O

oferns

Hi Steve,
Forgive my late response, I am in th UK and it was Bedtime!! Thanks
again for your help. I am at work at the moment but I suppose you are
in Bed! I shall re-try your suggestions and repost this evening.

Thanks again,
Oliver

Hi,
I have a Belkin Wireless router (192.168.2.1) with an ADSL internet
connection going into it. I have 4 PC's; 3 wireless connections and one
hard wired. I have a Bluetooth adapter plugged into the hardwired PC.
All IP address, including Bluetooth adapter and device are not assigned
by DHCP but are static. Here is the IPCONFIG /ALL from the hardwired
PC.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Lanparty
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter NvidiaETH:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networ
Physical Address. . . . . . . . . : 00-01-29-FB-B7-C4
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::201:29ff:fefb:
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth LAN Access
Physical Address. . . . . . . . . : 00-0A-3A-65-19-89
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::20a:3aff:fe65:
Default Gateway . . . . . . . . . : 192.168.2.2
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
[snip]

...and here is the routing table.... [snip]

The problem I have is that the Bluetooth device cannot see the LAN or
the Internet. I guess I need some persistent routes. Any help much
appreciated. I am a complete noob to this but otherwise technically
savvy.....

I can ping the Bluetooth Adapter and I can ping the bluetooth device on
192.168.1.1 & 192.168.1.2

The hardwired PC isn't configured to share its Internet connection via
Bluetooth. Defining persistent routes and enabling IP routing aren't
enough to do the job.

I don't have a Bluetooth network to test this with, but here are two
methods that I think will work. The first one will give Internet
access, but not LAN access, to the Bluetooth device. The second one
will give Internet access and LAN access to the Bluetooth device:

1. Enable Internet Connection Sharing on the hardwired PC's Ethernet
connection. Tell it to use the Bluetooth connection for the home
network. That will set the PC's Bluetooth connection to 192.168.0.1.
Configure the Bluetooth device to obtain an IP address automatically,
or give it these static properties:

IP Address: 192.168.0.x (1<x<255)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Server = 192.168.0.1 or your ISP's DNS server

or:

2. On the hardwired PC, create a network bridge between the Ethernet
connection and the Bluetooth connection. Give the Bluetooth device a
static IP address in the 192.168.2.x subnet.
Click to expand...

Hi Steve,
Thanks for the response; I have read many of your posts researching
this issue. I have tried both of your suggestions previously, and both
have ruined my LAN connection and consequently my internet connection
on the hard wired machine. :blush:( Perhaps I am doing saomething wrong.

I did try giving the Bluetooth Adapter an ip address in the same
range/mask as the LAN and I could ping the adapter (which always said
connected regardless of whether anything was or not) but not the
device. I am using a PocketPC 2003SE BTW. I had given the device an IP
address in the same subnet/mask as well and set its default gate way to
the bluetooth dongle's IP.

With hindsight, I imagine this shows quite a lot of ignorance on the
subject but would you mind attempting a brief explaination as to why
that didn't work? Also, if you have the time could you suggest anything
else to try or anything more info i can give to help?

IP routing is enabled in the windows registry throughout....

Also, why is adding to the route table not enough?

Thanks very much for your time...

Oliver
Click to expand...

You're welcome, Oliver. Since my reply to your first message, I've
found a couple of Bluetooth adapters and tried out the two methods
that I recommended to you. Both of them worked just as I expected,
after I followed the steps in this Microsoft Knowledge Base article to
get the Network Bridge working:

Bridge May Not Work With a Non-Promiscuous Mode Network Adapter
http://support.microsoft.com/kb/302348/en-us

I don't know why those methods don't work for you. Enabling Internet
Connection Sharing shouldn't ruin your LAN connection. To share your
LAN connection over Bluetooth:

1. Create a Bluetooth network connection between the computers.

2. Configure each computer's Bluetooth connection to obtain an IP
address automatically.

3. Right-click the LAN connection and click Properties.

4. Put a check mark in the box "Allow other computers to connect
through this computer's Internet connection".

5. If a box saying "Select a private network connection" appears,
select the Bluetooth connection from the menu.

Configuring the route table and enabling IP routing aren't enough to
give Internet access to the PocketPC. That requires NAT (Network
Address Translation), which is what Internet Connection Sharing does,
and what a typical home broadband router does.

Without NAT, the PocketPC is not accessible by web servers on the
Internet. They have no way to send information to the PocketPC's LAN
address. They can only send information to the main PC's Internet
address, and the main PC has no way of knowing that the data is a
reply from the Internet to the PocketPC, so it has no way of
forwarding the information to the PocketPC.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com[/QUOTE]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Wireless network setup - XP SP2 - workgroup computers not visible 9
Network WinXP Home with Win98FE 5
Mis-configured network I guess . . . 1
Cannot Ping Local Host With IP,name, localhost 10
One computer in network cannot share files 1
Two XP's Not talking " Chuck" 5
Limited or No Connectivity 26
File & Printer Sharing 2

Top