[isalist] Re: (no subject)
- From: "Thor \(Hammer of God\)" <thor@xxxxxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Mon, 12 Mar 2007 22:21:57 -0700
What about a plain old fashioned Win2k3 server? (i.e. - get SBS/ISA out of the
way...)
Captures? Logs?
t
----- Original Message -----
From: Glenn Johnston
To: isalist@xxxxxxxxxxxxx
Sent: Monday, March 12, 2007 10:03 PM
Subject: [isalist] (no subject)
I also would like to know how they do it.
I have a cable internet service specifically designated as a 'HOME USE'
broadband service, at home, I use the 'HOME USE' service cause it's nice and
cheap.
Sure, Port 25 is blocked inbound, and only allowed to the ISP' SMTP server
outbound, 1723 inbound is blocked inbound, as is 80, 21, 110, and probably a
few other that I haven't found yet, but for home, it works just fine.
I can plug this cable BB service into a LinkSys, D-Link, and Netgear BB
routers and they will get an address, the router do their NAT'ing perfectly,
and multiple devices can access the internet through the single public IP just
fine.
I can also plug the Cable modem directly into a WinXP Desktop or Notebook and
it will work Just fine.
But when I try to plug it into my play server, a Compaq Proliant DL380,
running SBS2003R2 Premium that I have at home, It just don't get issued with
an IP address, from the cable modem. Plug it through the LinkSys router, and it
can access the internet just fine, but plug the Server directly to the Cable
Modem = No Public IP address issues by the ISP's DHCP server.
This is repeatable, I can move the plug back and forth from the notebook to
the server, and the notebook wil repeatedly get the same public IP, but the
server times out, and ends up with a 169... private address.
For me. it's not really an issue, the server does not publish services, and
it only a play server anyway, but the ISP's obviously do something very tricky
& sneaky !
GJ
------------------------------------------------------------------------------
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On
Behalf Of Thor (Hammer of God)
Sent: Tuesday, 13 March 2007 15:32
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: ISA Server 2004/2006 & Verizon DSL Connection
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)
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:
