Fios router vs SBS2003 DHCP

I don't think I have the right config, but wanted to double check with the
experts.

I switched to Verizon Fios and decided to let the Verizon Fios router be the
router for my network. But now I can't configure my network printer. I was
able to install it on the server, but I can't print from the server or any
client. It is a Brother network-ready printer. It was printing fine before
Fios.

The way I had my network configured was with a Sonicwall firewall and my
SBS2003 server as the router (DHCP). Everything had been working fine for 3
years. Now, with Verizon Fios I let their router be the DHCP and my SBS2003
server with a static IP address and no DHCP. The reason I did it this way
was because each TV box needs and IP address from their router.

Am I doing something wrong? Can I let the Verizon router be the DHCP for
the TV boxes and at the same time have my SBS2003 server be the DHCP for the
PC network?

How can I get the network printer to wake up? When I send to print a Test
Page from the server it hangs for a while and then it gives me the error that
the document can't print. I can ping the printer via the command prompt fine.

Any help?

Thanks,
Eduardo Pietri

"Eduardo Pietri" <(E-Mail Removed)> wrote in message
news:CCE463E2-83A8-4A03-A9C8-(E-Mail Removed)...
> Am I doing something wrong? Can I let the Verizon router be the DHCP for
> the TV boxes and at the same time have my SBS2003 server be the DHCP for
> the
> PC network?

Never ever, ever, ever, ever, ever, ever, ever let a NAT firewall "router"
be the DHCP Server on a LAN with Active Directory. Always use the Windows'
Active Directory "aware" DHCP be the DHCP Server so it will properly
maintain the Dynamic DNS and WINS entries.

I have no idea what the "TV Boxes" are,...but they should not care where
they get the IP Config from.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Phillip,

Thanks for the response.

The TV boxes are the cable TV for boxes for cable TV service. The service
that I have is cable TV and Internet through Verizon Fios (fiber optic).
Verizon tells me that the TV boxes need their router to work properly. If I
go to the router configuration I can see all the TV boxes, PC's, access
points, etc. listed with an IP address.

Anyhow, can I isolate Verizon's Fios network from my network using their
router and a single NIC in my server? If the answer is yes, then, how? I
also have a switch because the router has only 4 ports, how should I connect
the swith and the server to the router?

Thanks again,
Eduardo


"Phillip Windell" wrote:

> "Eduardo Pietri" <(E-Mail Removed)> wrote in message
> news:CCE463E2-83A8-4A03-A9C8-(E-Mail Removed)...
> > Am I doing something wrong? Can I let the Verizon router be the DHCP for
> > the TV boxes and at the same time have my SBS2003 server be the DHCP for
> > the
> > PC network?
>
> Never ever, ever, ever, ever, ever, ever, ever let a NAT firewall "router"
> be the DHCP Server on a LAN with Active Directory. Always use the Windows'
> Active Directory "aware" DHCP be the DHCP Server so it will properly
> maintain the Dynamic DNS and WINS entries.
>
> I have no idea what the "TV Boxes" are,...but they should not care where
> they get the IP Config from.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"Eduardo Pietri" <(E-Mail Removed)> wrote in message
news:606DCECB-65E5-446C-A6B0-(E-Mail Removed)...
> The TV boxes are the cable TV for boxes for cable TV service. The service
> that I have is cable TV and Internet through Verizon Fios (fiber optic).
> Verizon tells me that the TV boxes need their router to work properly.

"Needing their router" does not mean "needing the DHCP on their router".
They should be able to use the SBS's DHCP as long as they know how to find
the Verizon box.....but....
But if it does work that way then you will have to isolate them in a
different subnet as you suggested.

> Anyhow, can I isolate Verizon's Fios network from my network using their
> router and a single NIC in my server?

The Server does not have anything to do with it. In your first post you
called the SBS a "router (DHCP)",...being a DHCP Server is not being a
"router". Your "router", and I use that term very loosly, is your
SonicWall. You need the Verizon "router" to be outside of the SonnicWall.
This means you may have to reconfigure the external side of the SonicWall
and the Internal Side of the Verizon box. The SonicWall is what isolates
the two networks. The two network cannot be running the same IP Range.

[LAN with SBS]
|
|
<SonicWall>
|
--------<TV Boxes>
|
<Verizon NAT box>
|
|
[Internet]

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

>
> "Phillip Windell" wrote:
>
>> "Eduardo Pietri" <(E-Mail Removed)> wrote in
>> message
>> news:CCE463E2-83A8-4A03-A9C8-(E-Mail Removed)...
>> > Am I doing something wrong? Can I let the Verizon router be the DHCP
>> > for
>> > the TV boxes and at the same time have my SBS2003 server be the DHCP
>> > for
>> > the
>> > PC network?
>>
>> Never ever, ever, ever, ever, ever, ever, ever let a NAT firewall
>> "router"
>> be the DHCP Server on a LAN with Active Directory. Always use the
>> Windows'
>> Active Directory "aware" DHCP be the DHCP Server so it will properly
>> maintain the Dynamic DNS and WINS entries.
>>
>> I have no idea what the "TV Boxes" are,...but they should not care where
>> they get the IP Config from.
>>
>> --
>> Phillip Windell
>> www.wandtv.com
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>>
>>

Great! Let me see if I understand correctly. The other part is how to get
it done.

[LAN with SBS] Static IP address 192.168.16.2, default gateway 192.168.16.1,
DHCP enabled with range of 192.168.16.3 - 192.168.16.x. DNS preferred
192.168.16.2.
|
-------Some PC's connected directly to the SonicWall router
-------<switch> Some PC's connected to the switch
|
<SonicWall> Static IP address 192.168.16.1. DHCP disabled. DNS ??
|
--------<TV Boxes>
|
<Verizon NAT box> Static address 192.168.1.1 (default), DHCP enabled, IP
address range 192.168.1.2 - 192.168.1.x, DNS as provided by Verizon.
|
|
[Internet]

Eduardo


"Phillip Windell" wrote:

> "Eduardo Pietri" <(E-Mail Removed)> wrote in message
> news:606DCECB-65E5-446C-A6B0-(E-Mail Removed)...
> > The TV boxes are the cable TV for boxes for cable TV service. The service
> > that I have is cable TV and Internet through Verizon Fios (fiber optic).
> > Verizon tells me that the TV boxes need their router to work properly.
>
> "Needing their router" does not mean "needing the DHCP on their router".
> They should be able to use the SBS's DHCP as long as they know how to find
> the Verizon box.....but....
> But if it does work that way then you will have to isolate them in a
> different subnet as you suggested.
>
> > Anyhow, can I isolate Verizon's Fios network from my network using their
> > router and a single NIC in my server?
>
> The Server does not have anything to do with it. In your first post you
> called the SBS a "router (DHCP)",...being a DHCP Server is not being a
> "router". Your "router", and I use that term very loosly, is your
> SonicWall. You need the Verizon "router" to be outside of the SonnicWall.
> This means you may have to reconfigure the external side of the SonicWall
> and the Internal Side of the Verizon box. The SonicWall is what isolates
> the two networks. The two network cannot be running the same IP Range.
>
> [LAN with SBS]
> |
> |
> <SonicWall>
> |
> --------<TV Boxes>
> |
> <Verizon NAT box>
> |
> |
> [Internet]
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
> >
> > "Phillip Windell" wrote:
> >
> >> "Eduardo Pietri" <(E-Mail Removed)> wrote in
> >> message
> >> news:CCE463E2-83A8-4A03-A9C8-(E-Mail Removed)...
> >> > Am I doing something wrong? Can I let the Verizon router be the DHCP
> >> > for
> >> > the TV boxes and at the same time have my SBS2003 server be the DHCP
> >> > for
> >> > the
> >> > PC network?
> >>
> >> Never ever, ever, ever, ever, ever, ever, ever let a NAT firewall
> >> "router"
> >> be the DHCP Server on a LAN with Active Directory. Always use the
> >> Windows'
> >> Active Directory "aware" DHCP be the DHCP Server so it will properly
> >> maintain the Dynamic DNS and WINS entries.
> >>
> >> I have no idea what the "TV Boxes" are,...but they should not care where
> >> they get the IP Config from.
> >>
> >> --
> >> Phillip Windell
> >> www.wandtv.com
> >>
> >> The views expressed, are my own and not those of my employer, or
> >> Microsoft,
> >> or anyone else associated with me, including my cats.
> >> -----------------------------------------------------
> >>
> >>
> >>
>
>
>

"Eduardo Pietri" <(E-Mail Removed)> wrote in message
news:0D3A559A-11C0-423B-93C8-(E-Mail Removed)...
> Great! Let me see if I understand correctly. The other part is how to
> get
> it done.
>
> [LAN with SBS] Static IP address 192.168.16.2, default gateway
> 192.168.16.1,
> DHCP enabled with range of 192.168.16.3 - 192.168.16.x. DNS preferred
> 192.168.16.2.
> |
> -------Some PC's connected directly to the SonicWall router
> -------<switch> Some PC's connected to the switch
> |
> <SonicWall> Static IP address 192.168.16.1. DHCP disabled. DNS ??
> |
> --------<TV Boxes>
> |
> <Verizon NAT box> Static address 192.168.1.1 (default), DHCP enabled, IP
> address range 192.168.1.2 - 192.168.1.x, DNS as provided by Verizon.
> |
> |
> [Internet]

Pretty close. Just a couple tweeks or verifications. The Verizon NAT box
needs a few more static IP#s that it doesn't give out via DHCP. The way you
show it you have it giving out all of them but the first one. Remeber that
Static does not mean Public or have anything to do with the Internet,..it
only means "static" as opposed to "dynamic" (DHCP).

---SBS---
Internal IP: 192.168.16.2
Gateway: 192.168.16.1
DHCP Enabled
DNS: This takes a paragraph to explain. All hosts on the LAN (not counting
the Verizon segment) will use the SBS for DNS. They must not use anything
else,..this is important. The SBS then uses the ISP's DNS (Verizon's?) in
the Forwarders List within the Configuration of the DNS Service in the MMC.
Optionally the Forwarders list can be left blank and it *should* default to
using Root Hints instead of a Forwarder which will also work and I have done
that in that past as well.

---SonicWall---
Internal IP: 192.168.16.1
External IP: 192.168.1.?? (I suppose 192.168.1.2)
Gateway: 192.168.1.1
DHCP Disabled
DNS: either none or use the SBS as the DNS
Access Controls must allow SBS make outbound DNS queries

---Verizon NAT box ---
Internal IP: 192.168.1.1
External IP: <provided by Verizon>
Gateway: <provided by Verizon>
DHCP Enabled
DNS: <provided by Verizon>

Keep in mind that you have now created a Back-to-Back DMZ between your LAN
and the Internet and you will have to deal with whatever issues that are
natural to Back-to-Back DMZs.
Your TV Boxes now will exist within the DMZ and will not be able to
communicate in any direct way with the rest of your LAN. This is true of
anything you place in the DMZ,...the LAN can communicate with them directly
but the things in the DMZ cannot communicate directly to the LAN without
special configurations on the SonicWall,...so it is a one-way thing.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Great! I'll try that. Makes sense. I was trying to figure that
configuration out by myself, but it was giving me a headache.

Now my new task is to learn about DMZ, but I doubt that it will be an issue.

The Verizon TV boxes have Static IP addresses in the Verizon router. I am
guessing that's how they 'activate' each box at the time of install. The
installer gives to Verizon the IP address of the router and the IP address of
each box, and bingo! that's how they let the signal in and charge me a
monthly fee for each box.

I appreciate the time and effort you've put into these replies. I'll post
back after I try it.

Cheers,
Eduardo

"Phillip Windell" wrote:

> "Eduardo Pietri" <(E-Mail Removed)> wrote in message
> news:0D3A559A-11C0-423B-93C8-(E-Mail Removed)...
> > Great! Let me see if I understand correctly. The other part is how to
> > get
> > it done.
> >
> > [LAN with SBS] Static IP address 192.168.16.2, default gateway
> > 192.168.16.1,
> > DHCP enabled with range of 192.168.16.3 - 192.168.16.x. DNS preferred
> > 192.168.16.2.
> > |
> > -------Some PC's connected directly to the SonicWall router
> > -------<switch> Some PC's connected to the switch
> > |
> > <SonicWall> Static IP address 192.168.16.1. DHCP disabled. DNS ??
> > |
> > --------<TV Boxes>
> > |
> > <Verizon NAT box> Static address 192.168.1.1 (default), DHCP enabled, IP
> > address range 192.168.1.2 - 192.168.1.x, DNS as provided by Verizon.
> > |
> > |
> > [Internet]
>
> Pretty close. Just a couple tweeks or verifications. The Verizon NAT box
> needs a few more static IP#s that it doesn't give out via DHCP. The way you
> show it you have it giving out all of them but the first one. Remeber that
> Static does not mean Public or have anything to do with the Internet,..it
> only means "static" as opposed to "dynamic" (DHCP).
>
> ---SBS---
> Internal IP: 192.168.16.2
> Gateway: 192.168.16.1
> DHCP Enabled
> DNS: This takes a paragraph to explain. All hosts on the LAN (not counting
> the Verizon segment) will use the SBS for DNS. They must not use anything
> else,..this is important. The SBS then uses the ISP's DNS (Verizon's?) in
> the Forwarders List within the Configuration of the DNS Service in the MMC.
> Optionally the Forwarders list can be left blank and it *should* default to
> using Root Hints instead of a Forwarder which will also work and I have done
> that in that past as well.
>
> ---SonicWall---
> Internal IP: 192.168.16.1
> External IP: 192.168.1.?? (I suppose 192.168.1.2)
> Gateway: 192.168.1.1
> DHCP Disabled
> DNS: either none or use the SBS as the DNS
> Access Controls must allow SBS make outbound DNS queries
>
> ---Verizon NAT box ---
> Internal IP: 192.168.1.1
> External IP: <provided by Verizon>
> Gateway: <provided by Verizon>
> DHCP Enabled
> DNS: <provided by Verizon>
>
> Keep in mind that you have now created a Back-to-Back DMZ between your LAN
> and the Internet and you will have to deal with whatever issues that are
> natural to Back-to-Back DMZs.
> Your TV Boxes now will exist within the DMZ and will not be able to
> communicate in any direct way with the rest of your LAN. This is true of
> anything you place in the DMZ,...the LAN can communicate with them directly
> but the things in the DMZ cannot communicate directly to the LAN without
> special configurations on the SonicWall,...so it is a one-way thing.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

Phillip,

We could not get it to work. I spent a lot of time with Verizon on the
phone and they couldn't figure it out either. I'll probably go to other
sources to see if they can help me. My intuition tells me that the sequence
of which devices I configure and when I hook them up may have something to do
with it.

A couple of questions though:

1. Does this configuration require the SBS LAN IP addresses to be defined in
the Verizon router? My guess is yes. The Verizon guy was not able to figure
out where to define them. My take is that they have to be defined before I
hook up the Sonicwall to the router. I don't know if defining them before
connecting the device makes any difference.

2. Should I connect the cable from the Verizon router to the Sonicwall into
the WAN port of the Sonicwall, or into one of the LAN ports?

3. What is the "external IP" for the Sonicwall? I am familiar with the
internal IP and the default gateway, but could not figure out what the
external IP is. My guess is that the SBS LAN will "see" the Sonicwall as
192.168.16.1, but the Verizon router will see it as 192.168.1.2. I'm not
sure that makes any sense.

4. Is the Access control to allow SBS to make outbound DNS queries a must,
or is that a default? Does that need to be setup as well in the Verizon
router?

Cheers,
Eduardo


"Phillip Windell" wrote:

> "Eduardo Pietri" <(E-Mail Removed)> wrote in message
> news:0D3A559A-11C0-423B-93C8-(E-Mail Removed)...
> > Great! Let me see if I understand correctly. The other part is how to
> > get
> > it done.
> >
> > [LAN with SBS] Static IP address 192.168.16.2, default gateway
> > 192.168.16.1,
> > DHCP enabled with range of 192.168.16.3 - 192.168.16.x. DNS preferred
> > 192.168.16.2.
> > |
> > -------Some PC's connected directly to the SonicWall router
> > -------<switch> Some PC's connected to the switch
> > |
> > <SonicWall> Static IP address 192.168.16.1. DHCP disabled. DNS ??
> > |
> > --------<TV Boxes>
> > |
> > <Verizon NAT box> Static address 192.168.1.1 (default), DHCP enabled, IP
> > address range 192.168.1.2 - 192.168.1.x, DNS as provided by Verizon.
> > |
> > |
> > [Internet]
>
> Pretty close. Just a couple tweeks or verifications. The Verizon NAT box
> needs a few more static IP#s that it doesn't give out via DHCP. The way you
> show it you have it giving out all of them but the first one. Remeber that
> Static does not mean Public or have anything to do with the Internet,..it
> only means "static" as opposed to "dynamic" (DHCP).
>
> ---SBS---
> Internal IP: 192.168.16.2
> Gateway: 192.168.16.1
> DHCP Enabled
> DNS: This takes a paragraph to explain. All hosts on the LAN (not counting
> the Verizon segment) will use the SBS for DNS. They must not use anything
> else,..this is important. The SBS then uses the ISP's DNS (Verizon's?) in
> the Forwarders List within the Configuration of the DNS Service in the MMC.
> Optionally the Forwarders list can be left blank and it *should* default to
> using Root Hints instead of a Forwarder which will also work and I have done
> that in that past as well.
>
> ---SonicWall---
> Internal IP: 192.168.16.1
> External IP: 192.168.1.?? (I suppose 192.168.1.2)
> Gateway: 192.168.1.1
> DHCP Disabled
> DNS: either none or use the SBS as the DNS
> Access Controls must allow SBS make outbound DNS queries
>
> ---Verizon NAT box ---
> Internal IP: 192.168.1.1
> External IP: <provided by Verizon>
> Gateway: <provided by Verizon>
> DHCP Enabled
> DNS: <provided by Verizon>
>
> Keep in mind that you have now created a Back-to-Back DMZ between your LAN
> and the Internet and you will have to deal with whatever issues that are
> natural to Back-to-Back DMZs.
> Your TV Boxes now will exist within the DMZ and will not be able to
> communicate in any direct way with the rest of your LAN. This is true of
> anything you place in the DMZ,...the LAN can communicate with them directly
> but the things in the DMZ cannot communicate directly to the LAN without
> special configurations on the SonicWall,...so it is a one-way thing.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"Eduardo Pietri" <(E-Mail Removed)> wrote in message
news:A3404F55-BE16-477A-ABAA-(E-Mail Removed)...
> 1. Does this configuration require the SBS LAN IP addresses to be defined
> in
> the Verizon router? My guess is yes. The Verizon guy was not able to
> figure
> out where to define them. My take is that they have to be defined before
> I
> hook up the Sonicwall to the router. I don't know if defining them before
> connecting the device makes any difference.

No. The Verizon NAT Box is completely oblivious to anything on the LAN side
of the Sonicwall. As far as the Verizon NAT box is concerned the only thing
that exists is the WAN interface of the Sonicwall and the TV Boxes. Nothing
else "exists" as far as it knows.

> 2. Should I connect the cable from the Verizon router to the Sonicwall
> into
> the WAN port of the Sonicwall, or into one of the LAN ports?

The WAN Port.

> 3. What is the "external IP" for the Sonicwall? I am familiar with the
> internal IP and the default gateway, but could not figure out what the
> external IP is. My guess is that the SBS LAN will "see" the Sonicwall as
> 192.168.16.1, but the Verizon router will see it as 192.168.1.2. I'm not
> sure that makes any sense.

You have three subnets (minimum).

1. Public = The "external" side of the Verizon NAT Box

2. Back-to-Back DMZ = Between the Sonicwall and the Verizon box. The things
that "live" on that one are the WAN interface of the Sonicwall, the
"internal" [LAN] port of the Verizon box, and the TV Boxes. It is probably
192.168.1.x

3. Internal Private LAN = the internal side of the Sonicwall. It is the
192.168.16.x All of the segments are totally independent of each other.
They are all oblivious to each other and none of them "effect" the
configuration of the others. None of them have to do anything special to
"know" about the other because they don't need to know about each other.

> 4. Is the Access control to allow SBS to make outbound DNS queries a must,
> or is that a default?

It is required.

Does that need to be setup as well in the Verizon router?

No. It is not related. The Verizon box should not be blocking anything
outbound to begin with,...typically you would have to go way out of your way
to make if block anything,...you'd have to do it on purpose.

My previous post has all the "specs" you need. There really is not anything
else. The Verizon people only need to concern themselves with the Verizon
box itself,...and the TV boxes. The Sonicwall should be treated [by them]
as if it is just another "simple" PC sitting on the network along with the
TV Boxes. Anything behind the Sonicwall should not concern them,...they
should not have you mess with any of it,...it does not exist as far as they
are concerned. However you do need to know the DNS Server IP that Verizon
provides for you becasue that is what you have to enter in the Forwarders
list on the SBS.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

GREAT!! I got it to work!

The one thing remaining now is to open up Port 3389 for remote desktop. I
had it set up in the Sonicall to a specific PC, but I just tested it in
'canyouseeme.org' and it can't see it. I need to play with the Verizon
router a little bit to see how to set it up.

Thanks a bunch again,
Eduardo


"Phillip Windell" wrote:

> "Eduardo Pietri" <(E-Mail Removed)> wrote in message
> news:A3404F55-BE16-477A-ABAA-(E-Mail Removed)...
> > 1. Does this configuration require the SBS LAN IP addresses to be defined
> > in
> > the Verizon router? My guess is yes. The Verizon guy was not able to
> > figure
> > out where to define them. My take is that they have to be defined before
> > I
> > hook up the Sonicwall to the router. I don't know if defining them before
> > connecting the device makes any difference.
>
> No. The Verizon NAT Box is completely oblivious to anything on the LAN side
> of the Sonicwall. As far as the Verizon NAT box is concerned the only thing
> that exists is the WAN interface of the Sonicwall and the TV Boxes. Nothing
> else "exists" as far as it knows.
>
> > 2. Should I connect the cable from the Verizon router to the Sonicwall
> > into
> > the WAN port of the Sonicwall, or into one of the LAN ports?
>
> The WAN Port.
>
> > 3. What is the "external IP" for the Sonicwall? I am familiar with the
> > internal IP and the default gateway, but could not figure out what the
> > external IP is. My guess is that the SBS LAN will "see" the Sonicwall as
> > 192.168.16.1, but the Verizon router will see it as 192.168.1.2. I'm not
> > sure that makes any sense.
>
> You have three subnets (minimum).
>
> 1. Public = The "external" side of the Verizon NAT Box
>
> 2. Back-to-Back DMZ = Between the Sonicwall and the Verizon box. The things
> that "live" on that one are the WAN interface of the Sonicwall, the
> "internal" [LAN] port of the Verizon box, and the TV Boxes. It is probably
> 192.168.1.x
>
> 3. Internal Private LAN = the internal side of the Sonicwall. It is the
> 192.168.16.x All of the segments are totally independent of each other.
> They are all oblivious to each other and none of them "effect" the
> configuration of the others. None of them have to do anything special to
> "know" about the other because they don't need to know about each other.
>
> > 4. Is the Access control to allow SBS to make outbound DNS queries a must,
> > or is that a default?
>
> It is required.
>
> Does that need to be setup as well in the Verizon router?
>
> No. It is not related. The Verizon box should not be blocking anything
> outbound to begin with,...typically you would have to go way out of your way
> to make if block anything,...you'd have to do it on purpose.
>
> My previous post has all the "specs" you need. There really is not anything
> else. The Verizon people only need to concern themselves with the Verizon
> box itself,...and the TV boxes. The Sonicwall should be treated [by them]
> as if it is just another "simple" PC sitting on the network along with the
> TV Boxes. Anything behind the Sonicwall should not concern them,...they
> should not have you mess with any of it,...it does not exist as far as they
> are concerned. However you do need to know the DNS Server IP that Verizon
> provides for you becasue that is what you have to enter in the Forwarders
> list on the SBS.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>