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



Well, I wasn't specifically talking about ISA because I'm not using it yet as
it messed up my client connections to the Internet. So, I guess I was
specifically speaking about just the built-in Firewall in Server 2003 itself.
I know the title says SBS 2003 SP1. I'm actually using Server 2003 R2. Not
sure if that makes any difference. At the moment, the PPPoE connection using
just the Internet and Email connection wizard seems to be working properly.
I can do an "ipconfig /all" and a PPP connection comes up with my static IP
and the DNS servers and all that jazz. It's just that when I use the
Internet and Email connection wizard it "craps out" on me during the Network
Setup phase of the wizard's setup. Everything else passes by fine. Is there
any way to find out explicitly why the Network portion of setup does not
work? My DSL modem is basically a router and has a built-in firewall. I
bypass all that by setting it to bridged mode (the same way I did for my
Linksys Firewall/Router). It's a Westell 6xxx DSL modem. Ideally, I'd like
to be able to control the firewall and port openings and routing and such
through the Windows 2k3 SBS computer rather than the modem and/or the linksys
firewall/router.
--
Brian Millikan
Computer/Software Engineer
Microsoft Control Applications (Dialog-Based) Specialist / Hardware Driver
Development / User-Level Hardware Device Interfaces



"Steve" wrote:

By Windows Firewall do you mean ISA 2004? If so of course its not useless.
Cris is just telling you that PPPOE will do much better if handled by an
inexpensive router in front of the SBS 2003 external NIC (and therefore
ISA).

"BMillikan" <BMillikan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D24C3156-D5A5-4926-88AB-C019A215128C@xxxxxxxxxxxxxxxx
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: 45 days STUCK LIKE CHUCK. DNS / Mx record cant recieve emails
    ... you've pretty much ruled out Exchange configuration. ... Exchange not listening on the Internet NIC. ... You can test the connection from within the LAN, ... I'm thinking that leaves the NAT device blocking port 25. ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW not accessible over web
    ... My laptop is docked to the LAN but I take it to client sites. ... option will configure ISA to provide network security and packet filtering. ... the clients unable to access Internet after you enable firewall. ... Before you run the Configure E-mail and Internet Connection Wizard, ...
    (microsoft.public.windows.server.sbs)
  • Re: ICS and FS trouble
    ... The master domain browser is assigned with the ISC client machine. ... >>sharing for ms networks, QoS packet sheduler, internet protcol. ... > Internet connection has a 192.168.0.x address that can't be changed to ...
    (microsoft.public.windowsxp.network_web)
  • Re: Internet Sharing
    ... This computer connects directly to the Internet. ... On the ICS clients, you select: ... If running the wizard on the clients is a problem, just set each client to use ... connection from the client but when I open up the internet browser it is like ...
    (microsoft.public.windowsxp.network_web)
  • Re: openvpn server bridge.
    ... Client has an adsl internet connection. ... I see that, when I try to ping server to client or client to server, there are many arp requests without answer. ...
    (comp.os.linux.networking)

Loading