Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with Network




On Dec 26, 2007, at 12:21 PM, Ron Robertson wrote:


On Dec 25, 2007, at 11:50 PM, Dan Shoop wrote:


On Dec 26, 2007, at 2:29 AM, Ron Robertson wrote:

Sorry I wasn't clearer. What happens is that the other computers no longer can access the internet, just each other. I have an Airport Extreme station that has been providing DHCP & NAT services for months (years, really, since it replaced an older Airport station that did the same thing). I'd prefer to have the Airport continue to do this since the network isn't interrupted by computer restarts due to updates, etc.

Yes, you said all that before, but what does that really all mean?

For instance when the can't "access the Internet" what can't they access? What is it they try to do and fails? When it fails what errors are reported?

When trying to go to a web page, the browser times out. That is what I mean by not able to access the internet.


Times out how? Why not post the *actual* error please!

To further clarify, when most users "can't access the Internet" they really are having DNS issues and can't resolve hostnames. Is host name resolution occurring properly? What do pings to specific foreign IP addresses reveal? What testing have you done and what are the results???

Anyway, my network consists of the private network,

Meaning what exactly? Meaning it's RFC1918? Meaning it's NATed? What?

The private network is all on Private IP Addresses (192.168.0.x) that it gets from the Airport station. They are all connected to a Gigabit Ethernet hub.

Then why do they need the airport if they are connected to the hub. And is it a hub or a switch?


As I mentioned before, NAT & DHCP are provided by the Airport station. I do think it is DNS issues, but I don't know why the XServe would interfere with resolving hostnames. I did try pinging foreign IP addresses from the affected machines without success.

So sounds like you have a routing problem. Consulting your routing tables should point out your issue.


which is all on a Gigabit hub, and the public network, which is on a T1 router with a smaller hub built in.

Connected how? What separates/conencts them?

The Public one

"Public one" what? Subnet? System? What is this network CIDR block?

is on the T1 router (it includes 6 ethernet ports), I've connected the WAN port of the Airport station there,

And is the Airport bridging or NAT'ing?

one of my personal Ethernet ports (to my computer, which has 2 ethernet ports),

Which are ordered how?

and 1 port from the XServe. They're all configured with the Public IP addresses I was given by our T1 provider.

A single address?

The two networks are on separate devices, I do not have them directly connected to one another, only indirectly via the 3 devices I mentioned above (my computer, the Airport & the XServe).


I'm sorry but I'm lost with this picture or lack thereof.

I have the Airport connected to both networks.

Interesting since it only has the concept of one subnet. How is this connected to both networks???

I have the WAN port connected to the T1 router, and one of the Ethernet ports connected to the Gigabit router (that's on the private network).


I also have my own personal system connected to both networks (it's a MacPro with dual interface),

And routing is configured how? How does it know how to route what to where? What is its primary NIC, gateway and network route?

The primary NIC is to the T1 router, secondary to the Gigabit hub. I manually set the IP addresses for both Interfaces to fit their respective networks (i.e., 192.168.0.5 for the public one, and one of the available public addresses [72.245.x.x] for the Primary NIC).


Which system is this?

and I was wanting to have the XServe on both networks,

Again read the last comment?

but no matter what I do, if I hook up the XServe to either or both networks, it stops internet services for the private network (no effect on the public one).

Disrupts what exactly? How is routing occurring?

It disrupts the internet connection, but not the network connections (all computers can see each other on the network, but they can't connect to the internet as mentioned before). If by routing you mean DHCP & NAT, that's provided by the Airport station, if you mean the physical routing, that's provided by the Gigabit hub.


I thought that a clean install might fix the problem, but I'm still having the same problem.

Indicating that this is not a problem with the software but how you've configured it.

I'm sure. I originally set it for Standard install, then upgraded to Advanced to access more parts to see if I could find something that seemed wrong, but DHCP and NAT are not on and should not be active since both are showing as not activated in the server admin. I've configured hundreds of computers (Macs [OS 9 through Leopard), PCs [win 95 to XP], Printers, and one SCO Unix box) for networking over the years, and even managed a few OS 9 & OS X Servers (10.2 & 10.3), plus one Win NT Server, including setting them up for mail, mailing lists, windows & mac file sharing, and printer sharing, but it's been a while since I've done that (about 3 years), so some of what I used to do is getting a bit fuzzy.


If you have some idea of where I should look to troubleshoot, I'd greatly appreciate it!

Perhaps start with telling use what troubleshooting you've done?

I've tried connecting only one ethernet port to the network (i.e., only the public-configured NIC, or only the private-configured NIC from the Xserve, and it still immediately stops the computers on the private (gigabit hub side) from accessing the internet, but not each other (as detailed above). I've gone into the Server Admin and checked for anything obvious, like DHCP or NAT running on the XServe (which they were not), checked and rechecked all the settings on the Airport station in case something was wrong there. Checked all the TCP settings on the Airport and the Xserve. Beyond that, I can't think of what more to check, so that's why I wrote the list.


Sorry I'm hopelessly lost by the lack of clarity.

Bottom line is you have what appears to be a routing issue. Examine your routing tables on affected machines and it should be obvious.

-dhan

------------------------------------------------------------------------
Dan Shoop
Computer Scientist
iWiring / U.S. Technical Services

email@hidden
AOL IM .................... iWiring
Nextel .................... 1-714-363-1174
Operations TOC (24/7) ..... 1-866-901-USTS
USTS Offices .............. 1-714-374-6300

For immediate response for urgent matters please speak to the Duty Officer
at the USTS Tactical Operations Center (above) who can reach me by radio.



_______________________________________________ Do not post admin requests to the list. They will be ignored. Macos-x-server mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macos-x-server/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.