The Guru De Grando Jimbo's answer looked like a winner to me. <<
http://support.microsoft.com/kb/326116 >>
As far as not being able to send mail with a static ip behind NAT, port 25
outbound on both the router and ISA is all that should be required.
JB
On Mar 12, 2007, at 9:25 AM, Tee Darling wrote:
John,
The scenario you described here is good. I had my network setup like that
before with ISA 2004. The problem I was having was that, the moment I had
the external interface configured to have a static private IP address on the
private side of the Verizon box NAT, I couldn't send e-mail out. I was able
to receive e-mail but not send. Was there any configuration I was supposed
to perform? Thanks.
T
On 3/12/07, John Becker <becker1@xxxxxxxxxxxxxxxxx> wrote:
>
> Technically not a guru ;-)
> It does not make sense to me that DHCP would be any different for a
> server version of windows.
>
> Is the Verizon router not able to perform NAT?
>
> The scenario which works for me: DSL router performing NAT - ISA
> external NIC manually set to an ip address on the private side of the NAT.
>
> KB
> On Mar 12, 2007, at 8:24 AM, Tee Darling wrote:
>
> It's residential. I don't know about MAC or NAT router (Linksys) since I
> did not ask them that question. My only concern is how do I make it work
> with ISA Server 2006 on a Windows 2003 server?
>
> On 3/12/07, John T (lists) <johnlist@xxxxxxxxxxxxxxxxxxx > wrote:
> >
> > Is the Verizon DSL service residential or business?
> >
> >
> > They said it only works with Windows Workstations, so does that mean
> > that it will not work with a MAC or with a firewall such as Sonicwall or
> > even a basic NAT router such as a Linksys?
> >
> >
> > * John T*
> >
> >
> > -----Original Message-----
> > *From:* isalist-bounce@xxxxxxxxxxxxx [mailto:
> > isalist-bounce@xxxxxxxxxxxxx] * On Behalf Of *Tee Darling
> > *Sent:* Monday, March 12, 2007 7:32 AM
> > *To:* isalist@xxxxxxxxxxxxx
> > *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
> >
>
>
>
