ICS in a server or domain environment

[Fernando]

Hello Group!
I have a company laptop with XP Professional working in a domain
environment. I use this computer at home to access my home lan and
internet with no problem. This computer also has a secondary drive with
XP Home set up in a Workgroup environment, which I only use if I want to
use/install software that I do not want in my XP Professional. It also
access my home internet/intranet with no problem.
I want to access the internet/intranet with a Bluetooth enabled PDA. I
have manually set up ICS, identically in both XP Professional and XP
Home. From the PDA I can ping my Bluetooth device and the
intranet/internet connection nic in both XP configurations, but can only
get in the internet with the use of the PDA in the XP Home
configuration. I suspect that my problem browsing the internet/intranet
with the PDA with the XP Professional is the fact that it works in a
domain environment. Are there any other options using XP Professional?
Or should I use a third party software? Getting help from the IT group
is out of the question.

The following configurations were taken using my home lan. I feel that
if I can get the XP Professional to work right at home I should have no
problem at work.

Working XP Home ipconfig

Windows IP Configuration

Host Name . . . . . . . . . . . . : latitude-d600
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Chadxxxxx
Description . . . . . . . . . . . : Broadcom 570x Gigabit
Integrated Controller
Physical Address. . . . . . . . . : 00-0F-1F-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
DHCP Server . . . . . . . . . . . : 192.168.0.254
DNS Servers . . . . . . . . . . . : 192.168.0.254
Lease Obtained. . . . . . . . . . : Wednesday, January 04, 2006
10:07:42 PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038
10:14:07 PM


Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth LAN Access Server
Driver
Physical Address. . . . . . . . . : 00-10-60-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :


Non-Working XP Professional ipconfig

Windows IP Configuration

Host Name . . . . . . . . . . . . : NC27689500
Primary Dns Suffix . . . . . . . : xx.xxx.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : xx.xxx.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : coqui.net
Description . . . . . . . . . . . : Broadcom 570x Gigabit
Integrated Controller
Physical Address. . . . . . . . . : 00-0F-1F-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254
DHCP Server . . . . . . . . . . . : 192.168.0.254
DNS Servers . . . . . . . . . . . : 192.168.0.254
Lease Obtained. . . . . . . . . . : Wed, Jan 04, 06 21:05:24
Lease Expires . . . . . . . . . . : Mon, Jan 18, 38 22:14:07

Ethernet adapter {025EBD12-EEAF-4464-A332-4F416EE2ED08}:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Nortel IPSECSHM Adapter -
Packet Scheduler Miniport
Physical Address. . . . . . . . . : 44-45-53-54-42-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Bluetooth Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth LAN Access Server
Driver
Physical Address. . . . . . . . . : 00-10-60-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Thanks...
Fernando

 

[Fernando]

I removed the laptop from the domain and add it to one of the still
existant old workgroups. The ICS started working inmediatelly. The bad
part is that I do not have enough persimision to add me back to the
domain... Ohhh, well... Will have to get the local IT guys to fix it for
me. Anyway, once they add me back to the domain I will be back to the
original problem. How do I share the internet/intranet in a domain
enviroment?

Thanks...

 

[Fernando]

Hello again...
Is there an answer to this problem? Or Is my question not clear? Can
anybody read this?!?!?! LOL! It is just weird to me that nobody has
answered my question either way.
Thanks,

Fernando

 

[Chuck]

I removed the laptop from the domain and add it to one of the still
existant old workgroups. The ICS started working inmediatelly. The bad
part is that I do not have enough persimision to add me back to the
domain... Ohhh, well... Will have to get the local IT guys to fix it for
me. Anyway, once they add me back to the domain I will be back to the
original problem. How do I share the internet/intranet in a domain
enviroment?

Fernando,

Your question, as phrased, leaves much to be desired. Strictly speaking, domain
membership should have nothing to do with sharing of Internet services.
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking.html

Generally, in a domain environment, folks who own a domain have enough expertise
to setup both file sharing, and Internet service sharing, without using the
Network Setup Wizard, and enough sense to not need ICS. ICS, and the NSW, were
therefore designed for use in peer-peer networks, or workgroups.
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html
<http://nitecruzr.blogspot.com/2005/05/ics-is-ok-but-you-can-do-better.html>
http://nitecruzr.blogspot.com/2005/05/ics-is-ok-but-you-can-do-better.html

Using a computer, alternately, in both a domain and a workgroup, PLUS using the
computer as an ICS host AND a Bluetooth bridge, could be a lot of work. Most
domains are complicated enough that all components are chosen with one purpose
in mind, and the owners stick to that one purpose.

If you truly want to use your company laptop as a Bluetooth bridge when you're
home, and on the domain at work, I recommend that you look at a network
configuration manager. These are not free products, but in this case, the
expense may be justified by the functionality which you seem to require.
<http://nitecruzr.blogspot.com/2005/05/have-laptop-will-travel.html#ComplexSolutions>
http://nitecruzr.blogspot.com/2005/05/have-laptop-will-travel.html#ComplexSolutions

 

[Fernando]

Chuck, thanks for the information. How should I go around then to setup
my bluetooth pda with this computer in order to browse the intranet
through my laptop?

 

[Chuck]

Chuck, thanks for the information. How should I go around then to setup
my bluetooth pda with this computer in order to browse the intranet
through my laptop?

Fernando,

If I was a domain admin responsible for supporting your laptop when it's
connected to the domain, I personally would hope that there would be a Corporate
Security Policy covering this issue. To wit:

No network changes may be made to domain joined computers.

Joining a domain is a matter of setting up a two way trust. The domain trusts
the laptop, and the laptop trusts the domain. When you reconfigure the laptop,
the trust relationship is broken, or at least damaged.

With Windows Vista will come a health check and quarantine, with possible
automatic repair, of any computers entering the domain from outside. All of
this will be according to Corporate Policy, but it's a start.

Barring the above CSP, and speaking as an IT person, I would highly recommend
that you work with your IT person. Jointly develop a strategy to support both
domain connectivity (at work) and workgroup / BT / PDA connectivity (at home).
Try the configuration managers, but work with your domain admin, not against him
(her?):
<http://nitecruzr.blogspot.com/2005/05/have-laptop-will-travel.html#ComplexSolutions>
http://nitecruzr.blogspot.com/2005/05/have-laptop-will-travel.html#ComplexSolutions

 

[Fernando]

Chuck,
Thanks for the information. I do not need to remove the laptop from the
domain name. I have been using it at my home lan with no problem. During
my reading over different places I got the impression that I could not
share my internet connection while in a domain name. That is why I
removed the laptop to see what happened. With no further changes I was
sharing the internet connection... I will check into that Windows Vista...
As far as the Regional IT group, working with them is close to
impossible, working for them is easy... I have a very valid need for a
variance, it has gone to my director level, and 2 months into it we
still don't have it resolved. Can you imagine how long it will take them
to just look at one user issue? They will just as well say no than to
even try. My local IT group is a different story, they won't always say
yes, but they are profesional, fast and darn good! Problem is, they have
no control over the domain.