Setting up a home network

[Homerio]

I have been trying to set up my home network again after updating the host computer to win2k pro. The host computer which my cable internet goes to is a p2 450 with 2 ethernet cards, one for the modem and one for the conneciton to the hub, which is a netgear 5 port ethernet hub. The problem I am having is that none of teh computers on teh network want to acknowlege each others existance. Trying to connect my xp machine it says it is connected to teh network, but doesnt receive any data, the same occurs with the network link on the host win2k machine. My ethernet hub occasionly has one of teh lights flash for a while and i cant ping each computer from the other. Everything is set to automatic configuration as all the guides i've looked at so far have said.

Any suggestions?

[Gayle29uk]

Is your cable modem acting as a DHCP server? If not it might be a good idea to set it up as one Either that or (my preference) set the host as a DHCP server/router with the modem as a DHCP client on another subnet. I don't know why but that always seems neater to me.

[MT]

come find uncle MT, I'll guide you thru it sexy homer.

ofcourse the cable modem is set up as a dhcp server else how do you get your ip address? duh.

anyway. make the nic on the gateway attached to the modem use dhcp to get the ip etc then that machine should beable to go on the internet. youll need to give it an ip on the nic connected to the hub, e.g. 192.168.0.1

now unless the gateway is also running its own dhcp server on the nic connected to the hub (pointless really) youll have to set the ips etc n all the nics on all the workstations, they should only be dhcp if your gateway is set up as a server.

then makesure the gateways ip (192.168.0.1) is entered into the nic settings of all the workstations

and voila

------------

also i just have to say i was there when MT's sig took place and it was stunningly beautifull!

[Gayle29uk]

Originally posted by Idi
ofcourse the cable modem is set up as a dhcp server else how do you get your ip address? duh.

From the host of course. As far as I'm concerned anything connected to my linux box does what it's told when it's told and is always a client, never a server. That way I know everything is run from one place and if it all goes runny I know where the problems lie

now unless the gateway is also running its own dhcp server on the nic connected to the hub (pointless really)

Actually, anything BUT pointless. It makes everything so much easier being able to plug new kit in and have it set itself up with all the network details.

youll have to set the ips etc n all the nics on all the workstations

See above, set up a DHCP server (it's win2k, it's EASY!) and you don't need to bother with that ever again.

then makesure the gateways ip (192.168.0.1) is entered into the nic settings of all the workstations

Assumptions are bad That's the internal IP address of MY server, could even be yours, but how do you know that's the subnet he's using?

[Homerio]

cable Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : aptiva
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC (3C
905-TX)
Physical Address. . . . . . . . . : 00-60-08-60-F5-0E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 80.6.38.83
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 80.6.38.254
DHCP Server . . . . . . . . . . . : 62.252.0.20
DNS Servers . . . . . . . . . . . : 194.168.8.100
194.168.4.100
Lease Obtained. . . . . . . . . . : 22 December 2002 09:35:37
Lease Expires . . . . . . . . . . : 22 December 2002 22:23:43

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-C0-DF-0D-AF-4F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.91.233
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

xp Windows ip configuration

Host name . . . . . . . . . . . . : jez
Primary Dns Suffix . . . . . . . :
Mode Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adpater Local Area Connection:

Connection-specific Dns Suffix . :
Description . . . . . . . . . . . : NETGEAR FA311 Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-02-E3-21-C4-EE
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autpconfiguration IP Address. . . : 169.254.71.151
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

[zenopus]

Originally posted by Homerio
Host
Adapter - Internet:
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 80.6.38.83
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 80.6.38.254
DHCP Server . . . . . . . . . . . : 62.252.0.20
DNS Servers . . . . . . . . . . . : 194.168.8.100 / 194.168.4.100
Adapter - Local Area:
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.91.233
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

Client
Adapter:
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autpconfiguration IP Address. . . : 169.254.71.151
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Note that MS have wisened up and actually follow some RFCs. The IP addresses you have on your local interfaces are fallback addresses, you might want to set up a DHCP server on your local network (eg. on the Gateway box) to allocate IP addresses from a range allocated for such purposes.

RFC 3330 - Special-Use IPv4 Addresses
169.254.0.0/16 - This is the "link local" block. It is allocated for communication between hosts on a single link. Hosts obtain these addresses by auto-configuration, such as when a DHCP server may not be found.
...
192.168.0.0/16 - This block is set aside for use in private networks. Its intended use is documented in [RFC1918]. Addresses within this block should not appear on the public Internet.

Can the Client (the one with the 169.254.71.151 IP address) ping the host (on interface 169.254.91.233) ?
( command window> ping 169.254.91.233 )

Could be you just need to configure a default gateway on the client - the IP address should be the local interface on the host.
You may have to fiddle with DNS settings as well.

Originally posted by Gayle28uk
From the host of course. As far as I'm concerned anything connected to my linux box does what it's told when it's told and is always a client, never a server. That way I know everything is run from one place and if it all goes runny I know where the problems lie


Actually, anything BUT pointless. It makes everything so much easier being able to plug new kit in and have it set itself up with all the network details.


See above, set up a DHCP server (it's win2k, it's EASY!) and you don't need to bother with that ever again.


Assumptions are bad That's the internal IP address of MY server, could even be yours, but how do you know that's the subnet he's using?

you're trying to hard to make me look stupid. That IP wasnt an assumption, it was an example.

And DHCP is gay.

Also we are not talking about your network we are talking about his.

[Gayle29uk]

Originally posted by Idi
you're trying to hard to make me look stupid.

Originally posted by Idi
ofcourse the cable modem is set up as a dhcp server else how do you get your ip address? duh.[/b]

You're doing a rather good job of it yourself, I'm merely helping.

[b]then makesure the gateways ip (192.168.0.1) is entered into the nic settings of all the workstations

That IP wasnt an assumption, it was an example.

That's certainly not how you posted it.

Homerio: Looking at the stuff you posted I'll stick with my initial suggestion of setting up a DHCP server on the win2k box (but assign the NIC that connects to the internal network a static IP address of 192.168.0.1) with the internal network on subnet 192.168.0.0 netmask 255.255.255.0. Have the cable modem configured with a static IP of 192.168.1.2 and put that on the second NIC which you assign IP 192.168.1.1 to. This allows you to control all traffic from your win2k machine and makes the internal network dynamic (for easy expansion/constriction) while giving you a static route to the internet

In case you don't know this stuff the broadcast IP for your internal net should be set to 192.168.0.255 and your XP (and any other machines) set as DHCP clients. If it's all set up properly everything will just fall into place beautifully

[Slidey]

Originally posted by Gayle28uk
You're doing a rather good job of it yourself, I'm merely helping.


That's certainly not how you posted it.

Homerio: Looking at the stuff you posted I'll stick with my initial suggestion of setting up a DHCP server on the win2k box (but assign the NIC that connects to the internal network a static IP address of 192.168.0.1) with the internal network on subnet 192.168.0.0 netmask 255.255.255.0. Have the cable modem configured with a static IP of 192.168.1.2 and put that on the second NIC which you assign IP 192.168.1.1 to. This allows you to control all traffic from your win2k machine and makes the internal network dynamic (for easy expansion/constriction) while giving you a static route to the internet

In case you don't know this stuff the broadcast IP for your internal net should be set to 192.168.0.255 and your XP (and any other machines) set as DHCP clients. If it's all set up properly everything will just fall into place beautifully

you talk so much crap without thinking, i dont think you should try and make anyone else look anything. give it up

[Gayle29uk]

Originally posted by Slidey
you talk so much crap without thinking, i dont think you should try and make anyone else look anything. give it up

So explain what's wrong with it rather than simply criticising.

Originally posted by Gayle28uk
You're doing a rather good job of it yourself, I'm merely helping.

That's certainly not how you posted it.

Originally posted by Idi
youll need to give it an ip on the nic connected to the hub, e.g. 192.168.0.1

Really? How about I give you a quick lesson in English and Latin.

e.g. stands for exempli gratia, which means 'for example' which is exactly what I gave with that IP address.

[Homerio]

it works now ta