Connecting Win2K to a WinXP Network

[Chris Simmons]

i have a win2k machine that i want to connect to a winxp machine and share
my dial-up connection. i already have 1 other winxp machine working fine.

my win2k machine is set to obtain an ip address from my winxp machine, but
that isn't working. it gets some ip that is not part of my network, and if i
manually set the ip address it doesn't work, and i cannot ping either
machines.

-chris-

 

[Pegasus \(MVP\)]

i have a win2k machine that i want to connect to a winxp machine and share
my dial-up connection. i already have 1 other winxp machine working fine.

my win2k machine is set to obtain an ip address from my winxp machine, but
that isn't working. it gets some ip that is not part of my network, and if i
manually set the ip address it doesn't work, and i cannot ping either
machines.

-chris-

A good starting point would be to post the IP addresses
used by the various machines.

 

[Herb Martin]

i have a win2k machine that i want to connect to a winxp machine and share
my dial-up connection. i already have 1 other winxp machine working fine.

my win2k machine is set to obtain an ip address from my winxp machine, but
that isn't working. it gets some ip that is not part of my network, and if

i

If it use 169.254.x.y then it is using APIPA (making up it's own address)
because the WinXP machine is not offering any address.

WinXP cannot be a FULL DHCP server so we must assume you have
enabled ICS on that machine -- this will hand out addresses from the
range 192.168.0.2+ on the INTERNAL network if you share the
external connection.

manually set the ip address it doesn't work, and i cannot ping either
machines.

Cannot ping by name or also by number? Name is irrelevant until
you have IP working.

What addresses are involved? (And subnet mask.)

 

[Chris Simmons]

ok, yes i have enabled ICS on winxp. ip's involved are 196.168.0.1 on winxp
and i win2k is getting 169.254.something or other... subnet mask is
255.255.255.0

 

[Pegasus \(MVP\)]

Your Win2000 machine is unable to reach the DHCP server
on the WinXP machine. This is why the WinXP machine
uses a subnet of 192.168.0 (not 196.168.0, as you write!)
whereas the Win2000 machine uses 169.254.xxx. The
machines will not talk to each other while they are on
different subnets!

Start off by giving the Win2000 machine a fixed IP
address, e.g. 192.168.0.10, to establish network
connectivity. You must also turn off your firewalls
during the testing phase. Later on, when you have
network connectivity, you can look at ICS.

ok, yes i have enabled ICS on winxp. ip's involved are 196.168.0.1 on winxp
and i win2k is getting 169.254.something or other... subnet mask is
255.255.255.0

and

 

[Herb Martin]

ok, yes i have enabled ICS on winxp. ip's involved are 196.168.0.1 on winxp
and i win2k is getting 169.254.something or other... subnet mask is
255.255.255.0

Then either you network is faulty (physical wire, NICs, etc) or
the ICS is enable on the WRONG NIC.

One shares the EXTERNAL NIC or Modem -- ICS controls the
internal NIC.

If the other machine gets a 169.254.x.y address (APIPA) this is a
sign that the ICS machine either didn't hear the DHCP request or
couldn't respond.

Check cables, hub, etc. How are they hooked together? Hub or
crossover cable (Is is really a cross cable or a regular one?)


--
Herb Martin

and

 

[Chris Simmons]

i have given the win2k machine an ip of 192.168.0.3 and subnet of
255.255.255.0 and turned of all firewalls, and they still can't ping each
other. nic's, cable, and hub are all working fine.

Your Win2000 machine is unable to reach the DHCP server
on the WinXP machine. This is why the WinXP machine
uses a subnet of 192.168.0 (not 196.168.0, as you write!)
whereas the Win2000 machine uses 169.254.xxx. The
machines will not talk to each other while they are on
different subnets!

Start off by giving the Win2000 machine a fixed IP
address, e.g. 192.168.0.10, to establish network
connectivity. You must also turn off your firewalls
during the testing phase. Later on, when you have
network connectivity, you can look at ICS.

 

[Chris Simmons]

everything is fine. cables are normal cat5 and i have an 8 port hub which is
fine. nic's are fine as well.

ok, yes i have enabled ICS on winxp. ip's involved are 196.168.0.1 on winxp
and i win2k is getting 169.254.something or other... subnet mask is
255.255.255.0

Then either you network is faulty (physical wire, NICs, etc) or
the ICS is enable on the WRONG NIC.

One shares the EXTERNAL NIC or Modem -- ICS controls the
internal NIC.

If the other machine gets a 169.254.x.y address (APIPA) this is a
sign that the ICS machine either didn't hear the DHCP request or
couldn't respond.

Check cables, hub, etc. How are they hooked together? Hub or
crossover cable (Is is really a cross cable or a regular one?)

 

[Pegasus \(MVP\)]

Experience says that you suffer from one of these problems:

- Bad cabling
- Bad network adapter
- Bad hub
- Firewall (yes, I read that you turned it off, but I recall a thread
that extended over 10 posts until the OP admitted that his
firewall was not off, after all).

When one of my clients has this type of problem then
I wheel in my trusty laptop and run some tests to eliminate
on suspected item after the other. I would also force all
adapters to 10 MBits/s half duplex. Furthermore, I would
turn on the network adapter indicator in the System Tray.
It tells me immediately if I have a valid network connection.

 

[Chris Simmons]

i now have it working. i don't know how, it just decided to work. all i have
to do now is get the win2k machine to access the net from my winxp machine.
i have another winxp machine doing this already, but it is getting an ip
from the winxp machine with the dial-up connection.

 

[Herb Martin]

i now have it working. i don't know how, it just decided to work. all i have
to do now is get the win2k machine to access the net from my winxp machine.
i have another winxp machine doing this already, but it is getting an ip
from the winxp machine with the dial-up connection.

You need the 2k to use the XP as it's default gateway and
DNS server -- or better put it back to DHCP assigned
addressing and the XP machine will assign these with the
address.

 

[Herb Martin]

everything is fine. cables are normal cat5 and i have an 8 port hub which is
fine. nic's are fine as well.

"Fine" means nothing unless you have a cable tester or NO
problems.

 

[Chris Simmons]

sorry, fine meaning no problems

which

"Fine" means nothing unless you have a cable tester or NO
problems.

 

[Chris Simmons]

woohoo, i finally have it all working. all i did was set the prefered dns to
my win xp machine.

thanks for all the help.