The people who used to log onto the network via dial-up (just like our
normal internet customers) have never had an LMHosts file, whether they
were using NT4 or Win95. Client for MS Networks (Win95) handles this in
conjuction with a workgroup name matching the NT domain name for the
network. All employees can see the entire network with no problems when
their IP is in the same C-class as the IPs for the servers and other
workstations in the office. Once the dial-up IPs were changed to a
different C-class (dynamically assigned as always), no one could log onto
the network anymore.
TCP/IP is the only protocol in use.
> At 10:15 AM 4/16/98 -0400, you wrote:
> >Since day one, our employees have been able to dial-up through our Maxes
> >and log onto the NT network here in the office just as if they were here
> >the building. Up until recently, all network-related devices as well as
> >computers in the office and all dial-up IP address have been in the same
> >subnet (184.108.40.206). A couple of weeks ago, we moved all dial-up IPs
> >a different subnet (220.127.116.11). Everyone can poke around on the
> >without any problems as well as get their mail, view any website on any
> >our servers, etc., but no one can log onto the network anymore (unless
> >they've got a dedicated IP address in the 18.104.22.168 range). All
> >machines can see all machines as far as ping/traceroute, http, ftp, etc.
> >go--just can't access network resources or get a listing of the machines
> >network domain (unless the user's IP falls in the original subnet).
> >Changing one of the workstations on the network here to an IP address of
> >199.44.20.x will make it unable to see the network (though can still see
> >anything on the internet including our own webservers/mailservers,
> >Does anyone have any idea why this is happening?
> >22.214.171.124 = 126.96.36.199 (our Cisco router)
> >All NT servers have both IPs set as gateways.
> >Josh Hillman
> > ----------------------------------------------------------
> > NTISP Mailing List firstname.lastname@example.org