Windows Server

clevere · Guest

Came in this morning, and noticed I had no internet on my desktop. After
quite a bit of trouble shooting, I was able to cross out my firewall, and
router as the problem (I get internet connecting directly to them).

So, from the Server, plugged into a known good working internet connection,
no internet access.

My Network Nic (dual nic setup) is as follows:

192.168.100.24
255.255.255.0
192.168.100.1

DNS:
192.168.16.2 (IP address of second nic)

This is my normal setup. I added my router as a DNS object, and poof. So
the setup for the network nic is:

192.168.100.24
255.255.255.0
192.168.100.1

DNS:
192.168.16.2 (IP address of second nic)
192.168.100.1

Now things are working great. I see no errors in the even viewer, no DNS
errors ... Any idea what I need to look at to fix this problem? (Yup, I
rebooted already)

Lanwench [MVP - Exchange] · Guest

clevere wrote:

clevere · Guest

Yes, I am aware of that. And that has been working for over a year now. This
morning, it's broke. Having just the server IP isn't working.

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:uAAlA3V$EHA.3908@TK2MSFTNGP12.phx.gbl...

Colby · Guest

Perhaps the IPs of the ISP's DNS server have changed, or perhaps those
servers have gone down?

Possibly removing those forwarders will fix the issue by causing your local
DNS server to use root hints instead of your ISP's DNS servers.

"clevere" wrote:

Jim K · Guest

If your local ISP DNS servers are down, your own DNS should give up and
use the hints. There's a time out setting on the forward properties. I
think the default is 5 sec. You can get rid of the forwarders at any
rate--it doesn't hurt anything.

But you said you have "no internet connection". Do you really mean that?
Or do you just mean no DNS working? If you can't even ping out, then
DNS is not the first issue.

Jim

Colby wrote:

clevere1 · Guest

With this setup (which has been working for years)

(External NIC to internet)
192.168.100.2
255.255.255.0
Gateway, 192.168.100.1

DNS:
192.168.16.2 (which is the internal NIC's IP).

I was unable to ping, or reach any outside address. So I added the DNS
servers of my ISP, and my router to the External NICS DNS information so now
the TCP/IP settings for the External nic look something like this:

192.168.100.2
255.255.255.0
Gateway, 192.168.100.1

DNS:
192.168.16.2 (which is the internal NIC's IP).
192.168.100.1

I can now ping, and reach outside addresses from the server, and the lan.

"Jim K" <"jim-skip this part-"@siena.org> wrote in message
news:ePFLZEZ$EHA.3368@TK2MSFTNGP10.phx.gbl...

Jim · Guest

You must have been pinging domain names instead of IP's when you say you
weren't able to ping or reach any outside address. If all you did was
add DNS servers, it should't affect your ability to ping, say, your
ISP's DNS or your router's internet IP.

So, for some reason, apparently your SBS DNS has stopped working
correctly. Did yout try removing the forwarders? If you can't log onto
your own local domains default web page from a client, then DNS may not
be working at all (be sure and flush the DNS cache on the client before
you do any DNS testing: ipconfig /flushdns).

Good luck!

Jim

clevere1 wrote:

	Windows Server Forum Index -> Small Business Server 2003	All times are GMT
Page 1 of 1