J
John
I have an old CPU with 2 NICs running Windows 98 and Sygate to share
my cable internet connection. This system has been running fine for 2
years with Windows 98 clients. Now I just bought a new client CPU and
installed Windows 2000 Professional on it - this connects to internet
and pings just fine, but does not see a DNS.
To be sure there was nothing wrong with the new client, I connected it
to a friend's DHCP router and it connected immediately to internet
with DNS and all.
So my question is: should I change any Windows 2000 network settings
in some way in order to get a DNS on my own system.
On my friend's network, ipconfig shows "connection-specific DNS
suffix" as: "lan", but on my own network, there is no entry there at
all.
Any pointers would be most welcome.
John
my cable internet connection. This system has been running fine for 2
years with Windows 98 clients. Now I just bought a new client CPU and
installed Windows 2000 Professional on it - this connects to internet
and pings just fine, but does not see a DNS.
To be sure there was nothing wrong with the new client, I connected it
to a friend's DHCP router and it connected immediately to internet
with DNS and all.
So my question is: should I change any Windows 2000 network settings
in some way in order to get a DNS on my own system.
On my friend's network, ipconfig shows "connection-specific DNS
suffix" as: "lan", but on my own network, there is no entry there at
all.
Any pointers would be most welcome.
John