XP networking issues

I have a laptop running WinXP. I use that laptop at work and at home.
I have a wireless network at home in a workgroup, while at work, I
connect to the work's domain. Now if I use the laptop at home I cannot
see my other machines that are on the workgroup, and I do not want to
remove it from the work domain either since then I have to get it
reconfigured it everytime. I need some expertise as to what would be a
way around it. I have been reading about Hardware profiles, but can I
have a hardware profile that makes changes to the domain/workgroup ??
Please help. Any help would be apprciated

Thank you

On 2 Apr 2004 10:39:35 -0800, *email_address_deleted* (Snake) wrote:

I have a laptop running WinXP. I use that laptop at work and at home.
I have a wireless network at home in a workgroup, while at work, I
connect to the work's domain. Now if I use the laptop at home I cannot
see my other machines that are on the workgroup, and I do not want to
remove it from the work domain either since then I have to get it
reconfigured it everytime. I need some expertise as to what would be a
way around it. I have been reading about Hardware profiles, but can I
have a hardware profile that makes changes to the domain/workgroup ??
Please help. Any help would be apprciated

Thank you

Snake,

You have three challenges:
1) Connection to router / WAP.
1) IP settings.
2) Domain / workgroup settings.

Connection to a router / WAP at work, and at home, simply involves associating
with each AP in turn. And, of course, each AP being setup for your laptop.

IP settings are easy, if you have DHCP in one or both location. If you use
automatic settings (TCP/IP Properties - General tab) for DHCP, then setup
Alternate Configuration for a fixed ip address if necessary.

If you connect to a domain at work (after having joined the laptop to a domain
at work), you can have a local account on the laptop, which will allow you to
access workgroup resources at home. Even though the laptop is a member of a
domain at work, you can still login at home using a local account, look under
Network Places - Entire Network - Microsoft Windows Network - Workgroup, and see
the resources available in workgroup Workgroup, when connected to your router at
home.

I have helped various folks at work, with similar setups.

And please learn to munge your email address properly, to keep yourself a bit
safer when posting to open forums. Protect yourself and the rest of the
internet - never post your address unmunged.
http://www.mailmsg.com/SPAM_munging.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

On 2 Apr 2004 10:39:35 -0800, *email_address_deleted* (Snake) wrote:

I have a laptop running WinXP. I use that laptop at work and at home.
I have a wireless network at home in a workgroup, while at work, I
connect to the work's domain. Now if I use the laptop at home I cannot
see my other machines that are on the workgroup, and I do not want to
remove it from the work domain either since then I have to get it
reconfigured it everytime. I need some expertise as to what would be a
way around it. I have been reading about Hardware profiles, but can I
have a hardware profile that makes changes to the domain/workgroup ??
Please help. Any help would be apprciated

Thank you

Snake,

You have three challenges:
1) Connection to router / WAP.
1) IP settings.
2) Domain / workgroup settings.

Connection to a router / WAP at work, and at home, simply involves associating
with each AP in turn. And, of course, each AP being setup for your laptop.

IP settings are easy, if you have DHCP in one or both location. If you use
automatic settings (TCP/IP Properties - General tab) for DHCP, then setup
Alternate Configuration for a fixed ip address if necessary.

If you connect to a domain at work (after having joined the laptop to a domain
at work), you can have a local account on the laptop, which will allow you to
access workgroup resources at home. Even though the laptop is a member of a
domain at work, you can still login at home using a local account, look under
Network Places - Entire Network - Microsoft Windows Network - Workgroup, and see
the resources available in workgroup Workgroup, when connected to your router at
home.

I have helped various folks at work, with similar setups.

And please learn to munge your email address properly, to keep yourself a bit
safer when posting to open forums. Protect yourself and the rest of the
internet - never post your address unmunged.
http://www.mailmsg.com/SPAM_munging.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

"Chuck" wrote in message
...
If you connect to a domain at work (after having joined the laptop to a
domain
at work), you can have a local account on the laptop, which will allow you
to
access workgroup resources at home. Even though the laptop is a member of
a
domain at work, you can still login at home using a local account, look
under
Network Places - Entire Network - Microsoft Windows Network - Workgroup,
and see
the resources available in workgroup Workgroup, when connected to your
router at
home.

I have helped various folks at work, with similar setups.

Chuck -- I'm struggling with precisely the same problem as the fellow that
originally posted. Laptop in a domain at work, home system in a workgroup.
Both WinXP Pro. I tried using a local account on the laptop, and still can't
see my workgroup machine (or any of the shares). Can't find it with the
Search feature.

I've disabled NetBIOS over TCP/IP on both machines, installed the
IPX/NetBIOS protocol, checked the bindings to ensure that both File and
Print Sharing and Client for Microsoft Networks is bound to IPX and NOT
TCP/IP, reboot both machines, still no success.

Read further based on some pointers in this newsgroup via MSDN knowlege base
articles. Modified the registry on both machines to set the NodeType to
Broadcast, rebooted, still no success.

Any more ideas? I have a workaround for file transfers using Remote Desktop
with the local resources mapped. Apparently, the Terminal Services bindings
for File and Print Sharing work. However, this is an awkward and not
completely flexible solution.

I'm getting quite frustrated...

Dave

"Chuck" wrote in message
...
If you connect to a domain at work (after having joined the laptop to a
domain
at work), you can have a local account on the laptop, which will allow you
to
access workgroup resources at home. Even though the laptop is a member of
a
domain at work, you can still login at home using a local account, look
under
Network Places - Entire Network - Microsoft Windows Network - Workgroup,
and see
the resources available in workgroup Workgroup, when connected to your
router at
home.

I have helped various folks at work, with similar setups.

Chuck -- I'm struggling with precisely the same problem as the fellow that
originally posted. Laptop in a domain at work, home system in a workgroup.
Both WinXP Pro. I tried using a local account on the laptop, and still can't
see my workgroup machine (or any of the shares). Can't find it with the
Search feature.

I've disabled NetBIOS over TCP/IP on both machines, installed the
IPX/NetBIOS protocol, checked the bindings to ensure that both File and
Print Sharing and Client for Microsoft Networks is bound to IPX and NOT
TCP/IP, reboot both machines, still no success.

Read further based on some pointers in this newsgroup via MSDN knowlege base
articles. Modified the registry on both machines to set the NodeType to
Broadcast, rebooted, still no success.

Any more ideas? I have a workaround for file transfers using Remote Desktop
with the local resources mapped. Apparently, the Terminal Services bindings
for File and Print Sharing work. However, this is an awkward and not
completely flexible solution.

I'm getting quite frustrated...

Dave

On Sun, 4 Apr 2004 13:42:23 -0700, "David Waller"
wrote:

Chuck -- I'm struggling with precisely the same problem as the fellow that
originally posted. Laptop in a domain at work, home system in a workgroup.
Both WinXP Pro. I tried using a local account on the laptop, and still can't
see my workgroup machine (or any of the shares). Can't find it with the
Search feature.

I've disabled NetBIOS over TCP/IP on both machines, installed the
IPX/NetBIOS protocol, checked the bindings to ensure that both File and
Print Sharing and Client for Microsoft Networks is bound to IPX and NOT
TCP/IP, reboot both machines, still no success.

Read further based on some pointers in this newsgroup via MSDN knowlege base
articles. Modified the registry on both machines to set the NodeType to
Broadcast, rebooted, still no success.

Any more ideas? I have a workaround for file transfers using Remote Desktop
with the local resources mapped. Apparently, the Terminal Services bindings
for File and Print Sharing work. However, this is an awkward and not
completely flexible solution.

Dave,

Your problem is most likely solvable. Can you please start another thread (your
own Subject) with this history and problem description? It is to your benefit
to do so.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

On Sun, 4 Apr 2004 13:42:23 -0700, "David Waller"
wrote:

Chuck -- I'm struggling with precisely the same problem as the fellow that
originally posted. Laptop in a domain at work, home system in a workgroup.
Both WinXP Pro. I tried using a local account on the laptop, and still can't
see my workgroup machine (or any of the shares). Can't find it with the
Search feature.

I've disabled NetBIOS over TCP/IP on both machines, installed the
IPX/NetBIOS protocol, checked the bindings to ensure that both File and
Print Sharing and Client for Microsoft Networks is bound to IPX and NOT
TCP/IP, reboot both machines, still no success.

Read further based on some pointers in this newsgroup via MSDN knowlege base
articles. Modified the registry on both machines to set the NodeType to
Broadcast, rebooted, still no success.

Any more ideas? I have a workaround for file transfers using Remote Desktop
with the local resources mapped. Apparently, the Terminal Services bindings
for File and Print Sharing work. However, this is an awkward and not
completely flexible solution.

Dave,

Your problem is most likely solvable. Can you please start another thread (your
own Subject) with this history and problem description? It is to your benefit
to do so.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

"Chuck" wrote in message
...
On Sun, 4 Apr 2004 13:42:23 -0700

Your problem is most likely solvable. Can you please start another thread
(your
own Subject) with this history and problem description? It is to your
benefit
to do so.

Thanks, Chuck. See the thread titled, "Can't browse/file/print/share between
Workgroup and Domain".

Dave

"Chuck" wrote in message
...
On Sun, 4 Apr 2004 13:42:23 -0700

Your problem is most likely solvable. Can you please start another thread
(your
own Subject) with this history and problem description? It is to your
benefit
to do so.

Thanks, Chuck. See the thread titled, "Can't browse/file/print/share between
Workgroup and Domain".

Dave