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
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
by cuziyq
by larryrh
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
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
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
Hope this helps.
by larryrh
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 larryrh
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
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 larryrh
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 larryrh
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 larryrh
by tyger07
by larryrh
by tekomni
by larryrh
by larryrh
This discussion is closed to new replies.
Trending Mac OS posts
Sort by Trending