Recent content by chucksel

Rols is correct. CRC errors are usually caused by either: 1. Drive fault (usually damaged/dirty/worn heads) 2. Media fault (faulty tape(s) ) Tapes wear. Dont think you can re-use them over and over again. So do tape drive heads (wear). Skew happens! ;o) (skew being the tape is being drug...

Go to DEVICES tab, right-click on the tape slot and choose "Label Media". CAUTION!!!! - that will re-label the tape and set it to unused and therefore WILL ERASE THE CONTENTS. That should automatically throw it into the SCRATCH media partition. Make sure the job is set to the proper setting...

While I appreciate your reply, I have tried that to begin with and found out that the pool of IP's should not be the same as the inside per this Cisco link: http://www.cisco.com/warp/public/110/pptpcrypto3.html If I use the same subnet for the dhcp, I can not connect to resources even if I use...

Ahhhhhhhhh, yes. Something I'd probably do in my haste as well. Be well in 2005. Chuck

Hello all and Happy New Year. I have configured my PIX 501 running 6.3(4) to accept PPTP clients. I have set up a small range of DHCP addresses and successfully connected to the PIX with an XP Pro client using PPTP with a static NATed (no PAT) IP address. Although I connect successfully and...

Looks pretty good to me. What resolved your problem? Chuck

Your PIX should have the latest firmware and then it should last you a few more years unless you get huge. BuckWeet is right, use turboACL's. Chuck

Hi. What is it about the FVS318 that you do not like? We use a mix of these and the 501's at remote sites to connect to our Cisco 3000 VPN so I am just curious. You realize that the 501 is limited to 10 users, right? It seems with a T1 (not DSL) and a couple cisco switches that you might...

Hello all and Happy Holidays. I have configured my PIX 501 running 6.3(4) to accept PPTP clients. I have set up a small range of DHCP addresses and successfully connected to the PIX with an XP Pro client using PPTP with a static NATed (no PAT) IP address. Although I connect successfully and...

Well, listen up. These guys are screwing you over. The PIX 520 will take some serious sh@t thrown at it. We are a financial institition. Securites dealers (stocks and bonds, etc). We have NASDAQ servers and many other financial servers and T1's coming into a PIX 520. Some SERIOUS dataflow. 25+...

I looked. I am not familiar with Cosine Communications - SafeNet SoftRemote IPSec Dial client v9.2.1 Sorry!

I can appreciate that! My approach was a money saving one. Surely you can throw money at it. You must be banging that PIX 520 pretty hard. I have a 200 user network with 4 interfaces on my PIX and CPU utilization is not too bad. What kind of gaming?

There are hacks for the PIX 520 to use faster processors. Google it. Chucksel

The link rudeboy provided is a great example and I have used it successfully to set up the PPTP and IPSEC clients but be forewarned it does not show you the ENTIRE PIX config, just the major snippets. For one, it does not show you any ROUTE statements that you will need to reach all your...

I had the same problem even with using the "use default gateway on remote computer option" in the TCP/IP properties of the MSFT PPTP connection properties. After you connect via PPTP to your PIX, if you go to a CMD prompt and type "route print" I'll bet there is no route to the remote network...