Re: LAN ip subnet is moving off from a bigger enterprise

Hi Jim,

Sorry I have not been checking this post because I have been really busy
moving the SBS network off of the integrated VLANs.

Thank you so much for your help though.

Despite what I said to the enterprise guy, he is not convince about letting
me to keep the existing IP scheme even though the SBS nework are completely
seperate from the enterprise

Here's the topology:

SBS network:
ISP Router --DMZ switch--SonicWall - Cisco Switch - LAN

Enterprise network:
ISP Router --DMZ switch - PIX - Cisco Switch - VLANs

Helen

Be"Jim Behning SBS MVP"
<jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ee0er357rirvpio7r0ihuhpupf4sknlv74@xxxxxxxxxx
You are starting to confuse me but that is ok.

I have one account with 4 locations. They receive Internet, anti-virus
and SQL services from the host company. The host company runs Cisco
switches. They said here is your port. Connect your switch to this
port. Your workstations will use this ip scheme. Times 4 as my account
has 5 offices in 4 buildings 100 miles apart. The host company gave me
access to only one port on their Cisco switch for each of the 4
buildings. It was a simple discussion of this is how it is, here is
your gateway, here is your ip scheme and subnet. The reason that the
host company said here is your ip scheme for each office is they had
to build their routing tables so stuff gets back to our networks.

So in this example they said my Fay office would be at 10.24.1.x with
the gateway at .1. At the CBO the network is 10.23.1.x and the gateway
is 10.23.1.60. At Mountainside the network is 10.21.2.x and the
gateway is 10.21.2.1. They did not care so much what I was doing at
each office.

Cisco Catalyst Vlan port 22 (Host company network device)
|
|
HP Procurve Switch (your network switch)
| | | |
| | | |
WS1 WS3 SBS HP4000

Could work. Host company says your gateway is at 10.64.2.1 and you can
use a subnet of 255.255.255.0

Or maybe you want to do

Cisco Catalyst Vlan port 22
|
|
wan port
Sonicwall TZ190
lan port
|
|
HP Procurve Switch (your newtwork switch)
| | | |
| | | |
WS1 WS4 SBS HP4000 printer

In this case maybe your host says your gateway is 10.64.2.1, your
firewall wan is at 10.64.2.1. Your firewall lan is at 192.168.16.1.
You port forward 25, 80, 443, 4125 and 3389 to your SBS.


I am lost when you say firewall and DMZ. I know what those words mean
but who supplied the firewall and what brand is it? Where is this DMZ?
When I see DMZ that usually means that inside of a firewall or router
I designate an ip that will accept all traffic. This differs from a
router or firewall where I say that a specific ip (my SBS) will accept
port 25, 80, 443, 3389, and 4125.

At my shared space account. The host company want to know what ip
networks I am using. Actually they had told me years ago what ip
networks I will use. That info was lost and they were making up a new
list they could keep track of. Once again this is for routing
purposes. In their routers they need to know where to send packets. My
host company was having problems because other tenants where picking
out networks without telling the host company. Packets were getting
lost. To keep track of stuff they just assigned all their tenants a
network and made entries in their routers.

http://en.wikipedia.org/wiki/Routing_table
http://www.windowsnetworking.com/articles_tutorials/Making-Sense-Windows-Routing-Tables.html
http://www.faqs.org/docs/linux_network/x-087-2-issues.routing.html


On Sat, 16 Feb 2008 00:04:17 -0500, "Helen Mooc" <hmooc@xxxxxxxxxx>
wrote:

Yes we are sharing the cost of the Internet connection. Our firewall is
plugged to their main switch and there is a rule on the switch to seperate
the SBS network on one VLAN. There is a crossover cable use to plug
between
the enterprise switch (note not the main one that I mention earlier) to
the
SBS network switch to allow share resource. Now if I just remove/unplug
that crossover cable (between that 2 switches), instead of the firewall
plugging to into their main switch, I would take it and plug it to the DMZ
switch. Would not that be sufficient to seperate us and avoid any cross
over issue that has been metioned? I think he mention something like "how
can you guarantee that someone (meaning me cause I am the only person
who's
in the server the most often) not plugging into the switch" I am not
really
following him but if he said so.

"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:bh8cr3tnmeusjjqua359nt0odognfrpojq@xxxxxxxxxx
If you get your own isp internet connection whatever they do with the
rest of their networks would not impact you. If they are still
supplying your internet then his statement may be true.

On Fri, 15 Feb 2008 17:49:37 -0500, "Helen Mooc" <hmooc@xxxxxxxxxx>
wrote:

Well it looks like I will have to change the ip scheme to something else
as
the Enterprise network person mention there might be a cross over in
certain
situation. I really don't understand HOW that can happen if the SBS
network
is completely off from the integrated VLAN. Would you know why is it?
Also
do you think 192.168.200.x can have cross over with other Linksys
router.
I just don't know how that's going to happen and if he's just making it
hard
for me.

Thanks.
Helen

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:O9RM74AcIHA.536@xxxxxxxxxxxxxxxxxxxxxxx
No, if nothing has changed you don't need to run the CEICW. Just
moving
to
a new switch is transparent to the network.

--
Claus
"Helen Mooc" <hmooc@xxxxxxxxxx> wrote in message
news:udMecU$bIHA.5892@xxxxxxxxxxxxxxxxxxxxxxx
Hey Claus, that is true!

I don't need to make any change at all except for the switch and the
firewall.

How did I not thing of that, lol.

Would I still have to run the CEIW wizard again?

Helen

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:O9q$IM%23bIHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
If you move to your own switches you could just leave the current
10.104.x.x. in place.

If you want to change, follow the instructions in my first answer.
To
avoid problems with potential VPN connections down the road I would
recommend using 192.168.16.x for you subnet. The key to a successful
switch is that you use the wizards. First the change server IP
wizard
and then the CEICW. Then have your clients renew their DHCP lease
and
change the static IPs.

--
Claus
"Helen Mooc" <hmooc@xxxxxxxxxx> wrote in message
news:OvkK269bIHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
Hi guys,

Sorry I am not explain this right. Right now the SBS network is
place
in / integrated with one of the 6 VLAN they have. They want us to
move
off of one of the VLAN and start a new IP schema for the network.
Does
that make sense. Right now, the SBS network 10.104.x.x. We can
even
start our own ip schema like 192.168.2.1 - 192.168.2.254.

I heard that AD does not like it too much when you change the IP,
is
that too? Why?

Ya there is about 8 or 9 static IP servers/printers on the network
that
I will have to change.

Thank you,

Helen

"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:534br3l3hiul9b2ic621ndcr18a8kmhhka@xxxxxxxxxx
I'm with Claus. At the server you could go to the command prompt.
Ipconfig/all >c:\ipconfig.txt and post those results. It is
possible
there is nothing to change.

On Thu, 14 Feb 2008 23:26:08 -0500, "Claus" <cjobes@xxxxxxxxxxxxx>
wrote:

Am I missing something? If you move the network onto its own
isolated
subnet, why do you need to change the IPs?

Anyhow, if you want to change it (assuming that the SBS box is
doing
the
DHCP), all you need to do is run the "Change Sever IP" wizard,
change
to
what you want and then run the CEICW. Any hardware with a static
IP
(printers etc.) need to be changed manually. Same goes for the BDC
if
it has
a static IP. Make sure you also change the DNS on those static
ones
to
point
to the new IP of the SBS box.

--
Claus
"Helen Mooc" <hmooc@xxxxxxxxxx> wrote in message
news:%23DusEQ4bIHA.5892@xxxxxxxxxxxxxxxxxxxxxxx
Hello

Unfortunately the SBS company did not work out with the
Enterprise
one and
as a result they will be moving off from the intergrate subnet
VLAN
network. The SBS firm will start all over with the internal LAN
ip
schema
basically but the public address will stay the same for the
firewall.

I was wondering what I would have to watch out for in terms of
moving off
SBS into a new subnet plus all its file/blackberry/backup
servers
and all
the printers too. I take it I will have to run the CEIW again
when
I get
the new ip for SBS but what else. I just don't want any
surprise
as
I am
already have a whole load of other projects I have on hands as
well.

BTW there is also a BDC to the SBS domain.

Thank you very much.

Helen












.

Relevant Pages

  • Re: LAN ip subnet is moving off from a bigger enterprise
    ... The host company runs Cisco ... Connect your switch to this ... At the CBO the network is 10.23.1.x and the gateway ... WS1 WS3 SBS HP4000 ...
    (microsoft.public.windows.server.sbs)
  • Re: Need guidance on Cisco 6513 install
    ... having this switch set up on Tuesday by noon, ... The switch itself (and other future network hardware) will be on the ... but you can always choose another vlan number and same ... In a two core environment, ...
    (comp.dcom.sys.cisco)
  • Strange results from a tcpdump, can anyone help?
    ... traffic was going ballistic on most ports in the network. ... other hosts went to normal (i.e. the only traffic you could see were ... packets from the same vlan destined to other hosts outside ... If it was simply a bad switch with a bad port that had lost it's mac ...
    (comp.dcom.lans.ethernet)
  • Re: Strange results from a tcpdump, can anyone help?
    ... traffic was going ballistic on most ports in the network. ... other hosts went to normal (i.e. the only traffic you could see were ... packets from the same vlan destined to other hosts outside ... If it was simply a bad switch with a bad port that had lost it's mac ...
    (comp.dcom.lans.ethernet)
  • Re: Help with IGMP
    ... By default it should forward multicast traffic to all port. ... good, it clog the network. ... It switch is has no VLAN or single VLAN and all ... the layer 2 protocol to allow switch interfaces to join multcast streams. ...
    (comp.dcom.sys.cisco)
Loading