iinet ADSL Problem - Update 2
Connected at last via ADSL in System X.1.2 on the G4 . I loaded the same system on the iBook and took it (and the modem) into iinet. The problem is the DSL 300 PPPoE client connects but does not bridge with Macs. DSL have been contacted and are going to fix this some time. iinet worked on a number of Macs with the same problem yesterday, I was just the unlucky one to be first with this problem. In the meantime the modem is set to RFC so it bridges and I am using the PPPoE client in OS X. Can I get an OS 9 PPPoE client somewhere? I'm not too keen on OS X! The support guys at iinet have been warned not to try and connect Macs via the PPPoE in the modem. Diana
Re: iinet ADSL Problem - Update 2
Can I get an OS 9 PPPoE client somewhere? I'm not too keen on OS X! According to http://whirlpool.net.au/faq-mac.cfm you should be able to get MacPoet http://www.winpoet.net/products/poet.html Good luck, Shay -- === Shay Telfer Perth, Western Australia Technomancer It must be bunnies! Opinions for hire [POQ] [EMAIL PROTECTED] fnord
iinet ADSL Problem - Update
Back on the air again via dial-up. First thanks to all who have sent helpful suggestions. I spent hours on the phone to iinet speaking to Stephen with no resolution to the problem. For any who are interested read on, the position is as follows. 1. OS 9 is supposedly supported. I referred Stephen to the section of the Standard Form of Agreement quoted by Lara. He found it but said it is not correct. My husband made the application and he does not remember reading that bit, but as he had a phone call about the death of a friend whilst he was doing it maybe his concentration was not as good as usual. 2. The ADSL Modem connects to iinet and all the addresses are supplied by the DHCP Server. As Onno guessed they do not use the DHCP Client ID. 3. I got IPNet Monitor. It costs $30 but you have a 3 week free trial period. I shall definitely purchase it. 4. When connected via ADSL the only address I could ping was the IP address. When I connect via dial up I can ping the iinet and Curtain DNS addresses. 5. Stephen wondered if the IP address was faulty as I always got the same one, so far only 50 people are connected to BLIINK. They checked it out and rang back to say it worked OK. 6. They asked if I had a fire wall. Answer NO. 7. They have decided it is something else on my computer which is causing the trouble and want me to take it in (plus the modem) and let Justin (their Mac expert) have his way with it. 8. Answers to other questions. Are you using PPPoE or static Ethernet? I don't know, I selected PPPoE on the screen which comes from the modem (in Netscape 4.77). Are you on iinet's new Blink contract? YES Are you using OS 9 or OS X for your connection? OS 9.2 Are using the Dlink DSL 300 modem? YES Are you still using your internal modem? Only when I want to access the Internet via dial-up to send emails! I am afraid some of Richard's queries were too technical for me as I am not OS X savvy. 9. I thought I would try using the iBook. In OS 9.1 I got a message that there was not room for another account but it would not let me delete the old one. In OS X.O Internet Explorer loaded the page from the modem but kept giving me an error message saying it could not load the panel to access the page even though I could see it. I had to force quit several times but eventually deleted the old account and added the new one but every time I clicked on Connect IE produced the error message and the rolling ball. I gave up! 10. I tried in OS X.1.2 on the G4. Using IE I managed to access the page in the modem, it still had the correct details but the bottom half of the page was missing. I tried restarting everything but I got a message that the server was not accepting connections ie 192.168.0.1, the page in the modem, was now inaccessible. I rebooted in OS 9.2 and got the same thing. First time I got half the page then nothing. I gave up and went to bed. This morning I tried a again, same story. But when I dialed in this morning and looked at my connection history there are two last night for 4 and 9 sec durations, probably from the iBook though the connection was too short to register on the screen. 11. When I changed the configuration in TCP/IP to use dial-up I noticed it had strange addresses in it, normally when you access the page in the modem it has the IP and server addresses as 192.168.0.1. This time I had IP 169.254.229.238, Server 224.0.9.251, the router was the same as the IP and the subnet mask was 255.255.0.0 (it is usually 255.255.255.0). 12. So I got rid of the settings and tried again. I got the full page this time and it indicated I was already CONNECTED to iinet, usual IP and gateway addresses. Netscape 4.77 kept telling me repeatedly that it could not connect to 192.168.0.1. I had to cancel the notice and quit quickly before it came up again. The connection history shows a 2 sec connection. Conclusion: I think it is gremlins and quite beyond me to solve. We have ordered a router and wireless connection from WA Solutions so I think paying them to sort it out will be the least stressful option. Diana
Re: iinet ADSL Problem - Update
5. Stephen wondered if the IP address was faulty as I always got the same one, so far only 50 people are connected to BLIINK. They checked it out and rang back to say it worked OK. Interestingly, one of my (PC using) workmates just signed up for bliink but hasn't been able to use his account yet due to router problems at iinet's end. No doubt in your case they'll blame the Mac though! Have fun, Shay -- === Shay Telfer Perth, Western Australia Technomancer It must be bunnies! Opinions for hire [POQ] [EMAIL PROTECTED] fnord
Re: iinet ADSL Problem
Lara Hopkins wrote: Ah - I might not be able to help you too much then. Is there any reason you're not running OS X? I only ask because iinet support OS X for their Bliink product, and doesn't support OS 9 (so I'm not too surprised that you haven't had much help from them). Is this true? iinet asked me what OS I was using and did not tell me they only support OS X. I do not wish to use OS X as I am addicted to a few old programs, I have not tried them in Classic. I recently bought Office 2001 but Word 5.1a still runs faster and does all I want, it also does one thing which I can't do in later versions. Also I just want to get on with the things I like to do and it will take time to master a new system at my age (66) as the little grey cells are not as active as before. NB: Bottom posting as suggested by the very helpful Onno. I have not had time to try his or Lara's suggestions but I shall when I get back from the physiotherapist (aged body parts failing too). Diana
Re: iinet ADSL Problem
Onno Benschop wrote: Are you using PPPoE or static Ethernet. If the former, you'll need to run an application on your connection machine to actually connect. If the latter, plugging it in may do the trick. It is possible, but without looking into the DSL 300 further I cannot tell, that it is in fact running the PPPoE software. It does. Though whether it's been configured properly is anyone's guess; hence my suggestion of an on-site visit rather than iinet looking at the Mac in isolation. -- Lara
Re: iinet ADSL Problem
Sorry for the top posting but I like to see the reply to the question I have already asked - I don't want to read it again or scroll through it to the reply. Having got that off my chest ... Dianna I can only suggest that you take a systematic approach to solving this problem. Get some software that will allow you to ping - IPNetmonitor as suggested by Onno or my preference MacTCP Watcher. The latter is free, I'm not sure about the former. Assuming you are using a direct Ethernet connection, follow these steps and post the results here, then we can help further; 1. Open the TCPIP control panel and record the IP address (and mask), DNS or Name server address and router/gateway address. Then close the control panel. If you do not have any of these then your connection won't work. If any of them are wrong then the connection won't work or will be erratic at best. 2. Open the application that lets you ping and ping the router/gateway address. This should be (must be) the ADSL modem. If you have success here then the first leg of the journey is working. If not, you have a local connectivity problem that may be physical (cable not working, modem port broken or Mac Ethernet port broken) or configuration (TCPIP settings wrong). 3. If 2 works then try pinging the DNS or name server address. If this works then you should, in theory, be able to use name resolution as described by Onno in one of his replies ie. You can use names like www.iinet.net.au instead of the IP address. 4. Then try pinging further afield like the address Onno supplied or ping our DNS server here at Perth iX (203.188.144.1) or www.cisco.com (198.133.219.25). Regards Greg on 1/7/02 7:01 PM, Diana Graham Stevens at [EMAIL PROTECTED] wrote: We have switched to ADSL, we remained with iinet because we wanted to retain our email address which is in a number of hard copy publications. What a mistake! The problem is that although the ADSL connection appears to be successful to the people at iinet and the IP address etc are assigned it does not work. Neither Netscape nor Eudora can find the server or any other address tried. When iinet tried to 'ping' the address it did not work, ie it is a dead connection. I have looked at the connection log and the ADSL connection is recorded as well as this mornings dial up. Can anyone suggest what is wrong please. iinet want me to take my Mac in to them to fiddle with but I am not keen to do this! Diana -- The WA Macintosh User Group Mailing List -- Archives - http://www.wamug.org.au/mailinglist/archives.html Guidelines - http://www.wamug.org.au/mailinglist/guidelines.html Unsubscribe - mailto:[EMAIL PROTECTED] Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Re: iinet ADSL Problem
on 2/7/02 4:21, Onno Benschop at [EMAIL PROTECTED] wrote: Are you using PPPoE or static Ethernet. If the former, you'll need to run an application on your connection machine to actually connect. If the latter, plugging it in may do the trick. While this used to be true it isn't any longer. The D-Link DSL 300's that iiNet are sending out have the connection software for PPPoE built into them. Simply plugging them in should just work. The modem can run in the mode where it needs PPoE software to be running on the machine it's hooked up to, or in the mode for a straight Ethernet connection as well. Talented little modem. Unfortunately it creates one of three states the modem can run in which without looking into the modem the iiDrone has no idea which mode the modem is in. It is possible, but without looking into the DSL 300 further I cannot tell, that it is in fact running the PPPoE software. If it's the default from iiNet it should be running the PPPoE software in the modem. As I've said above thought there are two other configurations the modem could be set to.
Re: iinet ADSL Problem
--- In [EMAIL PROTECTED], Diana Graham Stevens [EMAIL PROTECTED] wrote: I only asked because iinet's experts have run out of ideas. Their only other option was to take the Mac in to them and I plain don't trust them. Hi Diana, I happen to know that one of Chime's (a subsidiary of iinet) senior network engineers is a bit of a Mac person - his name is Ian Henderson. See if they can get him specifically to have a look at it. Good luck!! Meg
Re: iinet ADSL Problem
sonic_echidna (Meg) wrote: I happen to know that one of Chime's (a subsidiary of iinet) senior network engineers is a bit of a Mac person - his name is Ian Henderson. See if they can get him specifically to have a look at it. Nathan somebody in ADSL support is also a good one to strike. Lara
iinet ADSL Problem
We have switched to ADSL, we remained with iinet because we wanted to retain our email address which is in a number of hard copy publications. What a mistake! The problem is that although the ADSL connection appears to be successful to the people at iinet and the IP address etc are assigned it does not work. Neither Netscape nor Eudora can find the server or any other address tried. When iinet tried to 'ping' the address it did not work, ie it is a dead connection. I have looked at the connection log and the ADSL connection is recorded as well as this mornings dial up. Can anyone suggest what is wrong please. iinet want me to take my Mac in to them to fiddle with but I am not keen to do this! Diana
Re: iinet ADSL Problem
Diana Graham Stevens wrote: The problem is that although the ADSL connection appears to be successful to the people at iinet and the IP address etc are assigned it does not work. Neither Netscape nor Eudora can find the server or any other address tried. When iinet tried to 'ping' the address it did not work, ie it is a dead connection. I have looked at the connection log and the ADSL connection is recorded as well as this mornings dial up. Can anyone suggest what is wrong please. That's very difficult without any information on your setup - which modem? How are you connected (ethernet, wireless, is there a LAN involved?) What machine? What OS? What settings are you using? Has someone Mac-clueful in iinet's ADSL support department been over your settings with you? Have you tried a known-working ethernet cable (if it's an ethernet modem)? -- Lara
Re: iinet ADSL Problem
Sorry Lara, I was feeling a bit tired and emotional and forgot to
give the details, no doubt I shall be on Onno's blacklist.
I only asked because iinet's experts have run out of ideas. Their
only other option was to take the Mac in to them and I plain don't
trust them.
G4 Quicksilver 933 MHz, OS 9.2, DSL 300 modem, ethernet, not
connected to the network, Appletalk set on ethernet, all the correct
lights on the Modem.
I suspect it is the TCP/IP setting which is configured to connect
via ethernet using DHCP Server. This brings up a box to insert a DHCP
Client ID but the iinet guys do not know what should go in this box.
They said to leave it blank, we also tried with my user name but that
did not work either. When I was connected all the other addresses
were supplied by the server and appeared to be correct.
iinet talked about my ethernet port not being correctly configured
but as I just unplugged the lead which normally goes to the hub and
connected the lead from the modem I don't think this is the problem.
But I did use their new ethernet lead and not my old one which I know
works.
My heart sank when I saw it was a D-Link modem after what Shay said
about their equipment the other day.
The error messages I got when trying to connect via ADSL were, from Eudora:
Error involving Domain Name System
-3162
The server is not responding
{37:1170}
And from Netscape:
Netscape is unable to locate the server
www.iinet.net.au
Please check the server name and try again.
Using previously cached copy instead.
Once before when I got these messages repeatedly on dial-up I
connected to ATT and was able to access the iinet servers using
Eudora and Netscape. iinet could not explain this phenomenon. Two
days later it resolved.
Diana
Diana Graham Stevens wrote:
The problem is that although the ADSL connection appears to be
successful to the people at iinet and the IP address etc are assigned
it does not work. Neither Netscape nor Eudora can find the server or
any other address tried.
When iinet tried to 'ping' the address it did not work, ie it is a
dead connection. I have looked at the connection log and the ADSL
connection is recorded as well as this mornings dial up.
Can anyone suggest what is wrong please.
That's very difficult without any information on your setup - which
modem? How are you connected (ethernet, wireless, is there a LAN
involved?) What machine? What OS? What settings are you using?
Has someone Mac-clueful in iinet's ADSL support department been over
your settings with you? Have you tried a known-working ethernet cable
(if it's an ethernet modem)?
--
Lara
-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.html
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.html
Unsubscribe - mailto:[EMAIL PROTECTED]
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Re: iinet ADSL Problem
Diana Graham Stevens wrote: I only asked because iinet's experts have run out of ideas. Their only other option was to take the Mac in to them and I plain don't trust them. G4 Quicksilver 933 MHz, OS 9.2, Ah - I might not be able to help you too much then. Is there any reason you're not running OS X? I only ask because iinet support OS X for their Bliink product, and doesn't support OS 9 (so I'm not too surprised that you haven't had much help from them). I've downloaded the config guide for the D-link 300 (which I assume is the modem you've got), and it wasn't much use either. DSL 300 modem, ethernet, not connected to the network, Appletalk set on ethernet, all the correct lights on the Modem. Was this set up by an iinet staffer at your house? Did they test the connection and find it to be working? I suspect it is the TCP/IP setting which is configured to connect via ethernet using DHCP Server. This brings up a box to insert a DHCP Client ID but the iinet guys do not know what should go in this box. Sigh, but a slightly qualified sigh given that you've chosen an OS they don't support. As to whether they should support it, that's a completely different question :-) They said to leave it blank, we also tried with my user name but that did not work either. When I was connected all the other addresses were supplied by the server and appeared to be correct. So it was giving you an IP address? Something is working? iinet talked about my ethernet port not being correctly configured but as I just unplugged the lead which normally goes to the hub and connected the lead from the modem I don't think this is the problem. But I did use their new ethernet lead and not my old one which I know works. Try them both anyway... The error messages I got when trying to connect via ADSL were, from Eudora: Error involving Domain Name System [etc] Can you ping iinet? In case it's just a DNS issue? Failing all this, I guess you have a few options: - get a friendly WAMUGger with an OS X laptop to come over, try the connection and perhaps ring iinet support again with this (supported) machine at hand (I could be free to do this depending on your location). - ask for an iinet on-site visit (this may cost you, I'm not sure). - take the Mac in as they have suggested. - ring iinet support again, preferably during working hours, and just hope to strike someone who knows OS 9 a bit better by random chance. -- Lara
Re: iinet ADSL Problem - non helpful response
On Mon, 2002-07-01 at 22:55, Diana Graham Stevens wrote: no doubt I shall be on Onno's blacklist. For the record, there is no such list, but if you want I'm happy to start one :-) -- ()/)/)() ..ASCII for Onno.. |? ..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno.. ITmaze - ABN: 56 178 057 063 - ph: 04 1219 - [EMAIL PROTECTED]
Re: iinet ADSL Problem
On Mon, 2002-07-01 at 22:55, Diana Graham Stevens wrote:
I suspect it is the TCP/IP setting which is configured to connect
via ethernet using DHCP Server. This brings up a box to insert a DHCP
Client ID but the iinet guys do not know what should go in this box.
They said to leave it blank, we also tried with my user name but that
did not work either. When I was connected all the other addresses
were supplied by the server and appeared to be correct.
Although I now have several independent reports that the majority of
iiNet support staff are clueless, I can only *suggest* that if they
don't know what the DHCP Client ID is for, it is unlikely that they are
using this.
iinet talked about my ethernet port not being correctly configured
but as I just unplugged the lead which normally goes to the hub and
connected the lead from the modem I don't think this is the problem.
But I did use their new ethernet lead and not my old one which I know
works.
*Generally*, if the light comes on when you plug it in it's working, but
to make sure, use your old cable. I have seen situations where the light
comes on, but it still doesn't work - read on.
My heart sank when I saw it was a D-Link modem after what Shay said
about their equipment the other day.
I can back-up his statement about DLink gear is to be steered away
from, since it has cost me serious money last month, when a client
decided that the time it took to find out that the firmware in one of
their new DLink wireless base-stations was not compatible with their
newly supplied DLink wireless PCMCIA cards, was not billable to them :-(
Having said that, I know several reputable suppliers who use DLink gear
all the time and have little issue with it. I've spoken to the Manager
of Technical Support in Australia for DLink and he seems happy to
resolve issues - though I must confess that I did never hear of a
solution for another issue with that same base-station
The error messages I got when trying to connect via ADSL were, from Eudora:
Error involving Domain Name System
-3162
The server is not responding
{37:1170}
And from Netscape:
Netscape is unable to locate the server
www.iinet.net.au
Please check the server name and try again.
Using previously cached copy instead.
OK, here's what's supposed to happen when you do something on the
Internet: (Very simplified for this occasion)
1 - You connect your computer physically to the network.
2 - Your computer puts out a DHCP request.
3 - A response comes back from the network with an IP number and
optionally the DBS details.
4 - Your computer asks the DNS what the number for a name, like
www,iinet.net.au is.
5 - The DNS tells your computer it's: 203.59.24.221
6 - Your computer then opens a connection to the computer at that
address and your web-page appears.
Where it can go wrong:
1 - The physical connection is broken - either between your computer and
the modem, the modem and the wall, the wall and the street, the street
and the exchange, the exchange and the provider, inside the provider.
2 - Your computer is not configured to send out DHCP
3 - The request doesn't come back.
4 - The DNS is broken
5 - The DNS is broken
6 - The proxy server is broken.
You can eliminate some of these:
1 - Check the wires, use known good cables, test the new cable with
known good equipment.
2 - Check that it's set to DHCP, or supply the correct details yourself.
For a fully working IP connection, you need: an IP number, a gateway
address, a subnet mask and a DNS entry. DHCP is a simple way of getting
them all from a central location.
3 - Unlikely to be broken.
4,5 - The DNS number may be wrong, or the DNS may be down. But you don't
need a DNS to send IP information out. Get a hold of a piece of software
called:
IPNetMonitor
http://www.versiontracker.com/moreinfo.fcgi?id=2215db=mac
And try and ping something. I generally use 134.7.134.134, since I
remember it from my days at Curtin, supporting networks all day. This is
the DNS server at Curtin. Its up most of the time, since they know what
they're doing ;-)
If that works then you know that IP traffic is actually working, the
only broken bit is that a name cannot get translated into a number, ie.
the iiNet DNS is down, or their ADSL network uses a different DNS than
their dial-up network.
6 - Turn off the proxy, if it works, the proxy may not. It is also
connected to the net and also needs to have a fully working IP
connection.
Once before when I got these messages repeatedly on dial-up I
connected to ATT and was able to access the iinet servers using
Eudora and Netscape. iinet could not explain this phenomenon. Two
days later it resolved.
When the iiNet domain servers go down, which I'm told happens regularly,
this will happen.
Diana
Diana Graham Stevens wrote:
The problem is that although the ADSL connection appears to be
successful to the people at iinet and the IP address etc are assigned
it does not work.
