Discussion Locked

Macintosh Routing Problems

0 helpful
29 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a G3 Mac on the same TCP/IP network, (mostly windows NT) that is working fine. I can use Microsoft Mail Exchange and also use the Proxy server to surf the intranet. Now when I moved the Mac to another subnet, using a NT server as the router, not changing anything on the Mac, the Mac now can not use the proxy to get to the internet. The Mac is using DHCP and has a good address for the new subnet. I have tried using Mac-ping to ping the proxy, I do get a reply. When I use trace route to the proxy it also gets a reply thru the gateway. When using IE4.5 for Mac?s, I get a ?HTTP Error 403?, ?403.6 Forbidden: IP Address Rejected?. The new Mac address of the new subnet is in the "LAT" table on the proxy, also other windows NT pc's on that subnet are all using the proxy server without any problems. I also have modified the host file on the Mac to define the address of the proxy server. The Mac is using os9. As I said works just fine on the same subnet as the proxy server.

29 replies

by gus g

Hey there, we had a similar problem at the building with a couple of our macs after moving them to a different office. Our solution was to enter all the tcp/ip information manually. After we did this everything worked fine, good luck.

Gus g

by larryrh

I have tried to add all info manually, static address, router, mask, not using the DHCP, in the TCP/IP setting on the Mac. it does not make any differance. Also edited the Host file on the mac to define the Host name of the proxy server.Still noluck.. I even made all these changes and moved the Mac back on our subnet to make sure it still works, and it still did. Any more ideas? I think the problem is in the Host file but can't find any info about how to enter a routing table on a Mac.

by dcaratti

Sorry, I didn't see that you mentioned that you are using OS 9.

Instead of manually tying in all of the IP info, try inputing only your domain (ie intranet.company.com) in the additional search domains box of the TCP/IP Control Panel. You may have to go to advanced mode to see that box. Advanced mode is activated by selecting Edit - User Mode... click on the Advanced radio button.

I've had to do that with my Macs. It allows them to still receive a DHCP address yet still find the router.
Hope that helps.

Dave

by larryrh

Tried this. But no help either. Added the doman name, the router name, added all the names. there's gotta be a way to make or eddit the routing tables on a Mac to define the route. Even thou using tracert or ping it resolves the address or name through the Hosts file.

by cuziyq

I also have run into a similar problem at my company. Here's what I did to fix it, as unorthodox as it sounds. Disable AppleTalk, get rid of any static hosts files you have, remove all entries from your DNS search order, then disable DHCP. Then Ire-enabled DHCP and AppleTalk, then rebooted. It sounds bass-ackward to do it that way, but ti worked for me. Maybe it'll work for you.

by larryrh

Tried this, didn't help but was a good thought, never know what a clean install of the network does. Have fixed many problems on windows nt doing this. Thanks for the answer.

by redwards

Well, I would suspect that it has something to do with the proxy configuration. You are getting responses back from the proxy server, so you are able to connect to it just fine. You can traceroute and ping it as well.

If I remember correctly, the MAC address does not travel accross routers, and is only used on a local subnet. Therefore your proxy server must have a rule to allow the IP number of the mac on a different subnet, you can't use the MAC address at this point.

If it was a routing issue, you would not be able to ping or tranceroute, and browsers would complain of not finding the computer.

by larryrh

There are Windows Nt pc's using the Proxy server on the same subnet as the Mac that's having the problem. I did hard code the Mac's ip in the proxy's LAT table. or maybe I didn't understand your answer. Thanks

by bill roberts

Some questions for you.

Is the NT PC that is acting as a router enabled to route Appletalk or Ethertalk? Is it enabled to tunnel appletalk in IP? Is it running the Ethernet_II or Ethernet_SNAP frame type?

If you answer these, you may solve your own problem.

Bill Roberts

by larryrh

Yes on the route Appletalk and also rip for tcp/ip. Don't know how to enable tunneling apletalk! Using nt4.00 tcp/ip for the router. with seeding turned on to both nic cards.

by dgaunt

I know this is not going to seem like much of an answer considering you cannot get to the internet, but have you updated your OS reciently? There are some known issues with Open Transport 2.5.2 (original OS 9 version) and Macintosh has a newer version out. OT 2.6 fixes several issues with TCP/IP. This is free from Apple's home page

http://asu.info.apple.com/

Hope this helps.

by larryrh

I checked out the open transport, it's 2.6.2. Also applied the the patch 9.04 for the os. also did not help.. I brought the Mac back to this side of the router and the Mac still connects to the internet, go figure. The problem is on the NT 4.0 router not passing the Mac address but can't find the correct answer to fix the problem.Thanks

by ryan mccaigue

Long shot but??

Have you looked into the proxy settings on
I.E. ??

Consider trashing the TCP/IP Prep file in
the system folder, and TCP/IP Pref. file in
the Prefrences folder and restarting.
Appletalk should not be in play for this
issue.

by barekhunt

Sometimes, when Macs are moved in a NT Network, the Mac will switch to another Mac zone, do you have more than one Mac zone?
One what subnet is the Seed Router located?

by larryrh

Yes, there's two zones now. I added the second zone to see if that would fix this problem. It didn't...The "seed router default zone" is on the second subnet. The seed router is on the subnet that the mac's will not connect to the Intranet. This has always been this way. did not change that at all. The "seed router" is also the same NT router that separates the two subnets. Keep in mind this has never worked on the second subnet, Mac's getting to the Intranet. The Mac's do change Zones depending on which side of the router they are attached. If you have read the past answers, other NT PC's can get to the Intranet fine from this second subnet.. Hope you have an answer!!!

by drobledo

You must be pretty frustrated by now. :-)

This is just a shot in the dark since you've probably checked this already but have you tried using different applications, i.e., Netscape Navigator? You said ping and tracert work so everything seems fine and dandy up to the network layer. . .

There's been a lot of good ideas posted up here. The only other thing I can come up with is double check your Internet control panel for conflicting settings and if available try using earlier versions of the Mac OS to see if you can duplicate the problem. (Not that you want to duplicate the problem but you know what I mean :-)

Tough cookie to crack. Good luck!

by mikel~t

Can you ping the Mac from the Proxy Server when they are separated by the router? If the proxy can't send back the authentication to the Mac, that might explain why you are getting connections refused? I've also run into issues with the Macs and Proxy setup. I also noticed you use intranet and internet throughout your description of the problem: are you only accessing the internet, or are you accessing local internal web servers and hosts?

I think the issue is on your router setup. Although the PCs are working, it would appear that TCP/IP isn't working properly with your Mac and it's appletalk default protocol. WIth a PC, you can change the binding order...macs aren't as easy to manipulate. It will either use appletalk by itself,or tcp/ip by itself.

I understand your frustration: I would really take a harder look at the segements you have made, and check to see that you aren't limiting more than you need to between the two segments.

I'm not much help, but I just thought a fresh look at things might come in handy.

Good luck.

by espen

This has to be an issue with the access
configuration in either your proxy or the
website you are trying to access.

Does the HTTP error come from the proxy
or from the website you are trying to
access?

The 403 error is a client error, which is
returned if you try and access an area you
are not authenticated for. I suggest
setting static IP's on the mac, and see if
you get through the proxy. If you don't, try
and set the same static IP on a PC, and
see whether you are let through then.

If you are, then something really weird is
going on, because a router cannot see
any difference between TCP queries from
a mac or a pc, appart from the packet
size.

Also try and run debugging or auditing on
the proxy, to see how the connections are
recorded by the proxy. (Use netstat or
something like that to see whether the
incoming connection is actually
connecting to the proxy)

Try and configure static IP routes on the
proxy, and make sure there are no
conflicting routes anywhere.

If that doesn't work, try setting up a proper
router, rather than using NT, as NT's
routing services are quite bad.

Espen

by tyger07

Try this if it still matters..go to system folder and throw away the following preferences aslm, appletalk and tcp/ip..emtpy trash and reboot...Frank

by tekomni

I would try using a static IP instead of DHCP and also upgrade IE and the OS (which would be IE 5 and OS 9.1). I would say that for some reson the Mac doesnt like the Subnet/NT router combination.

by larryrh

The Mac is using a static ip and also using OS 9.1 now. I could not find IE 5.0 for mac but have the lattest of both IE and Netscape on the Mac.. I have installed a PC next to the users using Windows NT and the now can use the Internet.. Go figure, Macs do not like NT routers...

This discussion is closed to new replies.