New servers not visible on WAN 1

[rojariggs]

Hi

We have a 3rd party managed WAN consisting of open routers connecting nine sites to Head Office. All servers are located at Head Office.

I only started here recently so have inherited a number of the servers - all of which are working fine. I have built a handful of servers myself all of which work 100% OK on the LAN but are not visible on the WAN.

The new servers:

1. Can be pinged or tracert'd by either name or IP
2. Cannot be net viewed or browsed to by eother name or IP
3. Can be connected to via HTTP/IIS by IP but not by name

Existing 2008R2 servers have Windows firewall enabled and Kaspesrky AV. I have tried the new servers with these enabled and disabled and makes no difference.

Yesterday I built a test 2008R2 server to test this problem (ie no software, no apps, default settings) and it cannot be net viewed or browsed.

There mist be something really fundamental (and hopefully) simple missing on my new servers but I'm buggered if I can find it!

Any thoughts?

Cheers

Rog

 

[rojariggs]

Sorry, I should have said I have also tried the following:

1. Turn on Network Discovery (although not enabled on working servers)
2. Flushdns
3. Checked DNS & WINS (although I don't think these are the problem as name can be resolved ny ping and tracert)
4. Checked various registry settings as per post on forums but all are set the same as working servers.

Cheers

Rog

 

[NortonES2]

Check the default gateway

-------------------------------

If it doesn't leak oil it must be empty!!

 

[NortonES2]

PS when you run ping -a ip address does it return the FQDN or just the server name?

-------------------------------

If it doesn't leak oil it must be empty!!

 

[rojariggs]

Hi

Thanks for the replies. The default gateway is set to the DC on the servers and is set to the site router at each remote location.

ping -a returns FQDN

Cheers

Rog

 

[NortonES2]

So your domain controller is your router for head office? Would check the original servers that work to see what their default gateway is.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[rojariggs]

Sorry, the DC isn't the DG for Head Office. An ISA Server is the DG and is the same on all servers old and new.

Cheers

Rog

 

[NortonES2]

Have you added the required rules to the windows firewall? As a test don't disable the firewall but turn it off for the Domain network (disabling the firewall blocks all traffic to the server).

-------------------------------

If it doesn't leak oil it must be empty!!

 

[rojariggs]

I've checked the rules against a working server (and checked the Windows Services) and can see no difference.

I'll test with just the Domain FW off...

Cheers

Rog

 

[rojariggs]

Just tried that. Same result. Net view gives me a system error 53. I get the same if I leave the firewall on and set inbound and outbound to allow.

Cheers

Rog

 

[NortonES2]

I assume the new servers are on the same subnet as the existing servers.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[rojariggs]

The servers old and new are on the same subnet (10.0.1.x/255.255.255.0)

The remote PCs are on (for example) 10.0.2.x/255.255.255.0

Connections from the new servers to the remote PCs are fine

Cheers

Rog

 

[rojariggs]

Thanks for your post about the subnet. It got me thinking and realised I hadn't looked at static routes on the working servers. So I ran a ROUTE PRINT on a working server and sure enough they have persistent routes for the WAN DG to each of the remote sites (in addition to the ISA as DG for the Internet).

Added a new persistent route to my test server and works a treat!

Thanks for all your help

Cheers

Rog

 

[NortonES2]

Glad you got it working.

-------------------------------

If it doesn't leak oil it must be empty!!