It looks like the pings to the other subnet in the remote site (3002 Client side) are being routed to the Internet on the home office side. Now I've tried configuring static routes pointing to every interface on the 3000 concentrator as-well-as the interfaces on the remote site's 3002 just for...
Correction above:
Home office has Cisco 3000 VPN Concentrator
Remote Office has Cisco 3002 VPN Hardware Client
Also verified I can ping/trace from remote office VPN client to other subnets on home office site, but not from home office to other subnets on remote site.
I have a Cisco 3000 Wardware VPN client setup at a remote office connected to my 3000 VPN concentrator at the home office. The tunnel is up and I can ping from 3002 into my network here in the home office. I can also ping from the home office to the internal interface of and devices of the...
Sweet mother of mercy! I see, I was hoping to be able to check off the mailboxes I wanted with a GUI or something, but I guess I'll have to work at it instead. I've created the split policies as you suggested before in hopes that I can at least buy a little time on this bloody project.
Thanks...
Thanks for the post Ryan,
Yes I saw your other posts regarding splitting up the mailboxes per policy, but my question was actually how do you select individual mailboxes and NOT backup the rest. The method you described actually still backs up the entire set of mailboxes, but simply splits the...
I have Netbackup 5.1 running on RedHat and backing up the MS-Exchange 2003 server, as-well-as others. It does the full store and, currently, the entire brick level mailbox backup. The mailboxes are taking all night and running into the end of the scheduled window for other backups that fail...
The way I read this is you have given full passthrough rights to your internal DNS? I don't know if your company values it's data, but as a general rule you might want to keep attackers from having thier way with your internal zones. You might try setting up an EXTERNAL DNS server within a DMZ...
The superscope is the answer. I setup a test server to check my math and it seem to work out just fine. Saw the superscope as one, and assigned the reserved address w/different scope options to the thin client.
Now I just need to grow the "nads" to implement it into production network.
Thanks
I would take this one back to the beginning. See if you can get her to bring in the desktop to work on in your network. Do a non-citrix local print. That works with her equipment, then it's not her hardware. Check the Citrix servers and make sure there are no lingering auto created printers from...
Better way to discribe this is:
I would like to create a scope that has reservations in it. The devices that will pickup these reserved addresses need to point to different resources than the other devices in the current scope. Is there a way to force these reserved clients into a second scope...
Thanks zbnet,
That sounds like it'll get the job done, but what a freakin' hassle. Am I the only one on the planet who would ever need to do this? Isn't there some third party software out there that just one click does this for you?
There has to be some other management tool to manipulate the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.