Re: Unable to ping sbs 2003 from vpn client - site-to-site vpn

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

OH, and I should wait for the coffee to kick in.

In what way is ping failing? If pinging by name it may be failing to resolve the address, try ping by IP and see if it works.

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message news:%23UYDYwOzJHA.1196@xxxxxxxxxxxxxxxxxxxxxxx
assuming all else is OK I suggest trying packet fragmentation tests (related to MTU).

ping sbs -l 1400 -f

The number following the 'l' is the length of packet and the '-f' tells TCP/IP not to allow fragmentation of the packet. Slowly increase the length until the test fails, then compare to the MTU settings (1500 is default).

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org
"Madmxx" <Madmxx@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:5BF34774-1384-4BB5-9826-BC3225B6B2E0@xxxxxxxxxxxxxxxx
have a site to site VPN with two sonicwalls they seem to work great. my main
site A scheme is 192.168.1.0./24 with a sbs2003 that runs exchange and remote
web desktop. site B is 192.168.2.0/24 it only has workstations no servers. My
problem seems to be that the sbs 2003 server cannot ping the remote vpn
clients and the remote clients cannot ping the sbs 2003 server. The
workstations can communicate with each other from both sides and they are
able to ping the remote routers. I need the remote workstations to reach the
sbs 2003 server for the remote web desktop and outlook exchange to work for
these remote workstations.
--
Maxwell


.

Relevant Pages

  • RE: cannot connect computer
    ... if I type in the url of the server i get through ok. ... client computer to SBS domain. ... | I am unable to ping the sbs server by ip or name. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... That means that SBS has a static *private* IP on your LAN. ... Not being able to ping "the server" is probably not a sign of a problem...and is also technically inaccurate. ... I understand the desire to keep your server minimalist and only run exchange, but DNS and DHCP should be considered "essential" SBS components. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... It is held by SBS. ... There is no router in between the ISP's connection and the SBS server. ... So in essence, the WAN port will not ping, but it does get out on the internet, and OWA will work through it. ... That would be a very odd configuration considering what 'appears' to be the rest of your network layout. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... public IP is assigned to the external NIC of SBS. ... Is it installed with a standard install of SBS Server? ... I think I posted a question somewhere on the forums that I would have gladly ONLY installed Exchange if I could. ... So in essence, the WAN port will not ping, but it does get out on the internet, and OWA will work through it. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... The truth is that ping packets are a basic troubleshooting tool and a router *shouldn't* be monkeying with them. ... And changing a packet intended to to troubleshoot a connectivity issue defeauts the purpose of sending the packet in the first place...as the destination suddenly becomes ambiguous. ... The ISP configured the original device and the device actually PROPERLY recreates NAT ping packets and passes them to the servers, but the SBS server was not part of that initial configuration. ...
    (microsoft.public.windows.server.sbs)