Server Communication Issue

I have a remote site connected to the primary site via VPN. Our network is
a 2003 native domain. The remote site has 3 servers: a domain controller,
a sql server, and a terminal server. 2 of these servers (the DC and the
terminal server) have communication issues with a single server (named
WebServer32) at our primary location. The sql server communicates properly
with WebServer32.

All 3 remote servers use the remote DC as the primary DNS\WINS server. All
3 servers can properly resolve the hostname and can perform simple
communication such as command line FTP or a "net use" command. All 3
servers can ping WebServer32 via hostname or IP. All 3 servers are
connected to the same switch in the same rack. Finally, all 3 servers can
communicate properly with every other server at our primary site.

The remote DC and terminal server show the following symptoms (logged in as
the domain administrator to assure all privileges):

1. Attempting to use IE to navigate to http://webserver32 (or using the IP
in place of the hostname) results in an "Internet Explorer cannot display
the webpage" error. The IIS log shows the attempted request:

2008-01-16 18:37:05 W3SVC1 172.16.1.4 GET /iisstart.htm - 80 -
192.168.210.10
Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CL R+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506 .30)
200 0 1236

2. Attempting to connect to WebServer32 using Windows Explorer (whether by
navigating the domain tree OR simply entering \\webserver32) will show the
available network shares. However, selecting a share results in an error
message of:

\\Webserver32\sharename is not accessible. You might not have permission to
use this network resource. Contact the administrator of this server to find
out if you have access permissions. The semaphore timeout period has
expired.

Attempting to access directly with \\webserver32\sharename results in an
error message of:

\\Webserver32\sharename is not accessible. You might not have permission to
use this network resource. Contact the administrator of this server to find
out if you have access permissions. The specified network name is no
longer available.

Any ideas as to why this is happening?

Does the web server work flawlessly from within its own site? It sounds as
though you may have a problem with the VPN, e.g MTU's
Anthony, http://www.airdesk.com


"James McKenzie" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have a remote site connected to the primary site via VPN. Our network is
>a 2003 native domain. The remote site has 3 servers: a domain controller,
>a sql server, and a terminal server. 2 of these servers (the DC and the
>terminal server) have communication issues with a single server (named
>WebServer32) at our primary location. The sql server communicates properly
>with WebServer32.
>
> All 3 remote servers use the remote DC as the primary DNS\WINS server.
> All 3 servers can properly resolve the hostname and can perform simple
> communication such as command line FTP or a "net use" command. All 3
> servers can ping WebServer32 via hostname or IP. All 3 servers are
> connected to the same switch in the same rack. Finally, all 3 servers can
> communicate properly with every other server at our primary site.
>
> The remote DC and terminal server show the following symptoms (logged in
> as the domain administrator to assure all privileges):
>
> 1. Attempting to use IE to navigate to http://webserver32 (or using the
> IP in place of the hostname) results in an "Internet Explorer cannot
> display the webpage" error. The IIS log shows the attempted request:
>
> 2008-01-16 18:37:05 W3SVC1 172.16.1.4 GET /iisstart.htm - 80 -
> 192.168.210.10
> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CL R+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506 .30)
> 200 0 1236
>
> 2. Attempting to connect to WebServer32 using Windows Explorer (whether
> by navigating the domain tree OR simply entering \\webserver32) will show
> the available network shares. However, selecting a share results in an
> error message of:
>
> \\Webserver32\sharename is not accessible. You might not have permission
> to use this network resource. Contact the administrator of this server to
> find out if you have access permissions. The semaphore timeout period
> has expired.
>
> Attempting to access directly with \\webserver32\sharename results in an
> error message of:
>
> \\Webserver32\sharename is not accessible. You might not have permission
> to use this network resource. Contact the administrator of this server to
> find out if you have access permissions. The specified network name is
> no longer available.
>
> Any ideas as to why this is happening?
>

The server works flawlessly when connected to from:

All servers and clients at the primary site.
All servers and clients at another remote site
One server and all clients at the remote site at which the 2 servers have
communications problems.

I would think that if the MTU's were causing this, I'd have problems with
more than just the 2 servers. However, we are looking into the VPN config
and also the switches to check. Anything else you can think of?


"Anthony" <(E-Mail Removed)> wrote in message
news:e$(E-Mail Removed)...
> Does the web server work flawlessly from within its own site? It sounds as
> though you may have a problem with the VPN, e.g MTU's
> Anthony, http://www.airdesk.com
>
>
> "James McKenzie" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I have a remote site connected to the primary site via VPN. Our network
>>is a 2003 native domain. The remote site has 3 servers: a domain
>>controller, a sql server, and a terminal server. 2 of these servers (the
>>DC and the terminal server) have communication issues with a single server
>>(named WebServer32) at our primary location. The sql server communicates
>>properly with WebServer32.
>>
>> All 3 remote servers use the remote DC as the primary DNS\WINS server.
>> All 3 servers can properly resolve the hostname and can perform simple
>> communication such as command line FTP or a "net use" command. All 3
>> servers can ping WebServer32 via hostname or IP. All 3 servers are
>> connected to the same switch in the same rack. Finally, all 3 servers
>> can communicate properly with every other server at our primary site.
>>
>> The remote DC and terminal server show the following symptoms (logged in
>> as the domain administrator to assure all privileges):
>>
>> 1. Attempting to use IE to navigate to http://webserver32 (or using the
>> IP in place of the hostname) results in an "Internet Explorer cannot
>> display the webpage" error. The IIS log shows the attempted request:
>>
>> 2008-01-16 18:37:05 W3SVC1 172.16.1.4 GET /iisstart.htm - 80 -
>> 192.168.210.10
>> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CL R+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506 .30)
>> 200 0 1236
>>
>> 2. Attempting to connect to WebServer32 using Windows Explorer (whether
>> by navigating the domain tree OR simply entering \\webserver32) will show
>> the available network shares. However, selecting a share results in an
>> error message of:
>>
>> \\Webserver32\sharename is not accessible. You might not have permission
>> to use this network resource. Contact the administrator of this server
>> to find out if you have access permissions. The semaphore timeout
>> period has expired.
>>
>> Attempting to access directly with \\webserver32\sharename results in an
>> error message of:
>>
>> \\Webserver32\sharename is not accessible. You might not have permission
>> to use this network resource. Contact the administrator of this server
>> to find out if you have access permissions. The specified network name
>> is no longer available.
>>
>> Any ideas as to why this is happening?
>>
>
>