[isalist] Re: ISA Server 2004/2006 & Verizon DSL Connection
- From: "Jim Harrison" <Jim@xxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Tue, 13 Mar 2007 06:28:19 -0700
http://support.microsoft.com/kb/841141
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Tee Darling
Sent: Tuesday, March 13, 2007 3:00 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: ISA Server 2004/2006 & Verizon DSL Connection
Tom,
Excellent question you have here but the answer is I do not really
want the NAT device to assign the ISA Firewall's external interface an
IP address. The NAT device won't even do it. So I ended up doing it
manually. With this configuration, everything works fine except when I
try to send an e-mail from my Outlook 2003 which is connected to
Exchange 2003 within my Internal LAN then the mail gets stuck in the
Queue.
The problem I realised I was having was that when I was using a cable
device from Adelphia, everything was working fine with this setup I have
mentioned here. The cable box was able to assign a public IP to the
External Interface of the ISA 2004 Server machine which is running
Windows Server 2003 without any problem. Everything has been working
fine and I would say "Thanks to you" for I read most of your articles to
help setup my environment. The moment I dropped the cable comapny and
replaced them with Verizon DSL box, my e-mails would always get stuck in
the Queue. I dropped the cable company Adelphia because their connection
keeps dropping almost everyday.
I can't figure out what to do from here. Thanks.
Tee
On 3/12/07, Thomas W Shinder <tshinder@xxxxxxxxxxx > wrote:
Why do you want the NAT device to assign the ISA Firewall's external
interface an IP address? Do that manually and turn off DHCP services on
the NAT device.
HTH,
Tom
Thomas W Shinder, M.D.
Site: www.isaserver.org <http://www.isaserver.org/>
Blog: http://blogs.isaserver.org/shinder
Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7>
MVP -- ISA Firewalls
________________________________
From: isalist-bounce@xxxxxxxxxxxxx
[mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Tee Darling
Sent: Monday, March 12, 2007 9:46 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: ISA Server 2004/2006 & Verizon DSL
Connection
Steve,
For some reason, I think the DSL modem does. Even when I
connect the DSL box to just a Windows 2003 Server with no ISA server
installed on it, it still doesn't assign the Windows Server the Public
IP it's supposed to assign. But immediately after I connect it to a
Windows XP machine, I get the Public IP assigned to it fast. Can you
maybe explain that?
I'll try what you suggested out here by enabling the DHCP System
policy when I finished installing ISA 2006 on the machine to see what
will happen. Thanks
Tee
On 3/12/07, Steve Moffat <steve@xxxxxxxxxx> wrote:
I wouldn't imagine that a DSL modem has enough intelligence to
tell what sort of operating system is connected to it.
Enable the DHCP system policy rule.
S
From: isalist-bounce@xxxxxxxxxxxxx [mailto:
isalist-bounce@xxxxxxxxxxxxx <mailto:isalist-bounce@xxxxxxxxxxxxx> ] On
Behalf Of Tee Darling
Sent: Monday, March 12, 2007 11:32 AM
To: ISA Mailing List
Subject: [isalist] ISA Server 2004/2006 & Verizon DSL Connection
ISA Gurus,
Where are you guys hiding? I need your help out here :).
Okay, here is my problem. I have a Windows Server 2003, XP, and
Vista network setup. I have a Verizon DSL that connects to my network.
When I connect the Verizon DSL box (Westell Wirespeed) to any of my
workstations, I get a public DHCP assigned IP address from Verizon.
That's Great. Everything works fine. But when I connect the Verizon DSL
to my Windows Server 2003, the Verizon box is not able to assign the
Public IP address to the server. According to Verizon, their DSL box
only works with Windows workstations and not Windows servers.
My plan is to setup my network so that my Windows Server 2003
which has 2 NICS in it will have ISA Server 2004 or 2006 install on it.
Actually, I will install ISA Server 2006 since I have worked with the
2004 edition for over a year and a half now. One of the NIC will be
connected to the Internal LAN and the other NIC will be connected to the
Verizon Box. But since I cannot connect the Verizon box directly to the
2nd NIC because of the limitation that box has with Windows version of
the server, what are some of the connections work around? I even tried
to connect the 2nd NIC and the Verizon box to an unmanaged switch but
that was no good.
Anyone out there with a very good idea to help me make this
connection work? I really need the ISA Server in my environment. Thanks
all for any idea you may have.
Tee
All mail to and from this domain is GFI-scanned.
Other related posts:
