Avatar of ToddB02
ToddB02
 asked on

SBS Networking Issues

I Have a SBS 2008 that was setup before I took over, we are in the process of changing ISP's  When I change the settings on the router to the new ISP Static I am unable to get out to the internet from the small business server or even ping public IP addresses.  If I go back to the old ISP on the router everything works fine.

Nothing has changed on the private network, on a workstation if I put in a public DNS server I am able to get out to the internet just fine if I put the DNS back to the small business server no joy.  Once I go back to the old ISP everything works fine.

I have rerun the fix my internet wizard with no luck.  I'm guessing someone ran the wizard in the beginning of the servers setup and did the router config and somewhere in the registry it is remembering the old router config even though that shouldn't matter.

The router still has the same private IP address so that hasn't changed it is just the public IP addresses that have changed.  If I configure a laptop with the public IP info on the new service I am able to get out on the internet just fine so it doesn't have anything to do with the new ISP.

Can anyone make any suggestions on what to try next short of calling Microsoft, let me know if you need any additional information.

Thanks

Todd
Microsoft Legacy OSInternet Protocols

Avatar of undefined
Last Comment
ToddB02

8/22/2022 - Mon
ktaczala

Check the DNS forwarders on sbs 2011.  MS recommends using only root hints instead of forwarders,  I prefer forwarders instead of root hints,  I've have root hints do exactly what you're experiencing.
tsaico

Just in case, I would also check to make sure the firewall rules are on groups like "Public Wan -> Internal subnet".  I had inherited a Juniper firewall one time, and the rules were are specifically the old WAN ip, so the firewall itself was not allowing anything in other than the old IP.

As for the DNS forwarders, I have seen this also, but a restart of DNS server service fixes that.
ToddB02

ASKER
Okay I've tried just using root hint or forwarders no luck.

Also when I have things setup for the old ISP I can ping public IP addresses such as 8.8.8.8 but once I change it over to the new ISP I cannot ping 8.8.8.8 But form other machines on the network I can ping 8.8.8.8 and if I change to a public name server on that machine I can get out on the internet.

I have restarted the DNS services and booted the server cold with the new ISP in place.  The firewall was replaced after I took over so nothing is configure on it to restrict traffic.

Any other ideas?
Your help has saved me hundreds of hours of internet surfing.
fblack61
ToddB02

ASKER
Okay I have now done a netsh int ip reset with no luck either.

There has to be some sort of routing table that someone setup on this server, does anyone have any ideas on what I can try to reset or look at to get this working.
ktaczala

try a tracert 8.8.8.8 from an elevated command prompt.
first response should be from the router/firewall
then everything after that is public.

if you get no connection at all, you are definitely not getting out of the server, which means somewhere, someone has locked down the nic/server to a specific IP, internally on the server. What brand is the server?  Is there some kind of OEM app running that may be blocking?
ktaczala

you can look at the routing table from a command prompt.

route print
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
ToddB02

ASKER
The Trace route doesn't hit the router when I have the new ISP active.

With the old ISP it goes out just fine.

I don't see any weird software running that would be restricting traffic.

It is a dell R310 server I have updated the NIC drivers and firmware, Bios and anything else dell had on their site that was all done before I did the netsh on the TCP/IP stack.

Below are the results of the Route print.

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0  192.168.100.254   192.168.100.12    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
    192.168.100.0    255.255.255.0         On-link    192.168.100.12    266
   192.168.100.12  255.255.255.255         On-link    192.168.100.12    266
  192.168.100.255  255.255.255.255         On-link    192.168.100.12    266
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link    192.168.100.12    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link    192.168.100.12    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0  192.168.100.254  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 13    266 fe80::/64                On-link
 13    266 fe80::9dbf:4c89:9326:164f/128
                                    On-link
  1    306 ff00::/8                 On-link
 13    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
ktaczala

How about anything in local security policies? Network access policies?
Start | Programs | Administrative Tools | Local Security Settings
Start | Programs | Administrative Tools | Network Access Policies
ktaczala

Shot in the dark,
search the registry for the old ISP address, see if anything jumps out as restricting access to that IP only.

Maybe someone found an undocumented way to lock it down.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ToddB02

ASKER
Okay I didn't find anything for the public IP's but I did find the following under the registry key

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Tcpip\Parameters\PersistentRoutes

The Key value is below

0.0.0.0,0.0.0.0,192.168.100.254,-1

Looking on my local box I don't have anything set like that in the registry.

Should I delete it?
ktaczala

No, that's your persistent route as shown in your route print.
anything in the Nic settings?
network connections, properties, adaptor configuration.
ToddB02

ASKER
Nothing that looked out of the ordinary.

Do you think if I got a new network card and installed it that would make a difference or is it probably tied to the OS?
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
ktaczala

That was my next suggestion,

Add a nic card assign a different address to the new one then change DNS listening to new nic IP see attachment
ScreenCapture.jpg
ToddB02

ASKER
Okay the new NIC kinda did the trick but not fully once I reboot with the new IP it stops working again.

After it comes back up if I change it to an IP I've never used it is okay but if I reboot none of those IPS will connect with the new ISP.

Also now every time I go into the network card properties it want's to restart the machine.

Any other ideas or is it time to call Microsoft?
ktaczala

One thing I would try is install a completely different router.  It almost sounds like the router is denying traffic.
What kind of router is installed, does the router syslog show any traffic relating to the Server IP(s)
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
ktaczala

Once you installed the new nic & configured it, did you remove the static ip info from the old nic and disable it?
ToddB02

ASKER
It is a sonicwall firewall the old nic was disabled and the IP address was removed before the restart.  It has to be something with DNS.

I did configure a different firewall and tried it at one point but I still had the issue.

When I do the tracert it never even hits the firewall but I can ping the firewalls address just fine.
ToddB02

ASKER
Is there any way to rebuild/reset DNS on the Small business server?
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
ktaczala

how about trying some dcdiags and see what they reveal.

http://technet.microsoft.com/en-us/library/cc776854(v=ws.10).aspx
ktaczala

That's the connect to internet and fix my network wizards.  Since it's a DC removing/reinstalling DNS is not an option.
ToddB02

ASKER
The DCDIag log file is attached.

I also noticed a lot of dcom errors as well trying to talk to machines.
DCDiag.txt
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
ktaczala

Check active directory users and computers.  Is the DC in the OU called Domain Controllers?

If not it should be. If it's not examine which GPO's are being applied to it in detail.
 I don't think to Replication issues are critical since this is a single DC environment.

here's a link for the "failed test NCSecDesc" another non issue.
 http://support.microsoft.com/kb/967482
ASKER CERTIFIED SOLUTION
ToddB02

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ToddB02

ASKER
Ended up calling MS support to resolve the issue.