Re: Bare min. install with problems - Email, VPN
- From: "NonProfitAdmin" <NonProfitAdmin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 15 Jan 2006 09:36:02 -0800
Yes, you are helping and it is greatly appreciated.
One thing I am confused about (I've read a few other posts re: emails not
being sent properly) is this... If we have the local ISP as the domain that
is being used in the CEICW but they are using email addresses stemming from
their "theirowndomain.com" website/internet domain... do I need to change the
MX settings on their domain hosting or do I need to have the ISP do anything
special on our account or do I need to change any settings within Exchange
server to allow the emails that are getting stuck (there seems to be only
certain domain names that stick) get through...? Will SmartHost do that for
me?
More info further down...
"Lanwench [MVP - Exchange]" wrote:
>
>
> In news:CB9B5B18-47BF-4AD5-8866-E7A826F6CF01@xxxxxxxxxxxxx,
> NonProfitAdmin <NonProfitAdmin@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> > Thanks for your "insight" Lawrench... your wisdom is appreciated and
> > noted, harsh yes... but well excepted.
>
> Just tryin' to help, sir or ma'am. ;-)
>
> > I agree and will work on
> > getting them convinced toward updating the hardware.
> > Small consellation:
> >> it is backed up nightly to both a second drive and DVD
> >> the single drive is partitioned in to a 40 gig (SBS '03) and 80 gig
> >> (data)
> >
> > No idea what you refer to with the dial up thing... it is not for
> > connecting to the office but for connecting to the internet to get
> > their email when abroad (Europe, Japan, Korea, etc.) I mentioned it
> > because it was thought that sometime down the road they may want to
> > pull their email through the Exchange server.
>
> OK, I understood that. All they need is to connect to the Internet, and then
> they can use RPC over HTTP(s) to get Outlook 2003 to connect to Exchange. Or
> use OWA. And RWW.
Lanwrench, I am sorry could you explain this further. I get the idea but
don't know how you are thinking to do it...
> >
> > Yes they have a registered domain name and hosted website (mentioned
> > in my original post) but use their local ISP for internet access to
> > the office.
>
> No problem there.
>
> > I had proposed getting rid of all the emails other than their internet
> > domain name emails but they insist they need the attglobal.net
> > account for their internet access when in Europe and Asia.
>
> Then they don't understand the difference between using AT&T *dialup* and
> e-mail. The two are not related; you need to break this down and explain it
> to them. They can connect to the Internet using Joe's Cheap Dialup Service
> and then do whatever they, or you, have configured the computer to do -
> again, see RPC over HTTPs. And RWW. They do not need to use Joe's Cheap Mail
> Hosting Service as well.
Several of the executive's travel to cities in Russia, China, Korea, etc.
and want to keep things as simple as possible by using their own "connection"
to the web (Attglobal.net has a worldwide network whereas they would need to
search out local ISP's or internet connections to be able to connect to their
email, this way they get the email and the internet at the same source) but I
understand they could simply use a "theirowndomain.com" email instead of the
attglobal.net one. It is much easier for them to have a traveling ISP to
access.
> > I believe that smarthost was NOT selected during the CEICW. I assume
> > by your reply that this would be better to use. Can this be switched
> > at this point?
>
> Yes, you can re-run the wizard at any time.
> >
> > I will look in to the www.dyndns.org solution as they have a dynamic
> > IP, thanks.
>
> It's a good service. There are others, too - www.no-ip.com and www.tzo.com -
> but I have always used Dyndns.
> >
> > The local users that cannot connect are listed as RWW users (and
> > Mobile users too).
>
> What errors do you get?
They are getting this error when trying to use Remote Desktop Connection
(with their own username/password and connecting via IP address) from thier
home or remote computer-
"The local policy of this system does not permit you to logon interactively."
And shuts them (and me) out although I can use this exact connection with
the Admin username/password and same IP and connect to the server no problem.
I've tried this on 2 of the client computers within the network with same
results... both users are Mobile users and RWW users.
Thank you again.
NonProfitAdmin
>
> >
> > Thanks for the security information re: the wireless
> > Your $0.02 are appreciated.
>
> HTH.
> >
> > NonProfitAdmin
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >>
> >>
> >> In news:B41B5C25-6C37-49BC-857C-43EE7F84085C@xxxxxxxxxxxxx,
> >> NonProfitAdmin <NonProfitAdmin@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> >>> We have just installed SBS 2003 Standard on a PIII-500mhz/1Gig SD
> >>> Ram/120 Gig HD/Single NIC and it seems to be running fine (there is
> >>> only 5 clients on it so load is no problem)
> >>
> >> Well, a single hard drive *is* a problem. What if it fails?
> >>
> >>> for a Non-Profit Org.
> >>> They have an internet website/domain plus access the internet
> >>> through their local ISP account. They also use attglobal.net as a
> >>> travelling ISP access provider so have 3 email accounts that need
> >>> to be accessed through the server
> >>
> >> Having a dialup for their travel doesn't mean anything has to be
> >> used via that ISP's email, though.
> >>
> >>> on top of the 6 email accounts based on their
> >>> website domain AND one email account through their local ISP
> >>> account.
> >>
> >> Do they have a registerd Internet domain name? If not, they really
> >> ought to get one. I'd suggest they wean senders off their ISP POP
> >> account addresses and stop using them...
> >>
> >> I'd also ditch the POP connector and host the mail directly on the
> >> server.
> >>
> >>
> >>> Problems though are:
> >>
> >>
> >>> 1> We are using Exchange (set it up with the local ISP as the domain
> >>> name and adding their website domain email accounts and ISP email
> >>> account for some of the users) and POP3 Connector to grab the
> >>> emails. Problem is that SOME emails never get off the server and
> >>> are stuck in the Queue (when I check Servers/OurLocalServer/Queues
> >>> I see several emails to other domains that are stuck in the SBS
> >>> Server SMTP connector and have been retrying till they fail) Is
> >>> there a solution to this?
> >>
> >> Is mail being delivered to a smarthost (in the connector) or is mail
> >> being sent out directly (resolving via DNS)? You had this choice
> >> when you ran the CEICW. If you're using a smarthost, does the
> >> ISP/hosting company require that you authenticate? You ought to see
> >> some info on the queues (and select the SMTP connector to see what
> >> the status is)....
> >>
> >>
> >>> 2> I can connect to the Server via Remote Desktop Connection
> >>> (using the IP address assigned from our local ISP account
> >>
> >> If you have a static public IP and a registered Internet domain
> >> name, have whomever hosts the domain's public DNS set up an A record
> >> (like mail.mycompany.com or whatever.mycompany.com) that points at
> >> the public IP so you don't have to remember IP addresses. If you
> >> have a dynamic public IP, see www.dyndns.org for one option I like a
> >> lot.
> >>
> >>> and my
> >>> Admin username/password) but no one else can access their client
> >>> computers remotely via RDC using the same... their username/password
> >>> and the IP address). How can I make it so they can remotely access
> >>> their clients from home/travel?
> >>
> >> Are they in the Remote Web Workplace Users group in AD?
> >>
> >>> We are using a Benq switch, Linksys WRT54GX2 wireless router to
> >>> allow internet access to office guest users.
> >>
> >> If you don't have a good hardware firewall appliance (not just a
> >> simple NAT box) and aren't using ISA, you are asking for trouble.
> >> Even if you were to use two NICs and the Windows server's built-in
> >> firewall (which is a wet paper bag from a security standpoint).
> >>
> >> Also, if you must offer wireless access to non-domain users, you
> >> need a separate access point that is not on your LAN at all. Do not
> >> let strange computers connect to your network in any way. It's
> >> dangerous.
> >>
> >>
> >>>
> >>> Thanks for any help...
> >>>
> >>> BTW, if I choose to attempt to RE-install SBS 2003 Standard on to
> >>> another computer than can handle 2 NIC cards would I just be able to
> >>> back this configuration up and restore to the new computer?
> >>
> >> See
> >> http://www.microsoft.com/smallbusiness/support/articles/backup_restore_sbs2003.mspx
> >>
> >> Apologies if any of the above sounds harsh - it isn't meant to be. I
> >> support a couple of nonprofits, too....and I wouldn't set up a
> >> server without good hardware. They're worse off than if they never
> >> had one, should it fail....if they don't have the budget for decent
> >> server/network kit, I would rather they wait until they do. Just my
> >> $.02.
>
>
>
.
- References:
- Re: Bare min. install with problems - Email, VPN
- From: Lanwench [MVP - Exchange]
- Re: Bare min. install with problems - Email, VPN
- From: NonProfitAdmin
- Re: Bare min. install with problems - Email, VPN
- From: Lanwench [MVP - Exchange]
- Re: Bare min. install with problems - Email, VPN
- Prev by Date: Re: IP Config with 2 NICs Wizard dont work, Static dont work!
- Next by Date: Re: Creating Public Calendar
- Previous by thread: Re: Bare min. install with problems - Email, VPN
- Next by thread: Re: DNS Entry
- Index(es):
Relevant Pages
|
