On a machine that does not exhibit any problem go to a command prompt and
run "ipconfig /all |more" to see the full IP configuration. Do the same on
the machine that has the problem. You might want to use "ipconfig /all
>results.txt" to capture the information to file for printing or whatever.
Compare the results from both machines and identify any configuration
differences.
The ability to see your LAN and not see the Internet might indicate an
incorrect gateway setting or a problem with name resolution. Ping an
internet address by name and by IP number to help identify whether or not
name resolution is the issue. If both fail (ping by name and IP) see if you
can do this from a good machine. If you can ping an external machine by IP
but not by name then look at your DNS settings.
Did I understand you to say that there is no firewall/proxy device at all in
your configuration? Are all your machines visible to the internet? What
kind of device did Ameritech use to connect the DSL to the LAN? If you are
as wide open as your message seems to indicate, you are asking for trouble.
If this is the case IMO you need to pull the plug on this connection and
address the firewall issues now instead of at some time in the future.
Michael Ellis
-----Original Message-----
From: Schreiber, Scott [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 24, 2001 8:30 AM
To: NT System Admin Issues
Subject: 98 Workstation can't see server/Net
Here's one I just don't get...
I have a client (An elementary school) with an NT server and 30 nodes
running Win 98. They just got DSL installed so that all machines can access
the Internet.
The way the Ameritech guy set them up, all computers(including the server)
are getting IP addresses from an upstream DHCP somewhere in Ameritech. (I
know, it's not at all secure. I'll address that with the client later.)
Most of the machines work ok with this and can see the lan and the local
server and the Internet. About 6 of them can't get out to the internet, but
can access the server...their network configurations are identical.
On one machine I removed and reinstalled tcp/ip protocol and now that
machine can't even see the server. I get the "No Domain Server was
available.." message.
Any suggestions on where to look, what to look for?
At some time in the future I plan on advising them to go with private IP
(192.168.x.x) for the internal network, and a firewall device like the
Linksys or something that does aliasing.
Thanks for any suggestions in advance!
Scott
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
