Re: Cant Connect to Win2008 Server from 1 of several subnets
- From: "Scott Townsend" <scooter133@xxxxxxxxxxxxxxxx>
- Date: Thu, 9 Oct 2008 13:39:36 -0700
We don't really have too many hosts in each of the Class B Subnets. but we use parts of the Subnet for Different devices.
10.x.0.x servers
10.x.1.x Other IT Items, WiFi, Printers, etc
10.x.2.x Spare
10.x.3.x DHCP for Clients
10.x.4.x DHCP for Clients.
10.x.5.x Engineer's Testbed.
10.x.6.x Tech Support Testbed.
Etc....
Anyway... I found the issue... I had the Gateway Address set for the Firewall and not the Router.
Which is interesting, As the firewall has a Static Route for the 10.254.0.36 Subnet that points to the default router that I changed the machine with the issues to.
So Machine pointed -> Firewall
Firewall Pointed 10.254.0.36 to 10.1.0.1
When I pointed machine -> 10.1.0.1 as default Gateway All is well...
One of the reasons I like to have my Servers DHCP with Reservations... Though since this was a DC, hard to do that... (-:
Thanks!
"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message news:u2A7QrkKJHA.5692@xxxxxxxxxxxxxxxxxxxxxxx
"Scott Townsend" <scooter133@xxxxxxxxxxxxxxxx> wrote in message news:e4$mmfkKJHA.3744@xxxxxxxxxxxxxxxxxxxxxxxThank you for your reply...
1) There are no ACLs on the router as this is just a Site to Site router that we want all traffic to pass.
Being a site-to-Site link greatly increases the chance of my forth suggestion:
4. Flaw in the LAN's "routing scheme"
2) The Mask on the servers & Ethernet0 on the routers are all 255.255.0.0
The Mask on the Serial Port is 255.255.255.252,
DFG?
Ethernet segments should not be allowed to grow above 250-300 Hosts,..therefore you should be using 255.255.255.0. The 255.255.0.0 would be used in routing tables to supernet IP segments into a single route table entry to make the route table more efficient if the network design dictated that. It is doubtful that this is your problem,..but is something to consider.
The "252" mask is normal for a WAN link,..no problem there.
Since the machine that does not work is on the same Switch as the machine next to it and it can talk to the router's serial port just fine, I would think that the Router is set up to handle the traffic and pass the data.
If I took an IP on the machine that didn't work and moved that IP to a machine that does work and now that IP address does work... It has to be something on the machine...
I agree, but at the moment there is nothing that jumps out at me. I don't have any other suggestions right now.
--
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.
-----------------------------------------------------
.
- Follow-Ups:
- Re: Cant Connect to Win2008 Server from 1 of several subnets
- From: Phillip Windell
- Re: Cant Connect to Win2008 Server from 1 of several subnets
- References:
- Cant Connect to Win2008 Server from 1 of several subnets
- From: Scott Townsend
- Re: Cant Connect to Win2008 Server from 1 of several subnets
- From: Phillip Windell
- Re: Cant Connect to Win2008 Server from 1 of several subnets
- From: Scott Townsend
- Re: Cant Connect to Win2008 Server from 1 of several subnets
- From: Phillip Windell
- Cant Connect to Win2008 Server from 1 of several subnets
- Prev by Date: Re: Cant Connect to Win2008 Server from 1 of several subnets
- Next by Date: Wireless domain logon?
- Previous by thread: Re: Cant Connect to Win2008 Server from 1 of several subnets
- Next by thread: Re: Cant Connect to Win2008 Server from 1 of several subnets
- Index(es):
Relevant Pages
|
Loading