| Author |
Message |
Sal Tinajero
Guest
|
Posted:
Mon Dec 06, 2004 10:35 pm Post subject:
IP routing |
|
|
We've just implemented a VLAN network in our company. Everything went
smooth except our Exchange Clauster, only the systems in the VLAN that
Exchange belongs to can see it. For some reason Win2k3 with Exchange 2k3
does not allow the routing to be inheritered from the firewall. All the
other servers running Win2k and Win2k3 Standard in the Exchange VLAN are
visible from the other VLANs. There is something between the combo Win2k3
and Exch 2k3 that does not allow it to route properly. Does anyone have any
leads to this problem? Has anyone experience that same issue?
Thanks in advance.
|
|
| Back to top |
|
 |
Ed Woodrick
Guest
|
Posted:
Tue Dec 07, 2004 1:55 am Post subject:
Re: IP routing |
|
|
Exchange completely relies on the network layer to do it's routing.
My guess is that you probably don't have WINS and DNS properly setup and
things can't find each other.
Can all devices ping each other?
Are all default routers/gateways set on all systems correctly?
"Sal Tinajero" <stinajero@berkleyindustries.com> wrote in message
news:OlvrNH72EHA.2624@TK2MSFTNGP11.phx.gbl...
| Quote: | We've just implemented a VLAN network in our company. Everything went
smooth except our Exchange Clauster, only the systems in the VLAN that
Exchange belongs to can see it. For some reason Win2k3 with Exchange 2k3
does not allow the routing to be inheritered from the firewall. All the
other servers running Win2k and Win2k3 Standard in the Exchange VLAN are
visible from the other VLANs. There is something between the combo Win2k3
and Exch 2k3 that does not allow it to route properly. Does anyone have
any leads to this problem? Has anyone experience that same issue?
Thanks in advance.
|
|
|
| Back to top |
|
 |
Sal Tinajero
Guest
|
Posted:
Tue Dec 07, 2004 2:59 am Post subject:
Re: IP routing |
|
|
DNS works like charm! Its only the two nodes that have the problem and
cannot ping to the other VLANs. We can ping the NAS device but not the 2
nodes and the virtual IP. In the same VLAN that Exchange clauster is on, we
have other 20 servers and none have that problem. We had DELL Tech services
with three techs on the phone and we still couldn't figure it out. We have
triple checked the settings on the core switches, we have change ports,
cables and nics, as I stated before all the other servers work fine.
Exchange works great but only the server VLAN. Some how none of the nodes
want to inherit the routes from the gateway.
We've never seen this before. We are completely puzzled of this issue. If
any one has experienced something like this please let me know. I'll be
interested in knowing the reason.
Thanks,
Sal
"Ed Woodrick" <ewoodrick@ed-nospam-com.com> wrote in message
news:uKFqB282EHA.2316@TK2MSFTNGP15.phx.gbl...
| Quote: | Exchange completely relies on the network layer to do it's routing.
My guess is that you probably don't have WINS and DNS properly setup and
things can't find each other.
Can all devices ping each other?
Are all default routers/gateways set on all systems correctly?
"Sal Tinajero" <stinajero@berkleyindustries.com> wrote in message
news:OlvrNH72EHA.2624@TK2MSFTNGP11.phx.gbl...
We've just implemented a VLAN network in our company. Everything went
smooth except our Exchange Clauster, only the systems in the VLAN that
Exchange belongs to can see it. For some reason Win2k3 with Exchange 2k3
does not allow the routing to be inheritered from the firewall. All the
other servers running Win2k and Win2k3 Standard in the Exchange VLAN are
visible from the other VLANs. There is something between the combo
Win2k3 and Exch 2k3 that does not allow it to route properly. Does
anyone have any leads to this problem? Has anyone experience that same
issue?
Thanks in advance.
|
|
|
| Back to top |
|
 |
Gerald Aigenbauer
Guest
|
Posted:
Mon Dec 13, 2004 9:04 pm Post subject:
Re: IP routing |
|
|
hi sal!
do you have a default gateway pointing to the vlan-switch or do you use
routing protocols? which protocols?
gerald aigenbauer.
"Sal Tinajero" <stinajero@berkleyindustries.com> schrieb im Newsbeitrag
news:e1g67Z92EHA.2608@TK2MSFTNGP10.phx.gbl...
| Quote: | DNS works like charm! Its only the two nodes that have the problem and
cannot ping to the other VLANs. We can ping the NAS device but not the 2
nodes and the virtual IP. In the same VLAN that Exchange clauster is on,
we have other 20 servers and none have that problem. We had DELL Tech
services with three techs on the phone and we still couldn't figure it
out. We have triple checked the settings on the core switches, we have
change ports, cables and nics, as I stated before all the other servers
work fine. Exchange works great but only the server VLAN. Some how none
of the nodes want to inherit the routes from the gateway.
We've never seen this before. We are completely puzzled of this issue.
If any one has experienced something like this please let me know. I'll
be interested in knowing the reason.
Thanks,
Sal
"Ed Woodrick" <ewoodrick@ed-nospam-com.com> wrote in message
news:uKFqB282EHA.2316@TK2MSFTNGP15.phx.gbl...
Exchange completely relies on the network layer to do it's routing.
My guess is that you probably don't have WINS and DNS properly setup and
things can't find each other.
Can all devices ping each other?
Are all default routers/gateways set on all systems correctly?
"Sal Tinajero" <stinajero@berkleyindustries.com> wrote in message
news:OlvrNH72EHA.2624@TK2MSFTNGP11.phx.gbl...
We've just implemented a VLAN network in our company. Everything went
smooth except our Exchange Clauster, only the systems in the VLAN that
Exchange belongs to can see it. For some reason Win2k3 with Exchange
2k3 does not allow the routing to be inheritered from the firewall. All
the other servers running Win2k and Win2k3 Standard in the Exchange VLAN
are visible from the other VLANs. There is something between the combo
Win2k3 and Exch 2k3 that does not allow it to route properly. Does
anyone have any leads to this problem? Has anyone experience that same
issue?
Thanks in advance.
|
|
|
| Back to top |
|
 |
|
|
|
|