[isalist] Re: ISA Server 2004/2006 & Verizon DSL Connection

And here is how I got this thing resolved:

I read everything you guys stated here in this forum. What made me decide to
try this whole setup again was what Thor (Hammer of God) said some hours
ago. Here is what he said and I qoute:

"Since when does the DCHPDiscover message contain OS infoz?  I'm not aware
of any mechanism that allows a DHCP server to identify the client OS before
assigning an address..  There are several methods to secure DHCP assignment,
but how exactly could Verizon identify the OS type ?"

The moment I read this then I decided to connect the Verizon box back to my
Windows Server 2003 machine again to see if I'll get the Public IP. I was
also aware that even when I first connected the Verizon box to my
workstation, it did take a while for the public IP to show up on the
workstation.  I haven't yet installed the ISA Server 2006 yet because I
wanted to see the Public IP first on the box before I put ISA on it. I used
the repair tool when you right-click on the NIC to keep repairing the NIC
more than 6 times while the connection kept failing on me. I also disabled
the NIC and enabled it more than 5 times. Every time I do that, the NIC will
try to get the Public IP from the Verizon wiredspeed box. I told myself that
I'll let the NIC keep trying to  get  the  IP from the  verizon  box  for
the next 2 hours. I left the PCs and I went upstairs to watch a TV. I came
back after almost 2 and a half hours later and (Boom Bamm!!!) the Public IP
was finally on the Windows Server 2003 looking at my smiling face.

I had wanted to call the Verizon guys and tell them they are liars but I
decided against it. I kind of figured that those tech support guys had been
only trained to tell their customers that Verizon DSL only works with
Windows workstations and not servers.

Next time anyone encounters this kind of headache with Windows Server and
any DSL box, just be patient and wait and see how long it will take the DSL
box to assign the Public IP.

Right now my ISA Server 2006 is up and running with all the PCs in my home
office. I used Tom's ISA Server 2004 instructions to configure this ISA
2006. I don't think Tom needs to come out with another book for ISA 2006.
Get the ISA 2004 book and read Tom's articles on ISA 2006, and I think you
guys will be fine.

Thanks to everyone who participated in  this discussion. Peace  out!!!

Tee Darling

On 3/13/07, Thor (Hammer of God) <thor@xxxxxxxxxxxxxxx> wrote:

 Since when does the DCHPDiscover message contain OS infoz?  I'm not aware
of any mechanism that allows a DHCP server to identify the client OS before
assigning an address..  There are several methods to secure DHCP assignment,
but how exactly could Verizon identify the OS type?

t


----- Original Message -----
*From:* John T (lists) <johnlist@xxxxxxxxxxxxxxxxxxx>
*To:* isalist@xxxxxxxxxxxxx
*Sent:* Monday, March 12, 2007 4:45 PM
*Subject:* [isalist] Re: ISA Server 2004/2006 & Verizon DSL Connection

 Your Verizon DSL service, being residential, may be configured to only
assign IPs to non-server OS. You might try reading your TOS with them and it
may mention this.



*John T*



-----Original Message-----
*From:* isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
*On Behalf Of *Tee Darling
*Sent:* Monday, March 12, 2007 8:24 AM
*To:* isalist@xxxxxxxxxxxxx
*Subject:* [isalist] Re: ISA Server 2004/2006 & Verizon DSL Connection



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




Other related posts: