local server IP address unreachable

[christopher]

Greetings!

I am changing ISP's from fixed IP's on several machines to DHCP. One
of the boxes (FreeBSD) can't acquire a lease (probably because it was
once configured as a DHCPD / NAT server and there is a bad setting
somewhere. Yes I have disabled DHCPD and NATD, but the dhclient says
it can't find the interface for the nic). It really doesn't need to
be on the internet, as long as the other computers can find it locally
by IP address, so I can assign the machine a local address. aren't
there simple routing table additions that I can use to make these
machines see each other? When I look at route add (windows) I don't
know what to use for a gateway.

Cheers!
-- clh

 

[christopher]

Visibility of one computer to another is a function of connectivity. Are the
Windows computers (I presume Windows XP, since you're asking here) able to
successfully ping the FreeBSD computers? Start there, and deal with visibility
after you verify connectivity.

no I can't ping. the windows computer is online with a 67.x.x.x ip
address. I can set up the FreeBSD computer with a static ip like
192.0.3.1, but they can't ping each other (because they are on
different subnets? because there is no real gateway between them?)
Thanx!

--
Cheers,
Chuck, MS-MVP [Windows - Networking]http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

 

[Chuck]

Greetings!

I am changing ISP's from fixed IP's on several machines to DHCP. One
of the boxes (FreeBSD) can't acquire a lease (probably because it was
once configured as a DHCPD / NAT server and there is a bad setting
somewhere. Yes I have disabled DHCPD and NATD, but the dhclient says
it can't find the interface for the nic). It really doesn't need to
be on the internet, as long as the other computers can find it locally
by IP address, so I can assign the machine a local address. aren't
there simple routing table additions that I can use to make these
machines see each other? When I look at route add (windows) I don't
know what to use for a gateway.

Cheers!
-- clh

Visibility of one computer to another is a function of connectivity. Are the
Windows computers (I presume Windows XP, since you're asking here) able to
successfully ping the FreeBSD computers? Start there, and deal with visibility
after you verify connectivity.

 

[christopher]

Christopher,

OK, you're going to have to provide some more information about your network.
This forum deals with Windows XP network connectivity. How does your problem
relate to that issue?

Windows XP computers - like other computers - use a route table to define
subnets, and connectivity to those subnets. But a route table entry can't
compensate for proper network design, it's simply one component in proper
network design. If you have 2 subnets, you'll need a router to connect them.
And NOT the switch (LAN) side of a NAT router either.

Thanx! I just realized what I was trying to do was incorrect and ran
out to BestBuy and picked up a router. Problem solved for $60!
-- clh

Tell us more about the network, and how everything is physically connected.
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-i...>http://nitecruzr.blogspot.com/2005/06/background-information-useful-i...

--
Cheers,
Chuck, MS-MVP [Windows - Networking]http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

 

[Chuck]

no I can't ping. the windows computer is online with a 67.x.x.x ip
address. I can set up the FreeBSD computer with a static ip like
192.0.3.1, but they can't ping each other (because they are on
different subnets? because there is no real gateway between them?)
Thanx!

Christopher,

OK, you're going to have to provide some more information about your network.
This forum deals with Windows XP network connectivity. How does your problem
relate to that issue?

Windows XP computers - like other computers - use a route table to define
subnets, and connectivity to those subnets. But a route table entry can't
compensate for proper network design, it's simply one component in proper
network design. If you have 2 subnets, you'll need a router to connect them.
And NOT the switch (LAN) side of a NAT router either.

Tell us more about the network, and how everything is physically connected.
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html

 

[Chuck]

Thanx! I just realized what I was trying to do was incorrect and ran
out to BestBuy and picked up a router. Problem solved for $60!

Sometimes, the simplest solutions are the best. Thanks for letting us know.