[SOLVED] screwed by IP filtering?
[SOLVED] screwed by IP filtering?
- Subject: [SOLVED] screwed by IP filtering?
- From: Scott Ribe <email@hidden>
- Date: Tue, 11 Jun 2002 12:26:01 -0600
>
I have my little Carbon/OT based client and server working fine on 1
>
machine. But when running them on separate machines, the client just gets a
>
disconnect as soon as it tries to connect, and the server never sees the
>
connection.
>
>
Using netstat the listener shows up as expected, port scanning the server
>
from the server shows the open port, port scanning the server from the
>
client doesn't show it. The 2 Macs are on the same subnet and connected via
>
a dumb hub.
>
>
So I think that OS X on the server is filtering out the requests. I can find
>
no documentation on port number allocation in OS X; I've tried a
>
not-currently-used port number in the 6k range and one in the 19k range.
>
>
Where can I find some guidance on choosing port numbers, and some
>
information on allowing access from the outside world? I know I've seen
>
articles on this on the web, but danged if I can find any info now!
I'd rather go away and pretend this didn't ever happen. But instead I need
to post this so that I don't give anybody the idea that there is something
mysterious in OS X grapping tcp connections and killing them.
What was going on was that in the middle of a long session I somehow got a
mental bit flipped and in my mind reversed the IP addresses of the Macs I
was using, so that the client was trying to connect to itself instead of the
server. Duh. I am really surprised at how long it took me to notice that I
had "changed" my own IP address in my head ;-)
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 665-7007 voice
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.