MS Networks with dynamic DHCP (was: NETBEUI and TCP/IP

  • Thread starter Thread starter Jonathan Sachs
  • Start date Start date
J

Jonathan Sachs

Martin: I have a related problem; perhaps you or others can help.

I've tradidionally used MS Networks over TCP/IP on my home network.

I recently moved and had to subscribe to a new DSL service which
requires me to use DHCP instead of a fixed IP address. What does that
do to my MS Networks configuration? Must I switch it over to NETBEUI,
or is there some reasonably clean way to avoid that?

I'm particularly concerned that if my ISP's DHCP server goes down, or
I must disconnect my network from the Internet for any reason, my LAN
will cease to operate.

My mail address is jsachs177 at earthlink dot net.
 
Jonathan said:
Martin: I have a related problem; perhaps you or others can help.

I've tradidionally used MS Networks over TCP/IP on my home network.

I recently moved and had to subscribe to a new DSL service which
requires me to use DHCP instead of a fixed IP address. What does that
do to my MS Networks configuration? Must I switch it over to NETBEUI,
or is there some reasonably clean way to avoid that?

I'm particularly concerned that if my ISP's DHCP server goes down, or
I must disconnect my network from the Internet for any reason, my LAN
will cease to operate.

My mail address is jsachs177 at earthlink dot net.
Click to expand...

Perhaps you would want to purchase a small home firewall/router with
enough ports for all of your computers. You can connect the firewall to
the DSL service and hook the rest of your network behind it. That
sounds like the simplest way to avoid any changes to your existing
nework setup.

I'm just curious:
If you hook up all your computers to the ISP, would they be able to
communicate with each other with just TCP/IP? If this is the case, then
wouldn't someone not part of your network be able to reach your computer
also?
 
k2list said:
Perhaps you would want to purchase a small home firewall/router with
enough ports for all of your computers....
Click to expand...

Not unless I have to. I'm in school, not working for the present, and
money is very tight. Also, I only very occasionally use more than one
computer, so the extra hardware would rarely be useful.
I'm just curious:
If you hook up all your computers to the ISP, would they be able to
communicate with each other with just TCP/IP?
Click to expand...

Yes; that's the way I did it before I moved.
If this is the case, then wouldn't someone not part of your
network be able to reach your computer also?
Click to expand...

I think not -- I don't think MS Networks will work across network
segments. In any case I define all of my disk shares to require
passwords, so even if someone could reach my computer, they couldn't
reach my files.

My mail address is jsachs177 at earthlink dot net.
 
I have made some progress with this, but I still have a problem.

I decided to avoid the original problem by installing NWLink protocol
in both machines. (With Windows XP Microsoft has dropped support for
NETBEUI, which would otherwise have been my natural choice.) Now the
Windows XP machine can see the windows to thousands machine and can
transfer files in both directions, but the Windows 2000 machine
doesn't see the Windows XP machine at all. What could cause this? How
can I fix it?

My mail address is jsachs177 at earthlink dot net.
 
Back
Top