VPN to different network for passing data only

Hello. this is going to sound dumb but I am totally stumped. I work in a
small Hospital. we have installed a new PACS system and I am trying to get a
VPN to work with our Major Hospital for the Radiologist there. I have a
SonicWall t170. I have setup the VPN through this and the connection show
green and the log says shared secret has passed. I have a static ip for my
gateway and they have a static ip for their gateway. then I have my internal
Pacs with a 192.168.1.X ip and they have their internal Pacs with an ip of
10.1.189.x the green light on the sonicwall and log file on sonicwall is the
only thing that works. do I need to add anything to my pacs server like
network connections or RRAS connection to make this work? the local and
remote IP's are set in the sonicwall and the gateways are set in sonicwall
but nothing is seen from either network? I have searched everything for
setting up a VPN but most all of it deals with using the server to server. I
have the firewall/VPN setup and working but nothing is able to communicate...
Heeeeeeeeeelp


the pain builds in back of brain as boss slaps your head for not knowing:-(

thanks Kevin

There are different types of VPN and they are not interchangable.
Mainly,...
There is Remote Access VPN (Host-to-Point) initiated by the Host.
Then there is Site-to-Site VPN (Point-to-Point) initiated by [usually] both
"Points" at the same time in both directions.

Site-to-Site behaves like a Private Leased Line between two points and the
routing between the two sites is even handled the same way.

Remote Access VPN behaves like the old "dialup" Internet connections where
you had a modem in the machine and dialed up a particular server via Phone
Number and had your own private connection between the dialing Host and the
Server that no one else but the dialing Host could use.

So if you are doing a Site-to-Site between a pair of SonicWall boxes then
you have to treat the SonicWall as if it was the "LAN Router" between the
two networks and handle the routing accordingly. You might have to add the
Remote IP Range (10.1.189.x) to the Local Address Table on the
Sonicwall,...you'll have to verify that with the SonicWall documentation.

If you are doing a Remote Access VPN then the PACS system itself must
initiate the connection to the Remote side. Keep in mind that with the
nature of "dialup" technology (which VPN is dialup technology) the PACS
System be be "cut off" from your local LAN while the VPN is active.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"WyoITGuy" <(E-Mail Removed)> wrote in message
news:7D3F6604-DF4E-48E5-B5A3-(E-Mail Removed)...
> Hello. this is going to sound dumb but I am totally stumped. I work in a
> small Hospital. we have installed a new PACS system and I am trying to get
> a
> VPN to work with our Major Hospital for the Radiologist there. I have a
> SonicWall t170. I have setup the VPN through this and the connection show
> green and the log says shared secret has passed. I have a static ip for my
> gateway and they have a static ip for their gateway. then I have my
> internal
> Pacs with a 192.168.1.X ip and they have their internal Pacs with an ip of
> 10.1.189.x the green light on the sonicwall and log file on sonicwall is
> the
> only thing that works. do I need to add anything to my pacs server like
> network connections or RRAS connection to make this work? the local and
> remote IP's are set in the sonicwall and the gateways are set in sonicwall
> but nothing is seen from either network? I have searched everything for
> setting up a VPN but most all of it deals with using the server to server.
> I
> have the firewall/VPN setup and working but nothing is able to
> communicate...
> Heeeeeeeeeelp
>
>
> the pain builds in back of brain as boss slaps your head for not
> knowing:-(
>
> thanks Kevin