Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problem accessing some machines at a different location

Status
Not open for further replies.

techi03

IS-IT--Management
Joined
Jun 29, 2004
Messages
5
Location
CA
we have two networks in seperate buildings, one is a DHCP network (192.168.2.X)+ a few static(192.168.2.1 to 192.168.2.30). The other is static (192.168.32.X),
both the buildings have cisco 760 routers connected by and ISDN line.
both networks can talk to each other, the problem is that some computers cannot.
e.g 192.168.2.147(dynamic) can talk to all machines except 192.168.2.4(static). But can talk to 192.168.2.3, 5, 9 etc (dynamic).
192.168.32.134 (static) can talk to machines on the other network except 192.168.2.3.
i can ping both sides of the gateway on either network, just seems wierd that some machines cannot communicate.
any suggestions?
Thank you
 
what subnet mask and is ip classless in your config?

john poole
bellsouth business
columbia,sc
 
255.255.255.0
everywhere
 
What operating system are on these machines, if it's Windows XP, make sure the internet connection firewall isn't checked off. Also do you have like a ping sweep or anything, to make sure the ip addresses that are not responding are soley the only ones. If you can post your router config, or email them to me, that would help me seeing exactly what you have.
 
my laptop is an XP machine(firewall disabled) that cant ping 192.168.2.4 but can ping 192.168.2.9, 3. etc.
192.168.2.9 and 3 are w2k servers, the machine on 192.168.32.20 is a win98 machine, now it cant even logon to hotmail.
will do a ping sweep and let u know, along with the router config.
the problem is that i just started workign here and the network is a mess, so i dont know what's happening.
Thanx
 
Ok, yeah since your new in that environment, I'm sure there will be things that don't make sense, but you'll figure it out as you get more familiar with everything. Give us anymore input as you get it.
 
ok will do, but what i dont get is that if there was a problem with the config file, then would all computers not be able to access each other.
what i have here is:
some machines on subnet1 cannot access only a few machines on subnet2, but can access others.



 
ok i think i have figured seems like 192.168.2.3 is the problem.
here is the thing, I have 3 networks, office and prod are on the same subnet and mshop is on a different.
office and mshop are connected with the cisco's ISDN
prod is connected to office through a fiber line. when i run a trace from prod to office it seems to be using 192.168.2.3 as a gateway to get to office.
and 192.168.2.3 is the only server that cannot be accessed from mshop.
so it looks like 192.168.2.3 has some sort of a route configured on it that could be the problem.
now i have to figure out where it is, RRAS is not configured.
any ideas?
thanx
 
Well the reason I would check the router config is to make sure there's no static route, or anything weird going on with a wrong subnet. Pretty much though I would check all the IP statements.

As for the the 2.3 server, check to see if there are multiple nics installed. Now from what I can gather OFFICE and PROD are on the same IP segment, so PROD shouldn't need to have 2.3 as a gateway, because it doesn't need a gateway to reach the OFFICE network/domain because it's on the same IP segment which is 2.x right? PROD and OFFICE is connected via fiber, which is from a switch to a switch right? Now for the IPs you can't ping, what happens when you do a traceroute to them? Also if you have switches involve and obviously routers, take it one step closer to the destination and try pinging or tracing from the switch, router, etc.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top