Re: Problems with 'non-standard' ICS on XP machines.
- From: "4wd" <QBXVRAVCYLPD@xxxxxxxxxxxxx>
- Date: 14 Aug 2005 01:27:29 -0700
Steve Winograd [MVP] wrote:
> In article <1123907112.743966.79160@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
> "4wd" <QBXVRAVCYLPD@xxxxxxxxxxxxx> wrote:
> >Hello all, first off I have ICS working as follows:
> >
> >1) Desktop XP-Pro SP2 (DESK1), ICS Host, dialup internet shared over
> >WLAN, workgroup is MSHOME, DHCP enabled, 192.168.0.1 static.
> >2) Laptop XP-Home SP2 (ACER), ICS client, DHCP assigned
> >3) Desktop XP-Pro SP2 (DESK2), ICS client, DHCP assigned
> >
> >The above works fine, set up using the network wizard.
> >
> >However, I want to use workgroup WORKGROUP - it didn't work.
> >
> >I found out that even though I had specified WORKGROUP on all machines,
> >on DESK1 it made the WLAN adapter DESK1.mshome.net, (My
> >Computer->Properties->Computer Name shows WORKGROUP), needless to say,
> >it didn't work.
> >
> >DESK1 also has two GBit and an IEEE1394a adapter. I want to bridge one
> >of the GBit adapters and the IEEE1394a and give them a static address.
> >As soon as I do it, ICS stops working.
> >
> >Are there reasons why these problems should happen?
> >
> >Is there a way toget what I want rather than what Windows wants?
>
> Internet access doesn't use workgroup names or computer names --
> they're only used for file and printer sharing. Something else is
> causing the problem.
Just seems strange that when I changed the workgroup name to what it
wanted everything suddenly worked.
I'll elaborate a little, I originally gave all machines
workgroup=WORKGROUP, (the group most often used at our LAN meetings).
File sharing and pinging worked between ACER and DESK2 but neither
could talk to DESK1, (the ICS host), however both obtained IPs from
it's DCHP server.
As soon as the workgroup was changed to MSHOME, (the default), file
sharing/pinging worked between all machines and ICS started working.
Also doesn't explain why, when I had told it to use
workgroup=WORKGROUP, it gave the ICS host adapter the name
DESK1.mshome.net, surely it should have given it DESK1.workgroup.net?
> Please reply to this message in the news group (not by E-mail) with
> more information to help other people understand the problem:
>
> What network adapter has the 192.168.0.1 address and shares the
> Internet connection with ACER and DESK2? Is it one of the GBit
> adapters, the IEEE1394a adapter, or a different one?
Sorry, thought that was clear enough here:
1) Desktop XP-Pro SP2 (DESK1), ICS Host, dialup internet shared over
WLAN, workgroup is MSHOME, DHCP enabled, 192.168.0.1 static.
A USB WLAN adapter, (Netgear WG111), has the IP of 192.168.0.1 and
handles ICS traffic.
> What static address did you give the network bridge?
192.168.0.244
> Just out of curiosity, why do you want to bridge those connections?
At LAN meetings it's the easiest way to connect to those without GBit
adapter but have IEEE1394, (a lot faster than Fast Ethernet).
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
Thanks,
Dave
.
- Follow-Ups:
- Re: Problems with 'non-standard' ICS on XP machines.
- From: Steve Winograd [MVP]
- Re: Problems with 'non-standard' ICS on XP machines.
- References:
- Problems with 'non-standard' ICS on XP machines.
- From: 4wd
- Re: Problems with 'non-standard' ICS on XP machines.
- From: Steve Winograd [MVP]
- Problems with 'non-standard' ICS on XP machines.
- Prev by Date: Re: Uninstall Network Sign on.
- Next by Date: Re: Problems with 'non-standard' ICS on XP machines.
- Previous by thread: Re: Problems with 'non-standard' ICS on XP machines.
- Next by thread: Re: Problems with 'non-standard' ICS on XP machines.
- Index(es):
Relevant Pages
|
