Weird problem with remote VPN clients

  • Thread starter Thread starter adamofevil
  • Start date Start date
A

adamofevil

I have a Windows 2003 SBS at location #1 and another location #2 with no
server. The two locations are connected via gateway-gateway VPN. Remote
clients at location #2 point to the SBS at location #1 for DNS which is
configured to forward external requests to ISP DNS. The DNS forwarding
works perfect for location #1 but when attempting to nslookup from a client
at location #2 the following is received:

DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.168.2: Timed out
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.168.2

(where 192.168.168.2 is the SBS server address)

Location #1 subnet: 192.168.168.0/24
Location #2 subnet: 192.168.0.0/24

Domain name is lenderservices.local

Remote clients at location #2 are able to resolve client names from
location #1 using hostname but not FQDN (i.e. if I ping SERVER , it takes a
while but I get a response, but if I ping SERVER.lenderservices.local it
says hostname not found).

This is weird and I can't seem to figure it out. Any help would be
appreciated.

Thanks,
Adam
 
in message
:I have a Windows 2003 SBS at location #1 and another location #2 with no
: server. The two locations are connected via gateway-gateway VPN. Remote
: clients at location #2 point to the SBS at location #1 for DNS which is
: configured to forward external requests to ISP DNS. The DNS forwarding
: works perfect for location #1 but when attempting to nslookup from a
client
: at location #2 the following is received:
:
: DNS request timed out.
: timeout was 2 seconds.
: *** Can't find server name for address 192.168.168.2: Timed out
: *** Default servers are not available
: Default Server: UnKnown
: Address: 192.168.168.2
:
: (where 192.168.168.2 is the SBS server address)
:
: Location #1 subnet: 192.168.168.0/24
: Location #2 subnet: 192.168.0.0/24
:
: Domain name is lenderservices.local
:
: Remote clients at location #2 are able to resolve client names from
: location #1 using hostname but not FQDN (i.e. if I ping SERVER , it takes
a
: while but I get a response, but if I ping SERVER.lenderservices.local it
: says hostname not found).
:
: This is weird and I can't seem to figure it out. Any help would be
: appreciated.

Pinging SERVER is resolving a NetBIOS name. SERVER is not a FQDN. NetBIOS
doesn't route but it can use TCP/IP as a transport. What is at location 2,
re: servers? How do they get their IP? What kind of router? Do the
systems at location #2 only have location #1s DNS in their network settings?
On #1, you should point the forwarder to your router, instead of your ISP,
if possible.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
 
in message
:I have a Windows 2003 SBS at location #1 and another location #2 with
:no
: server. The two locations are connected via gateway-gateway VPN.
: Remote clients at location #2 point to the SBS at location #1 for DNS
: which is configured to forward external requests to ISP DNS. The DNS
: forwarding works perfect for location #1 but when attempting to
: nslookup from a
client
: at location #2 the following is received:
:
: DNS request timed out.
: timeout was 2 seconds.
: *** Can't find server name for address 192.168.168.2: Timed out
: *** Default servers are not available
: Default Server: UnKnown
: Address: 192.168.168.2
:
: (where 192.168.168.2 is the SBS server address)
:
: Location #1 subnet: 192.168.168.0/24
: Location #2 subnet: 192.168.0.0/24
:
: Domain name is lenderservices.local
:
: Remote clients at location #2 are able to resolve client names from
: location #1 using hostname but not FQDN (i.e. if I ping SERVER , it
: takes
a
: while but I get a response, but if I ping SERVER.lenderservices.local
: it says hostname not found).
:
: This is weird and I can't seem to figure it out. Any help would be
: appreciated.

Pinging SERVER is resolving a NetBIOS name. SERVER is not a FQDN.
NetBIOS doesn't route but it can use TCP/IP as a transport. What is
at location 2, re: servers? How do they get their IP? What kind of
router? Do the systems at location #2 only have location #1s DNS in
their network settings? On #1, you should point the forwarder to your
router, instead of your ISP, if possible.
Click to expand...

There are 4 workstations and no servers at location #2. I configured all 4
computers with static addresses 192.168.0.100-103, the gateway/router is
192.168.0.1 and DNS is 192.168.168.2 which is at location #1. Both
locations are connected via VPN using Netgear FVS318 routers which have
DHCP disabled. Location #1 gets DHCP from the SBS server. The systems at
location #2 ONLY have location #1s DNS in their network settings. I will
try changing the forwarder to the router instead of ISP and let you know
the results.
 
Back
Top