Re: SBS 2003 SP1 Premium Issues (including ISA 2004 installation i

Is there no plug-in or other software that can do a PPPoE login? If not, it
means that I will have to use the previous router/firewall I had. Does that
mean the Windows Firewall is useless? Can't XP create a PPPoE connection?
2003 has many of the same features as XP (without all the frills added in
like CD-burning from Roxio and such).


--
Brian Millikan
Computer/Software Engineer
Microsoft Control Applications (Dialog-Based) Specialist / Hardware Driver
Development / User-Level Hardware Device Interfaces



"Cris Hanna [SBS-MVP]" wrote:

I'm not sure why you would have had to change anything on the Modem
BUT
regardless of what wizard says it can do...it just doesn't do PPPoE, you'll have issues every time

You'll need an inexpensive router to handle the PPPoE between the external NIC and the DSL modem

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"BMillikan" <BMillikan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:EEDE3CFF-CB77-457A-B014-5F2CC48676CD@xxxxxxxxxxxxxxxx
I am running Windows SBS 2003 SP1 or 2... whichever is the latest. I try to
keep it up to date. I had to get a new DSL modem, but it finally arrived and
I was able to put it into a "bridged ethernet" mode where the modem's
router/firewall is disabled and should allow SBS 2003 to handle that. I set
up the PPPoE using the Internet/Email configuration wizard, but it's giving
me an error on Network setup every time. However, the SBS 2003 computer (as
well as my client computers) can access the internet without issue (it seems
anyway). However, I think the DNS may not be working properly. I can get to
the intranet "home" page by typing "http://[server name]" in Explorer, but it
gives me a DNS error when I try to go to "http://companyweb";. It didn't give
me an error with the previous setup. Any suggestions?

I have a Windows Vista x64 client computer running Office 2007 Enterprise
that was connecting to the exchange server (2003) just fine, but now it won't
connect. I tried deleting the profile and creating a new one, but it still
won't connect. When that connection went down, so did (apparently) my Mac OS
X Entourage 2004 exchange connection. However, my wife's Outlook 2007
connection to exchange 2003 (laptop running Windows XP Pro x86) works fine.
I haven't tried my account on that computer yet. So, exchange appears to be
running, but I cannot connect to it (not even via OWA!) because of the DNS
issues, I suppose.

I'm using Exchange 2003 as a mail "repository" so I don't have to worry
about which email was checked from where and such. Now, I can check it from
any client (that can connect to exchange - haven't found one for Linux yet
other than Novell's SuSe linux but I'm too cheap to buy it) without any
issues. The problem is with outbound mail. It takes my username and tacks
on my FQDN as the reply address. However, my ISP block port 25. So, even
though that mail should be routed back to my exchange server, it can't get
through. Is there anything I can do to workaround this issue? Is there a
way to force exchange to use the incoming email address (typically from my
ISPs mail server - I'm using the POP3 connectors to fetch the mail) to be the
"reply to" address in the outgoing mail? Of course, working with my domain
records (MX) and/or exchange to get the mail routed directly to my mail
server would be the best solution.

I installed the SQL 2000 SP4 server from my Premium disc and everything was
fine. I then installed ISA 2004 and none of my client computers could
connect to the internet! How can I prevent this? It's like it shut down the
routing service or something. I have no idea. I uninstalled it and all was
back to normal. Needless to say, I haven't installed it since. Any help
with this would be much appreciated as well.
--
Brian Millikan
Computer/Software Engineer
Microsoft Control Applications (Dialog-Based) Specialist / Hardware Driver
Development / User-Level Hardware Device Interfaces

.

Relevant Pages

  • RE: New computers to replace old ones
    ... users can log into all client computers on the domain. ... as long as the user's mail is stored in Exchange ... on and connect Outlook to the Exchange server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 SP1 Premium Issues (including ISA 2004 installation i
    ... Can't XP create a PPPoE connection? ... that was connecting to the exchange server just fine, ... X Entourage 2004 exchange connection. ... I then installed ISA 2004 and none of my client computers could ...
    (microsoft.public.windows.server.sbs)
  • Re: EDST - Which patch/tool fixes new calendar appointments on a go forward basis?
    ... The updated timezone information on client computers takes cares of ... and applying the Exchange CDO patch does it. ... CDO on Exchange and my BES server, updates the OS on my clients, and run ...
    (microsoft.public.exchange.admin)
  • Re: TOTALY bad SP1 installation :(
    ... The only MS Exchange services not running are: ... >> 2) All the client computers can't access the internet. ... >> can't contact the DNS server who of course is the SBS 2003 ... >> WINS server is the SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: Outside Exchange Account
    ... running setup did not remove the Exchange profile from my workstation. ... The Server installation was primarily an easy way to setup ... If "Configure Outlook Profile Information" is listed, ... then Assign Applications to Client Computers. ...
    (microsoft.public.windows.server.sbs)