Re: W2K Laptop Networking Questions
From: serverguy (nospam_at_hatespam.com)
Date: 06/24/04
- Next message: brian woodward: "Peer 2 Peer set-up"
- Previous message: Phillip Windell: "Re: DHCP basic question - turning on scope of same range?"
- In reply to: absolutezero273c: "Re: W2K Laptop Networking Questions"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Jun 2004 10:31:40 -0400
I guess you need to better explain the peer2peer situation. As mentioned
before, you should not need static ips at all. However, I don't necessary
agree with Phillip on the DHCP point because if you don't have DHCP at all
times, you won't have ip addresses and you won't have a network. But in
order to use DHCP in the peer2peer environments, you need "something"
serving up ip addresses. There are many ways to do this: buy some cheap
routers, make one or more of the laptops a DHCP server giving it a
permanently static ip, configure ICS, etc... How exactly do the laptops
connect to each other in the peer2peer lans? Once they have ip addresses,
connecting the laptops to each other is a simple matter of permissions using
their existing cached domain credentials, or if necessary local user
accounts. And then you get the fun part of figuring out the DNS. Good
luck.
"absolutezero273c" <absolutezero273c@discussions.microsoft.com> wrote in
message news:7C3EAF09-AD36-4A68-8379-E5C9A55709D6@microsoft.com...
> Phillip,
>
> Yes, I was wrong in saying "reservation".
>
> But that is not really where my problem lies. I don't have any problem
with my users changing locations (subnets) when using DHCP. WINS and DNS
work fine.
>
> The "knowing the ip address" part came up when these users go out to a
remote location and attempt to connect to each others machines in a work
group and can't browse to each other in network neighborhood. Incedentally,
how long should this take for the browser to update if in a workgroup?
>
> For example, I can set Multi-Network Manager (MNM) to use DHCP in 2
"network profiles", and set it to renew the dhcp address each time (I can't
set the dhcp lease to expire in hours and sometimes these individuals go to
multiple offices within the dame day) but in the 3rd network profile in MNM
I switch to a "workgroup" so the users can share files on a peer-to-peer
network when not in the office. Here is where I need the static ip
addresses. Or at least I think I do.
>
> In addition to this peer-to-peer file sharing in the workgroup I need the
network profile to be accessible to the user who is logged in locally. I
would prefer that they can login using their network username and password.
But if that won't work then I can continue sharing the network profile to
the local profile.
>
> I was hoping to find a way to allow this network switching without
additional software, without requiring admin rights of the user and without
requiring the user to change any settings.
>
> Maybe I'm going about this all wrong?
>
> How can I guarantee that 2 or more of my laptop users will be able to see
each other, in a remote location (not on any subnet on my domain) retain the
ability to share data files between each other, and still be able to be
logged in to their network profile to access software, e-mail, data, etc.?
Without using additional software?
>
>
> "Phillip Windell" wrote:
>
> > "absolutezero273c" <absolutezero273c@discussions.microsoft.com> wrote in
> > message news:EFB0E171-AB69-4DCC-8F3A-66C6AD26AED5@microsoft.com...
> > > another laptop. So for now they are all set static and I have
reserved ip
> > > addressese in each subnet for each nic.
> >
> > Static and Reservations don't go in the same sentence :-) They are
either
> > Static or they are DHCP and getting it by Reservations. You sure you
didn't
> > mean to say "Exclusions"?
> >
> > Reservations mean nothing if the Client isn't using DHCP. You should be
> > able to set Reservations in each scope (subnet) and they would receive
the
> > proper address eveytime they connect according to which subnet they
logged
> > into.
> >
> > But that is all pointless anyway and is not the way to handle this.
They
> > would work perfectly fine with DHCP and there is no real reason to have
to
> > know which IP# they have at all times. They should be using common WINS
and
> > DNS Servers and should be accessed by machine name instead of IP#s.
These
> > services will keep the Names accessable no matter what IP# they use. Now
if
> > you end up with a "naming" issue then you must solve that by making sure
> > WINS & DNS is being done properly, but DHCP (or staic IP#s) certainly is
not
> > the place to design the plan nor troublshoot the plan.
> >
> > > I realize that I should also be able to assign 2 ip address to one
nic.
> > But I tried
> > > that and had issues. My guess is it was getting hungup on which was
> > primary a
> >
> > No, there is not a prayer that that would work and is the wrong
approach. A
> > single nic can have multiple addresses but they must be from the same
> > subnet. The Primary will always be the one listed in the normal config
while
> > all secondaries will have to be added via the additional addresses
section.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > secondary and would never get to the secondary ip address which was to
> > represent the subnet in the remote office.
>
- Next message: brian woodward: "Peer 2 Peer set-up"
- Previous message: Phillip Windell: "Re: DHCP basic question - turning on scope of same range?"
- In reply to: absolutezero273c: "Re: W2K Laptop Networking Questions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
