Being a complete newbie to networking, I'm very confused about assigning
IP addresses and even if they need to be assigned.

I've studied a lot of the "how to" and "troubleshooting" info available
and there does not seem to be any consensus on this.

Example :- I'm currently trying to set up our SOHO on a peer to peer
basis:-

7 machines - 4 on XP Pro, 2 on W98SE and one on W2K.
One of the XP machines has an internet connection ( ADSL via a NIC)
and all the other machines use that access (ICS) and that works fine.
I set up the NW on one of the XP machines and created the diskette
with the netsetup program. and installed it on the others.
On the XPs - no problem
Netsetup not for WIN2K but that machine is connecting to the net OK
and can see and be seen by the others ( don't ask me how I did it - no
idea -
" mucho suck it and see")
The Win98s are a nightmare - one connects OK sometimes but at the
next reboot will give the message " unable to browse the network"
The other W98 just straight forward refuses to see see the entire
network.

( N.B. All PCs have unique names and the same workgroup name )

Maybe my query re IP addressing is not in the right area but even if
it's not I'd appreciate a small clarification on this and any other help
re: the general problem .

Many TIA

Di Lemma

You might have an issue with the trying to use multiple protocols. How have
you got it set up now? Are you just using TCP/IP or are you using NETBeui
too? Windows has issues using multiple protocols. You only need TCP/IP.
Uninstall the other protocols on the 98 machines and use only TCP/IP with
NetBios enabled. Should work.

"PeeJay" <(E-Mail Removed)> wrote in message
news:ben1p1$pic$(E-Mail Removed)...
> Being a complete newbie to networking, I'm very confused about
assigning
> IP addresses and even if they need to be assigned.
>
> I've studied a lot of the "how to" and "troubleshooting" info
available
> and there does not seem to be any consensus on this.
>
> Example :- I'm currently trying to set up our SOHO on a peer to peer
> basis:-
>
> 7 machines - 4 on XP Pro, 2 on W98SE and one on W2K.
> One of the XP machines has an internet connection ( ADSL via a
NIC)
> and all the other machines use that access (ICS) and that works fine.
> I set up the NW on one of the XP machines and created the diskette
> with the netsetup program. and installed it on the others.
> On the XPs - no problem
> Netsetup not for WIN2K but that machine is connecting to the net
OK
> and can see and be seen by the others ( don't ask me how I did it - no
> idea -
> " mucho suck it and see")
> The Win98s are a nightmare - one connects OK sometimes but at the
> next reboot will give the message " unable to browse the network"
> The other W98 just straight forward refuses to see see the entire
> network.
>
> ( N.B. All PCs have unique names and the same workgroup name )
>
> Maybe my query re IP addressing is not in the right area but even
if
> it's not I'd appreciate a small clarification on this and any other help
> re: the general problem .
>
> Many TIA
>
> Di Lemma
>
>

Without a server or other device on your network to automatically
assign IP addresses using DHCP, you need to assign them manually.
On each PC - Open TCP/IP properties and assign an address from the
192.168.1.x (x=1-254) group.
Make sure Client for Microsoft Network and File and Print Sharing for
Microsoft Network are installed and enabled.
Make sure all PCs are members of Workgroup (name may be changed to
suit)
Reboot each PC after addressing.

A great many thanks for this reply.

It certainly helps but at the same time leads me on to another question
i.e. what is the best strategy re: IP addresses?

Is it best to assign them or let DHCP handle it?

As far as I can see we do not have a 'server' in the true sense - just a
'main' machine that is connected to the internet via DSL and all the other
machines use it via ICS .

When I look at this 'server' (XP) and its network places I only see some of
the machines yet they are all using it for ICS.

Can anyone please advise re: a policy/strategy (if that's what required)
to sort this out?
TIA

"theshard" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Without a server or other device on your network to automatically
> assign IP addresses using DHCP, you need to assign them manually.
> On each PC - Open TCP/IP properties and assign an address from the
> 192.168.1.x (x=1-254) group.
> Make sure Client for Microsoft Network and File and Print Sharing for
> Microsoft Network are installed and enabled.
> Make sure all PCs are members of Workgroup (name may be changed to
> suit)
> Reboot each PC after addressing.

"Jack H" <(E-Mail Removed)> wrote in message
news:bf1jkt$p7r$(E-Mail Removed)...
> A great many thanks for this reply.
>
> It certainly helps but at the same time leads me on to another question
> i.e. what is the best strategy re: IP addresses?
>
> Is it best to assign them or let DHCP handle it?

It depends. Some client/server apps might work better with manually
assigned IP addresses. In general DHCP simplifies management of multiple
computers.

>
> As far as I can see we do not have a 'server' in the true sense - just a
> 'main' machine that is connected to the internet via DSL and all the other
> machines use it via ICS .

Server/client relationships are relative and only useful to talk about in
specific contexts. One machine might be the DHCP server and one of its
clients might be the accounting server. Etc.
>
> When I look at this 'server' (XP) and its network places I only see some
of
> the machines yet they are all using it for ICS.
>

The invisible machines may not have file sharing enabled? (Network
properties)

> Can anyone please advise re: a policy/strategy (if that's what
required)
> to sort this out?
> TIA

Spend a lot of time reading about network protocols and topographies, then
spend years tinkering with the network configuration settings. After that,
you'll be able to make most things work the way you want most of the time.
Sorry if that sounds glib, but you asked.

Will Niccolls