Re: Server 2003 VPN

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Yep - sure does.
With two simple commands, you've just validated these things:
1. the VPN client can pass traffic to the internal network
2. name resolution is failing for VPN clients

Make sure the VPN client IP configuration includes:
1. DNS (and/or WINS) servers for the internal network
2. DNS suffix appropriate top the internal domain structure

How are the VPN clients assigned their IP addresses; from a static pool or via DHCP?
--
--
Jim Harrison [ISA SE]
Read the help, books and articles!

This posting is provided "AS IS" with no warranties, and confers no rights.

"Joel" <priamyd@xxxxxxxxxxx> wrote in message news:6oCdnYgCq4os0eLZnZ2dnUVZ_v6dnZ2d@xxxxxxxxxxxxxx
ping to IP Address:
replies without issue

ping to name:
ping request could not find the host 'server.' please check the name and
try again.

i hope this clarifies.

- joel -


"Jim Harrison (MSFT)" <jmharr@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eaFjrGRhGHA.4656@xxxxxxxxxxxxxxxxxxxxxxx
You can't get that error for both of those tests.
To clarify:
Q1 used the name of the server in the "ping" command
Q2 used the IP address of the server in the "ping" command

If the server name can't be resolved, you'll see "host not found" or
similar
If no response is received, you'll get "timed out" or similar
If the routing structure doesn't know how to get to that server IP, you'll
see "unreachable"

--
--
Jim Harrison [ISA SE]
Read the help, books and articles!

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Joel" <priamyd@xxxxxxxxxxx> wrote in message
news:fs-dnRtb4LVTmePZnZ2dnUVZ_tqdnZ2d@xxxxxxxxxxxxxx
i've attempted both. 'destination host not found'

i've even tried '\\servername\sharename' and it could not reach the
server.
it came back basically saying that the endpoint (ie. the server) did not
exist, or could not be contacted.

- joel -

"Jim Harrison (MSFT)" <jmharr@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:us7Q4%23EhGHA.5088@xxxxxxxxxxxxxxxxxxxxxxx
That makes it a bit easier, if a bit off-topic.

Q1 - what is the result of "ping servername" from the VPN client?
Q2 - what is the result of "ping serveripaddress" from the VPN client?

--
--
Jim Harrison [ISA SE]
Read the help, books and articles!

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Joel" <priamyd@xxxxxxxxxxx> wrote in message
news:0POdneizA-SmK-HZRVn-rw@xxxxxxxxxxxxxx
no ISA involved at all.

"Jim Harrison (MSFT)" <jmharr@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eOpW8TGgGHA.1264@xxxxxxxxxxxxxxxxxxxxxxx
Is ISA involved here?

--
--
Jim Harrison [ISA SE]
Read the help, books and articles!

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Joel" <priamyd@xxxxxxxxxxx> wrote in message
news:Au-dnQzR3rWHkuvZnZ2dnUVZ_vydnZ2d@xxxxxxxxxxxxxx

"Joel" <priamyd@xxxxxxxxxxx> wrote in message
news:UtydnTAu9NfYE-7ZRVn-sw@xxxxxxxxxxxxxx
i have a Verizon Business Class DSL, which goes into a 3Com wireless
router. it is passing all VPN traffic to the 2k3 Server.

the client connects to the VPN without any issue.
the client cannot open/utilize the network based application.
the client cannot browse to the server.
the client cannot ping the server either.

i've looked over the configuration, and made certain that IAS was
installed as well. i've even removed, then re-constructed the VPN
setup
on the server.

still is a no go.

please help!


no one has any ideas? i'm seriously in a time crunch...









.

Relevant Pages

  • VPN clients cannot ping Netbios name but only ip address.
    ... >From the VPN client which was given the VPN ip address of 192.168.100.71. ... And this client is trying to communicate with a Windows 2k Server: ... But it cannot ping the netbios name Mercury... ... NETLOGON Disk Logon server share ...
    (microsoft.public.win2000.ras_routing)
  • VPN clients cannot ping Netbios name but only ip address.
    ... >From the VPN client which was given the VPN ip address of 192.168.100.71. ... And this client is trying to communicate with a Windows 2k Server: ... But it cannot ping the netbios name Mercury... ... NETLOGON Disk Logon server share ...
    (microsoft.public.win2000.networking)
  • VPN clients cannot ping Netbios name but only ip address.
    ... >From the VPN client which was given the VPN ip address of 192.168.100.71. ... And this client is trying to communicate with a Windows 2k Server: ... But it cannot ping the netbios name Mercury... ... NETLOGON Disk Logon server share ...
    (microsoft.public.win2000.security)
  • think I found the problem... ISA bug?
    ... routed directly to www01 from the vpn server. ... the ISA server doesn't know about this communication. ... default gateway) because it is trying to contact the vpn client which is on ... never asked and thus blocks/denies the connection. ...
    (microsoft.public.isa.enterprise)
  • think I found the problem... ISA bug?
    ... routed directly to www01 from the vpn server. ... the ISA server doesn't know about this communication. ... default gateway) because it is trying to contact the vpn client which is on ... never asked and thus blocks/denies the connection. ...
    (microsoft.public.windows.server.general)