|
|
why do I get -> go.read.the.rfc.this.server.doesnt.r
|
|
|
|
Grizzled Veteran
Join Date: Sep 2000
Location: Adelaide, Australia
Status:
Offline
|
|
OK its macosx 10.2.2 on a new PB 1 gig. I am using an Airport Base Station
and manually assigning my ip as 10.0.1.10
If I go into Sharing it says:
Computer Name macmurray2
Rendezvous Name macmurray2 .local
Network Address go.read.the.rfc.this.server.doesnt.resolve.rfc1918
If I click on the go.read.... it changes to 10.0.1.10
Other macintosh users can access your computer at
afp://go.read.the.rfc.this.server.doesnt.resolve.rfc1918/
If I open an XTerm in OrborOSX it has go.read.the.rfc.this.server.doesnt.resolve.rfc1918
as title.
I think in my previous powerbook I got rid of this by some trick
but I have forgotten what. Any ideas ?
When at work on the internet with a proper IP I don't get anything like this
of course.
Thanks - Michael
|
|
|
|
|
|
|
|
|
Forum Regular
Join Date: Sep 2000
Status:
Offline
|
|
Originally posted by mmurray:
OK its macosx 10.2.2 on a new PB 1 gig. I am using an Airport Base Station
and manually assigning my ip as 10.0.1.10
Network Address go.read.the.rfc.this.server.doesnt.resolve.rfc1918
If I click on the go.read.... it changes to 10.0.1.10
Other macintosh users can access your computer at
afp://go.read.the.rfc.this.server.doesnt.resolve.rfc1918/
I haven't read RFC 1918 in it's entirety ( http://rfc-1918.rfc-index.net/).... but I'd imagine since you're using the 10.x.x.x block of IP addresses, which are unallocated and used for private networks (and therefore don't resolve), you're not resolving, and apple (or whoever implemented the network code) put this little phrase in instead of an error message.
You could try using a different IP address range (a lot of folks use 192.168.x.x, which is also unallocated, but you might run into the same problems) but I don't know of a workaround other than that. Hope this helps... more of an explanation than a solution though.
-uD
|
|
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Oct 2000
Location: Cardiff, Wales
Status:
Offline
|
|
I was getting something similar (TheAddressDoesNotExist) and tried a few things which may or may not have been responsible for it working now... !
I don't have Airport, but I assume the basestation acts as a DHCP server. In which case, you could try 'DHCP with a static IP address' in your Network Preferences.
You can also try typing 'hostname macmurrary2' as root in the terminal.
Or add '10.0.1.10 macmurray2' to your hosts file (/etc/hosts I think... depressingly, I know it's winnt\system32\drivers\etc\hosts on Win2K )
Chris
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Sep 2002
Location: New York, NY
Status:
Offline
|
|
This sounds like you have enabled Airport to Ethernet Bridging. This makes your private 10. network be part of your ISPs network, which it can't.
|
Vandelay Industries
|
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Sep 2000
Location: Adelaide, Australia
Status:
Offline
|
|
Originally posted by Art Vandelay:
This sounds like you have enabled Airport to Ethernet Bridging. This makes your private 10. network be part of your ISPs network, which it can't.
No I haven't got that selected. Thanks for posting though
Michael
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|