Frame relay and VPN failover problem printing when fail over occurs

Suggestion:
Make the 2610 and 3640 the default gateway for each respective network
Disable EIGRP and enable OSPF, with the PIX at each end participating.
Each PIX sends default information to local router.
If the T1 line drops, the routes automatically switch over to the PIX to be routed through the VPN tunnel.

>all networked printers (HP'S) must point to themselves for the default gateway
Makes absolutely no sense, they should point to the router.

>Also the print server is located on the edge network
Do I need to go into the drawbacks of having the central print queue on a remote network for local printers? Makes no sense to me.

The 2610 is the default gateway for the local network and the 3640 is the gateway for the 2610.
Your next three lines are already being performed by EIRGP.
Your comment about the printer is one of the reasons I posted a question.
Your next comment about print servers makes no sense. Who ever said anything about local printers?
Why would you want to send print request over WAN links to spool and then back to print. Maybe you should review your theories.
Again my fail over WORKS just not the printing aspect.
So either you did not understand the question or you’re just talking to hear yourself speak.

My apologies if I misunderstood your situation. Check my credentials and my profile. I do not post "just to hear myself speak". My only intent is to help you. I certainly did misunderstand the "host" site and "edge" site and the relationship to the print server.

I have been very successful at this exact scenario using OSPF instead of EIGRP because the PIX's can participate in the routing updates and can back each other up, but the PIX does not use EIGRP. It's only a suggestion based on experience. Since your failover is obviously working, then no need to change it.

My understanding of your issue is that you have local networked printers, each pointing to themselves as the default gateway, and the print server is local (same subnet) to the printers. All works fine as long as the frame circuit is up. If the frame drops and the VPN takes over, you have to then change the default gateway on the printers to point to the local router. Just so that I am very clear about your situation...
Questions:
 What happens if the printers' gateway is pointing to the local router and the frame circuit is up? What works, what does not? Any chance it could be a subnet mask issue on the printers? Any other protocols enabled on the printer other than TCP/IP?
Do the printers need to communicate over the WAN/VPN? Are host site users printing to the edge site networked printers? Are the edge site users printing to host site networked printers?
Do all print jobs go through the local print server?

No apologies needed, I appreciate your help.
While the frame is up the printers do not print if pointed to the true default gateway.
All the TCP/IP setting are correct on the printers.
TCP/IP is the only protocol used
Only 4 to 5 due to we use Right Fax and the DS1 used for the Right Fax DID's reside @ the host location and then the faxes are spooled locally and printed to the edgr network. (which goes against what i said prior)
Other than that no.
No edge network users print back to the host location
Yes, all print print to the local print server.
The Edge server, is a DHCP, DNS/WINS, File and print server. We do this to decrease WAN network traffic back to our host location.
The whole printing thing is an  anomaly. I agree with you 100% that the printers should point to the local gateway.

>While the frame is up the printers do not print if pointed to the true default gateway.
Wow, this is an anomaly. It doesn't make sense. Print jobs are created locally, sent to the local print server to spool, print server sends print job to local printer Subnet masks put router, printer, print server and clients all on the same local subnet. No gateway needed, really, on the printers because nothing goes direct to/from the printer to the remote subnet. Logically, the gateway is the gateway is the gateway and as long as it is local, I can't see how it could break local printing.
Is the FAX printing the only thing that breaks when failed over to the VPN? User's can still print locally even without changing the gateway on the printers? How do the faxes get printed to the edge printers with the frame up if the edge printers don't have their gateway set? Do the faxes get sent to print server for spooling first?
What is the default gateway setting on the edge site print server? Is it perchance set to the PIX vs the router?

All printing is interupted.
All network devices point to the lcoal router as there gateway with the exception of the printers. So our primary connection (Frame) is the only situatuion were the "anomaly" comes into play becuase printing does not work correctly in that senario. Once the VPN solution comes into play all logical things work ex. all network device must point to the local router.
On the fax server the printing is set up as follows; WIN2K on the Host network printing directly via TCP/IP to the edge network printer.
Also "sometimes" we can put the gateway in and it will work. This is also across different HP models from 1200's up to 8000's.
The faxes get spooled on the host network FAX server and sent directly to the edge network printer.
All network devices, Server and desktops point to the router. Nothing points to the PIX.
The Router is taking the LAN traffic (non-routeable addresses) and point it to the frame, and points all web traffic to the PIX. (Sorry I did not mention this fact prior)
We do because this edge network generates a high volume of web traffic and at times was congesting the frame, so we do route web based traffic over our "failover" line.
Would it be helpful if I were to send you a Visio fo the topology?

Unfortunately, we don't have the ability to upload files to this forum. If you can post your visio on a web site somewhere and post the link here it would be helpful. You can always delete it later..