Recent content by jonbush

maybe, if you use folder re-direction to a share on the server, (thus moving the big "my documents" issue) make sure all the users e-mail is held on the exchange server, rather than a .pst file, and maybe....hmmm, here's a thought...have a dhcp server on each site, then jig a logon script to...

i had a similar situation, here's how i resolved it.... got two pentium pc's with two nics in each, installed smoothwall firewall on each (using them as independent firewalls for each site) with static addresses for each internet connection....then configured the firewalls to talk to each other...

hi, just some info for you...i have an exchange 2003 server (enterprise ed.) running on an windows server 2003 (enterprise ed.) hardware fault tolerance is essential, raid 5 minimum really, i have a Pentium4 3.0 Ghz cpu with 2Gb of ram, and it works fine for our network 700+ users... I use...

hi, if you would normally map to a share called data on a server by mapping to \\server\data, then if it is a hidden share called data$ then map to \\server\data$ the name is as you share it, but the $ just prevents it from being seen.... hope this helps J...

factors to consider: - data redundancy, what will you do if theres a disk failure ? it's as easy to configure a hardware raid 5, then divide your partitions accordingly, and have a spare disk lying on your shelf just in case.... - data storage, if you mirror the c: drive, you have raid1 cover...

Hi, just my thoughts... if you are already used windows servers, then a move to exchange would probably be a wise move...you could probably re-organise your network and buy a new powerful server to deal with your e-mail, and after 6 months it's paid for itself by saving you 1200 bucks a month ...

I don't think you can downgrade exchange, enterprise installs a few extra functions and is designed for clustering and has large databases etc...check out the MS website, but i don't think it's a starter :-( J. ======================================= I know i've got it backed up somewhere...

thanks for letting us know the solution :-) ======================================= I know i've got it backed up somewhere! =======================================

as wolluf says, check hard disk and memory, something has changed to cause the fault, try a rebuild of NT server on a new hard disk... hope this helps J. ======================================= I know i've got it backed up somewhere! =======================================

of course, there is another plan.... use a third party spam filter, like gfi mail essentials or mailwall...i have used both in the past and found them to be quite good.... might appease the management, and be easy and a lot less hassle and time consuming... J...

as far as i understand it (some checking on the old technet may be in order) but you build an exchange server, then add it to an existing exchange organisation, then tick the box under "server properties" to set it as a front-end server....then configure it to do your collecting and sending...

I concur with tfg13, i tend to use trend antivirus on fileservers, exchange and workstations and find it to be just fine, cheap enough and very efficient. I have used f-secure in the past and found that to be pretty good.... it's just down to how good you want it to be :-) J...

no, you keep your existing system, just build a new pc with two nic's in, then install smoothwall on it, then use the lan ip address of the firewall as your default gateway, then reconfigure your DNS if needed, and away you go !!!! J. ======================================= I know i've got it...

with SBS if you use the wizard, then when you add a user, use the appropriate template and this should set up exchange for each user...it should be straightforward...if any user can connect to exchange, then they all should...if any can't, then it's probably an issue with the workstation...

what software are you using on the gateway ??? most decent software packages can control access.... the alternative is put your intranet on a seperate server and configure your DNS to point to the new server, so there is no need to use your bandwidth until you need to, or change your setup...