I think you should eliminate everything that might possibly cause a
problem - even those things which seem to have worked in the past.
ONE: Power off EVERYTHING and disconnect ALL the Ethernet cables -
labelling them, of course! This includes the printers, network
switches, security cameras, mobile phones - absolutely everything that
might have a network capability.
TWO: The secondhand Plusnet router, what is its make and model number?
And its serial number? I am aware you also have a TPLink TD-W9970 router.
THREE: Connect the secondhand Plusnet router to the incoming broadband
line, and power up. Wait until its lights show that it has sync and a
good internet connection. This may take several minutes.
FOUR: Connect one computer ONLY directly to the router (not via any switches). This should be the one which previously was able to see the status pages in the router. I believe this is the Mini (running OS
10.15.7).
Make sure you use a good Ethernet cable, one with all 8
wires. Connect this cable directly between the computer and the Plusnet router.
Power up this computer.
FIVE: Examine the Plusnet router's status pages. Identify its firmware version and tell us what it is. Bear in mind that - being secondhand -
this is a totally unknown quantity, and may have had some unknown
firmware installed.
SIX: Note the how the line connection is described. If it shows ADSL (or ADSL2, or ADSL2+) then your copper pair goes all the way to the
exchange. If it shows VDSL (or VDSL2, etc) then your copper pair goes
only to a nearby green cabinet and the service may also be known as
FTTC. Your performance figures would suggest you have ADSL.
SEVEN: Note the public IP address that has been issued to the router.
Have you paid Plusnet for a static public IP address? If so is the
correct address shown? If the address is dynamic, tell us what it is.
Please be absolutely sure that you have the correct login name and
password for the Plusnet connection; if it is wrong you might be issued
with a strange IP address on a closed network which won't give you
access to the internet.
EIGHT: Find the page in the router with the WiFi settings, and DISABLE
THE WIFI. This is so that you are not confused by any unexpected
wireless clients trying to connect.
NINE: Get your computer to tell you its Ethernet settings. Googling
tells me that this is possible on OS 10.15.7 - choose Apple menu >
System Settings, click Network in the sidebar, then click an Ethernet service. (You may need to scroll down.) I don't have a Mac here to
refer to, but others will tell you how to navigate these settings to
find IP address, subnet mask, DNS, default gateway, etc. Report what
you find.
Stop there for the moment. I will work out what to ask next in the
light of your responses.
Make sure you use a good Ethernet cable, one with all 8
wires. Connect this cable directly between the computer and the Plusnet
router.
They are in different parts of the house, so I have had to use the
underfloor Ethernet circuits which terminate in a wall socket in each
room. Each item is joined to the relevant socket with a shortish
male-male cable. The circuits have never given any trouble and I have
no reason to suspect them now.
SEVEN: Note the public IP address that has been issued to the router.
Have you paid Plusnet for a static public IP address? If so is the
correct address shown? If the address is dynamic, tell us what it is.
Please be absolutely sure that you have the correct login name and
password for the Plusnet connection; if it is wrong you might be issued
with a strange IP address on a closed network which won't give you
access to the internet.
Couldn't find anything with that name
but a temporary Username and
Password was there after a factory reset.
I changed these to my own
Username and Password and it logged in OK.
"Ethernet is currently active and has the IP Address: 192.168.1.104
Subnet mask: 225.225.225.0
Router: 192.168.1.254
...also greyed-out DNS Server: 192.168.1.254
I went a bit further and found the Mini was now receiving webpages from
the internet, so I plugged the switches back in and it still worked.
Then I switched on the G3, the Mini still worked but the G3 wouldn't
connect. I have had to put back the TPLink router to send this reply
(and the Mini is still working at the moment).
Liz Tuddenham wrote:
[snip]
Make sure you use a good Ethernet cable, one with all 8
wires. Connect this cable directly between the computer and the Plusnet >> router.
They are in different parts of the house, so I have had to use the underfloor Ethernet circuits which terminate in a wall socket in each
room. Each item is joined to the relevant socket with a shortish
male-male cable. The circuits have never given any trouble and I have
no reason to suspect them now.
I understand your reasoning, and your later info suggests that the
wiring is not a problem. But it would be nice to know: is there some
reason why you cannot carry the Mini to the router? Are you for example wheelchair-bound?
SEVEN: Note the public IP address that has been issued to the router.
Have you paid Plusnet for a static public IP address? If so is the
correct address shown? If the address is dynamic, tell us what it is.
Please be absolutely sure that you have the correct login name and
password for the Plusnet connection; if it is wrong you might be issued
with a strange IP address on a closed network which won't give you
access to the internet.
Couldn't find anything with that name
Don't understand. Do you mean you cannot find its public IP address?
I've tried to find a manual for your SAGECOM 2704N but can't. So I
can't tell you where to find this information.
Why did you buy this router?
[snip]
So the question is why the Mini did not see web pages when you had it connected previously. Given that is was connected via switches it would
have been essential to power it off then on to force it to send its DHCP request to a different router. So when changing a router, always power
off all the client computers.
It's possible that one of the network switches is faulty. Or you have
more than one cable connecting between two network switches - look up Spanning Tree Protocol. So you MUST test without the switches.
Please arrange to connect the Mini and later the G3 directly to the
router each with its own Ethernet cable. You might have to buy some
long cables (but Ethernet is specified for 100 metres) or move the
computers - see above.
What OS is running on the G3 please?
With the mini connected and working connect the G3 and look at the RJ45 sockets on the router and the G3. There are usually LEDs showing
connection and speed. What do they indicate for the port on the router
that connects to the G3, and on the G3 itself?
Does the SAGECOM 2704N router show anything about the connection to the
G3? If so, what?
---
Going back, why did you buy the SAGECOM 2704N router? What did you
suspect was wrong with your TPLink TD-W9970 router?
Couldn't find anything with that name
Don't understand. Do you mean you cannot find its public IP address?
I cannot find anything called "Public IP address", it may be there under another name.
That is probably the reason the Mini didn't work at first, but then it
did when started from cold*. It doesn't explain what is going on with
the G3, but I suspect the TPLink was set up by my friend to connect with
the G3 through a fixed address and the Plusnet router isn't - and I am
not confident enough to try to do that myself without any diagnostic
tools.
If I plug a MacBook into one of the Ethernet sockets on the router, the MacBook connects to the web but it doesn't show up in the router's "Home Network" panel.
If I could tell them it was a Plusnet router and let them take me
through the settings and prove to their satisfaction that it was working properly, they would be forced to treat my complaint seriously.
Don't understand. Do you mean you cannot find its public IP address?
I've tried to find a manual for your SAGECOM 2704N but can't. So I
can't tell you where to find this information.
Liz Tuddenham wrote:[...]
[snip]
Now I think your SAGECOM 2704N should have a similar page where you can
see these parameters.
[snip]
The default IP address of the TD-W9970 is 192.168.1.1 whereas the
default address of the SAGECOM 2704N router is 192.168.1.254. This is
why you should ALWAYS use DHCP (i.e. Automatic) for all your computers
unless you know EXACTLY what you are doing. That way the router will
tell the computer how to communicate with the router and hence with the outside world.
You should do the same for the printers, using the features of the
router (if they exist) to fix their addresses.
The two different router IP addresses and the lack of DHCP explain why
you have had problems.
[snip]
We might have eliminated any potential problem with the network switches.
[snip]
If I plug a MacBook into one of the Ethernet sockets on the router, the MacBook connects to the web but it doesn't show up in the router's "Home Network" panel.
It may be necessary to reboot the router to get it to show this.
[snip]
... On each printer, identify the
mechanism for the printer to tell you its IP settings.
Tell us how you get on ...
On 29. Oct 2024 at 18:54:17 CET, "Graham J" <nobody@nowhere.co.uk> wrote:
Don't understand. Do you mean you cannot find its public IP address?
I've tried to find a manual for your SAGECOM 2704N but can't. So I
can't tell you where to find this information.
You can use <https://www.whatismyip.com/> (or a similar service) to get
that information.
... On each printer, identify the
mechanism for the printer to tell you its IP settings.
There isn't one that is accessible without a lot of digging around - and
then only with a Windows machine. That is why my friend had so much
trouble setting up the network in the first place. It took him a whole afternoon and he had to download special software to get any information
out of the printers.
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 29. Oct 2024 at 18:54:17 CET, "Graham J" <nobody@nowhere.co.uk> wrote:
Don't understand. Do you mean you cannot find its public IP address?
I've tried to find a manual for your SAGECOM 2704N but can't. So I
can't tell you where to find this information.
You can use <https://www.whatismyip.com/> (or a similar service) to get
that information.
Thanks, that gives:
TPLink: 51.6.168.71
Plusnet: 91.125.75.32
On 30 Oct 2024 at 10:22:30 GMT, "Liz Tuddenham" <Liz Tuddenham> wrote:
... On each printer, identify the
mechanism for the printer to tell you its IP settings.
There isn't one that is accessible without a lot of digging around - and then only with a Windows machine. That is why my friend had so much trouble setting up the network in the first place. It took him a whole afternoon and he had to download special software to get any information out of the printers.
If I type the local IP address (192.168.1.4) of our printer into a web browser, then the printer serves up a web page at which I can see its settings, do maintenance stuff etc.
Does yours have this possibility?
The default IP address of the TD-W9970 is 192.168.1.1 whereas the
default address of the SAGECOM 2704N router is 192.168.1.254. This is
why you should ALWAYS use DHCP (i.e. Automatic) for all your computers
unless you know EXACTLY what you are doing. That way the router will
tell the computer how to communicate with the router and hence with the
outside world.
I've created a new IP Configuration on the G3 with DHCP set to automatic
and the Client set to 192.169.1.254
When I switched to that
Configuration the G3 could contact the internet. The G3 was able to
contact both printers (HP LaserJet 6MP and Canon CLPG460ps) before I
changed the Configuration and it still contacts them after the change.
The "My Home Network" panel on the Plusnet router page now shows a new un-named device, which disappears when the G3 is switched off. No
printers show up at all.
You should do the same for the printers, using the features of the
router (if they exist) to fix their addresses.
The features don't appear to exist on the Plusnet router (but they do on
the TPLink router and were set up by my friend, with great difficulty).
If I plug a MacBook into one of the Ethernet sockets on the router, the
MacBook connects to the web but it doesn't show up in the router's "Home >>> Network" panel.
It may be necessary to reboot the router to get it to show this.
It has a 'Refresh' button, but that doesn't make any difference as far
as the MacBook is concerned. I would imagine it is manually configured
in the same way the G3 was, so if I really needed to use it on the
Plusnet router I would have to re-configure it.
... On each printer, identify the
mechanism for the printer to tell you its IP settings.
The G3 can now see the internet and both printers, but the router only
shows the Mini reliably and the G3 sometimes (it vanishes from the
listing if it doesn't use the internet for a while).
The Mini can't see
either printer or the G3. I have no idea how to re-configure the
printers
I am now in a position to switch to the Pluslink router the next time I
get a website blockage and then tackle Plusnet about it.
[By the way, I've tried to access the Plusnet router with the G3, its
webpage crashes iCab but works OK with Classilla]
On 30 Oct 2024 at 10:22:30 GMT, "Liz Tuddenham" <Liz Tuddenham> wrote:
... On each printer, identify the
mechanism for the printer to tell you its IP settings.
There isn't one that is accessible without a lot of digging around - and then only with a Windows machine. That is why my friend had so much trouble setting up the network in the first place. It took him a whole afternoon and he had to download special software to get any information out of the printers.
If I type the local IP address (192.168.1.4) of our printer into a web browser, then the printer serves up a web page at which I can see its settings, do maintenance stuff etc.
Does yours have this possibility?
Liz Tuddenham wrote:
[snip]
...192.169.1.254
That looks meaningless, I think you have a typo.
With the G3 set to DHCP you should not need to set anything else. Once connected with the router that screen may show some values. I would
expect its own IP address 192.168.1.<something> and entries for Default Gateway and DNS both pointing to the router 192.168.1.254.
It's quite possible that the printers don't use TCP/IP for communicating
with the Apple computers.
Investigate to confirm whether after power off/on of the printers and
SAGECOM 2704N router the printers have the same IP addresses. Make a
note of them for future reference. But as I suggest above, their IP addresses may not be relevant for printing from Apples.
[snip]
I thought you said the Macbook could see the internet via the SAGECOM
2704N router? If so it must have a suitable IP address, DNS and default gateway settings, which would imply is is configured with DHCP. Given
that it is a laptop and therefore portable, and you might want to use it elsewhere, it really is essential that it uses DHCP.
Are you sure it
was connecting via Ethernet and not WiFi? Possibly to your neighbour's
WiFi router?
... On each printer, identify the
mechanism for the printer to tell you its IP settings.
Most will print out a configuration page.
The G3 can now see the internet and both printers, but the router only shows the Mini reliably and the G3 sometimes (it vanishes from the
listing if it doesn't use the internet for a while).
Has the G3 gone to sleep?
Can the Mini ping the G3?
BUT given the difficulties you have with the SAGECOM 2704N router I
suggest you keep it in place and get everything working with it (I
accept that this may hurt your brain) so that when you suspect a Plusnet problem you are not struggling to get your system working first.
It seemed to need the IP of the router, after that it set up everything
else automatically.
I think it (Macbook) has a manually-set fixed address
Can the Mini ping the G3?
How do I do that?
That is the general idea. Most of the system is now working as well on
the Plusnet router as it was on the TPLink, so it is good enough to get
me through when I need to use it.
The Canon has a menu which allows the IP address to be set manually.
There is no automatic option. With no manual option in the Plusnet
router, that router cannt see it - but the G3 connects to it all right.
I don't have a clue how to connect the Mini to it.
Liz Tuddenham wrote:
[snip]
It seemed to need the IP of the router, after that it set up everything
else automatically.
Very strange! But maybe the G3 and OS 8.6 don't implement DHCP properly.
TimS <tim@streater.me.uk> wrote:
On 30 Oct 2024 at 10:22:30 GMT, "Liz Tuddenham" <Liz Tuddenham> wrote:
... On each printer, identify the
mechanism for the printer to tell you its IP settings.
There isn't one that is accessible without a lot of digging around - and then only with a Windows machine. That is why my friend had so much trouble setting up the network in the first place. It took him a whole afternoon and he had to download special software to get any information out of the printers.
If I type the local IP address (192.168.1.4) of our printer into a web browser, then the printer serves up a web page at which I can see its settings, do maintenance stuff etc.
Does yours have this possibility?
Not as far as I know. The LaserJet 6mp pre-dates that sort of thing and
is running through an Apple mini-DIN cable and an Asanté adaptor to the Ethernet. If I had the IP address, it would only get me as far as the adaptor.
If you know the IP address, you could try this:
echo -e "hello world\r\n\f" | nc 192.168.1.4 9100
it may print a page with 'hello world' on it.
(assuming it supports Jetdirect and text-mode, which I think those 1990s
do)
If it doesn't print, you still may see it wake up from sleep.
On 30 Oct 2024 at 17:20:36 GMT, "Theo" <theom+news@chiark.greenend.org.uk> wrote:
If you know the IP address, you could try this:
echo -e "hello world\r\n\f" | nc 192.168.1.4 9100
it may print a page with 'hello world' on it.
(assuming it supports Jetdirect and text-mode, which I think those 1990s do)
If it doesn't print, you still may see it wake up from sleep.
Here, that just hung (^C to exit) until the printer was powered on when the command completed but was ignored by this Canon G6050. Subsequently with the printer on the command completed immediately but was still ignored. FWIW.
No, my point is to use it ALL THE TIME, so you never have to worry about getting the configuration right when you need to challenge Plusnet about something. It saves brain power in the long run.
Graham J wrote:
[snip]
No, my point is to use it ALL THE TIME, so you never have to worry about getting the configuration right when you need to challenge Plusnet about something. It saves brain power in the long run.
I will be away for a couple of days with no internet access (yes, such
places do exist!) So bear with me if you ask a question and I don't reply.
Sorry to resurrect this thread but things have started happening again.
A few days ago my TP-Link router refused to connect to the Web so I ran diagnostics and discovered:
Ping default gateway - Fail
Ping Primary Domain Name Server - Fail
Test DNS Root - Fail
Network Connection Status Inspect - Fail
I rebooted the router and the first two remained at "Fail"
but the last
two showed "Pass" and Web browsing returned.
I tried the
<poppyrecords.co.uk> website and that appeared OK.
I then tried to upload a file to the web server but Fetch refused to establish an FTP connection.
It has been like this for several days.
My website host says:
" Done a couple of tests - no fault found. However, I rarely use ftp.
I either deploy from git (for big sites) or use the control panel file transfer which is a different instance of the ftp server than you use."
Which isn't much help to me.
What tests should I do to establish the cause while the fault persists?
It has a habit of going on like this for about a week and then suddenly correcting itself.
Liz Tuddenham wrote:[...]
What did the router tell you about the upstream and downstream sync speeds?
Did the router show that it had a WAN IP address? This would confirm
that it was authenticated with Plusnet.
Either or both of these failing would lead to the following results:
Ping default gateway - Fail
Ping Primary Domain Name Server - Fail
Test DNS Root - Fail
Network Connection Status Inspect - Fail
No idea what this last item means. Does your router explain this anywhere?
I rebooted the router and the first two remained at "Fail"
These would suggest that the router is not connected to Plusnet. Did
you provide the IP addresses for the gateway and DNS? Or a name of some sort?
but the last
two showed "Pass" and Web browsing returned.
So this is inconsistent. If the first two fail, then I would not expect
you to be able to browse the web. Something else is going wrong. I
would suspect that the router is failing intermittently. Is this
TP-Link router the one recently provided to you by Plusnet?
If not, what happens when you use the Plusnet-supplied router?
I tried the
<poppyrecords.co.uk> website and that appeared OK.
I then tried to upload a file to the web server but Fetch refused to establish an FTP connection.
I've no idea what "Fetch" is, but does it give any explanation for its failure to establish a connection?
A decent website hosting service should be able to monitor your
connection attempt and identify exactly what is going wrong.
What tests should I do to establish the cause while the fault persists?
It has a habit of going on like this for about a week and then suddenly correcting itself.
Do you have an alternative FTP client that you can try?
Do you have an alternative FTP server that you can connect to? I think
your account with Plusnet should give you access to theirs, see: <https://www.plus.net/help/broadband/about-your-plusnet-webspace/>
Have you any computer which will run wireshark or a similar network
analysis program? That could tell you why FTP fails.
If you have Telnet you could try sending commands to the FTP server to
see how it responds.
Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
Sorry to resurrect this thread but things have started happening again.
A few days ago my TP-Link router refused to connect to the Web so I ran diagnostics and discovered:
Pimg default gateway - Fail
Ping Primary Domain Name Server - Fail
Test DNS Root - Fail
Network Connection Status Inspect - Fail
I rebooted the router and the first two remained at "Fail" but the last
two showed "Pass" and Web browsing returned. I tried the <poppyrecords.co.uk> website and that appeared OK.
I then tried to uppload a file to the web server but Fetch refused to establish an FTP connection. It has been like this for several days.
My website host says:
" Done a couple of tests - no fault found. However, I rarely use ftp.
I either deploy from git (for big sites) or use the control panel file transfer which is a different instance of the ftp server than you use."
ftp is deprecated by many places because it is insecure. Can you use sftp instead?
There is a table under "Network > WAN interface which includes:meaming Point to Point Protocol over Ethernet
Name: pppoe_0_38_1_d
Type: PPoE
VPI/VCI orVID: 0/38A code to make your DSL connection function correctly
IPvX: IPv4This is your public IP address, as issued by Plusnet. The /32 is the
IP/Mask: 51.6.168.38/32
Gateway: 172.16.15.137This is a router in a private address range (see RFC1918) that your
DNS: 212.159.13.49A Plusnet DNS server
2122.159.6.9Actually 212.159.6.9 = another Plusnet DNS server
Status: ConnectedThis confirms that you are connected to Plusnet and hence (hopefully) to
Is this where I should look in the event of a future disconnection?This is the second place to look. The first place is the up/down sync
No, but it 'helpfully' gives the abbreviation "NCSI".F---ing Magic!!
I rebooted the router and the first two remained at "Fail"
These would suggest that the router is not connected to Plusnet. Did
you provide the IP addresses for the gateway and DNS? Or a name of some
sort?
Not that I remember.
If not, what happens when you use the Plusnet-supplied router?
I didn't try it at the time. i have tried it now and FTP still doesn't
work.
I've downloaded Zenmap, but can't get it to work.
If you have Telnet you could try sending commands to the FTP server to
see how it responds.
I have Telnet 1.1 SSHr3 on the G3, but it isn't set up for any of my
current routers. It may take me a while to do this.
DNS: 212.159.13.49
2122.159.6.9
On 25. Nov 2024 at 20:58:41 CET, "Liz Tuddenham" <Liz Tuddenham> wrote:
DNS: 212.159.13.49
2122.159.6.9
I guess the 2122 is a typo?
There is a saying:
-It’s not DNS
-There’s no way its DNS
-It was DNS
First thing I try when something goes wrong with the internet:
use Googles and Cloudflares DNS-Servers.
Goto Network settings on your computer, there is an option to manually configure the DNS servers.
First thing I try when something goes wrong with the internet:
use Googles and Cloudflares DNS-Servers.
Goto Network settings on your computer, there is an option to manually
configure the DNS servers.
I presume you are thinking of OSX and the Mini, because there is nothing called '"Network Settings" in OS 8.6. ...but there is no FTP on the
Mini, so I can't test it.
Liz Tuddenham wrote:
[snip]
First thing I try when something goes wrong with the internet:
use Googles and Cloudflares DNS-Servers.
Goto Network settings on your computer, there is an option to manually
configure the DNS servers.
I presume you are thinking of OSX and the Mini, because there is nothing called '"Network Settings" in OS 8.6. ...but there is no FTP on the
Mini, so I can't test it.
Most routers allow you to specify the DNS server(s) that the router will allocate to its clients when they make their DHCP requests.
But given that (for the moment, while testing) you have to use the
crippled device provided by Plusnet, and your client Macs appear not to
know how to use DHCP, you're a bit stuffed.
On 26. Nov 2024 at 09:26:43 CET, "Liz Tuddenham" <Liz Tuddenham> wrote:
because there is nothing
called '"Network Settings" in OS 8.6.
Ah, I used that a loooong time ago :-)
There should be a "TCP/IP" control panel.
Have a look in there if you can configure the DNS servers.
...but there is no FTP on the
Mini, so I can't test it.
On the mini you could try Filezilla for FTP.
<https://filezilla-project.org/>
because there is nothing
called '"Network Settings" in OS 8.6.
...but there is no FTP on the
Mini, so I can't test it.
On 26. Nov 2024 at 10:11:00 CET, "Liz Tuddenham" <Liz Tuddenham> wrote:
I'll look into that, but the OS of the Mini (10.15.7) doesn't have any
FTP support. (Apparently it can be bought-in from Apple, but I haven't
found out how to do that yet)
Filezilla "Requires macOS 10.13.2 or newer" so you should be good.
Don´t bother with Apples FTP-Support.
I'll look into that, but the OS of the Mini (10.15.7) doesn't have any
FTP support. (Apparently it can be bought-in from Apple, but I haven't
found out how to do that yet)
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 25. Nov 2024 at 20:58:41 CET, "Liz Tuddenham" <Liz Tuddenham> wrote:
DNS: 212.159.13.49
2122.159.6.9
I guess the 2122 is a typo?
Yes
There is a saying:
-It’s not DNS
-There’s no way its DNS
-It was DNS
That was my previous experience.
First thing I try when something goes wrong with the internet:
use Googles and Cloudflares DNS-Servers.
Goto Network settings on your computer, there is an option to manually
configure the DNS servers.
I presume you are thinking of OSX and the Mini, because there is nothing called '"Network Settings" in OS 8.6. ...but there is no FTP on the
Mini, so I can't test it.
I'll look into that, but the OS of the Mini (10.15.7) doesn't have any
FTP support. (Apparently it can be bought-in from Apple, but I haven't
found out how to do that yet)
On 26 Nov 2024 at 09:11:00 GMT, "Liz Tuddenham" <Liz Tuddenham> wrote:
I'll look into that, but the OS of the Mini (10.15.7) doesn't have any
FTP support. (Apparently it can be bought-in from Apple, but I haven't found out how to do that yet)
Just install an FTP client (such as CyberDuck).
TimS <tim@streater.me.uk> wrote:
On 26 Nov 2024 at 09:11:00 GMT, "Liz Tuddenham" <Liz Tuddenham> wrote:
I'll look into that, but the OS of the Mini (10.15.7) doesn't have any
FTP support. (Apparently it can be bought-in from Apple, but I haven't
found out how to do that yet)
Just install an FTP client (such as CyberDuck).
Did that on the Mini and tried to contact the server - it says the
server is rejecting it (similar to Fetch on the G3). By then, the poppyrecords website had disappeared too, so I rang Richard (Waveney
Web Services who host the website) got him to check that everything
appeared normal at that end.
I had been using the Plusnet router, so I rang Plusnet. They rang me
back after about 5 minutes and got me to try it again, the website had
come back but FTP still didn't work. They advised me that if I got that problem with the website again, disconnect the router and wait at least
5 minutes, so that it picks up a different IP address on restart - the
IP was the cause of that problem.
They don't know what is causing the FTP problem and will ring me back on Monday to try to sort it out.
They don't know what is causing the FTP problem and will ring me back on Monday to try to sort it out.
But given that (for the moment, while testing) you have to use the
crippled device provided by Plusnet, and your client Macs appear not to
know how to use DHCP, you're a bit stuffed.
On 26/11/2024 08:38, Graham J wrote:
But given that (for the moment, while testing) you have to use the
crippled device provided by Plusnet, and your client Macs appear not
to know how to use DHCP, you're a bit stuffed.
Wait, what? Even classic MacOS could use DHCP. There's lots of detailed information at http://www.applefool.com/se30/
Chris Ridd wrote:
On 26/11/2024 08:38, Graham J wrote:
But given that (for the moment, while testing) you have to use the
crippled device provided by Plusnet, and your client Macs appear not
to know how to use DHCP, you're a bit stuffed.
Wait, what? Even classic MacOS could use DHCP. There's lots of
detailed information at http://www.applefool.com/se30/
At last! Somebody who knows a bit about Apple networking on old Macs!
Perhaps you can review this thread and explain to Liz how she should configure her legacy Macs to use DHCP?
Given the state of Liz's computers I'm not sure she will be able to view
the pages at the link you've given.
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 29. Oct 2024 at 18:54:17 CET, "Graham J" <nobody@nowhere.co.uk> wrote:
Don't understand. Do you mean you cannot find its public IP address?
I've tried to find a manual for your SAGECOM 2704N but can't. So I
can't tell you where to find this information.
You can use <https://www.whatismyip.com/> (or a similar service) to get
that information.
Thanks, that gives:
TPLink: 51.6.168.71
Plusnet: 91.125.75.32
You can use <https://www.whatismyip.com/> (or a similar service) to get
that information.
Thanks, that gives:
TPLink: 51.6.168.71
Plusnet: 91.125.75.32
On 30/10/2024 10:22, Liz Tuddenham wrote:
Bernd Froehlich <befr@eaglesoft.de> wrote:
On 29. Oct 2024 at 18:54:17 CET, "Graham J" <nobody@nowhere.co.uk> wrote: >>
Don't understand. Do you mean you cannot find its public IP address?
I've tried to find a manual for your SAGECOM 2704N but can't. So I
can't tell you where to find this information.
You can use <https://www.whatismyip.com/> (or a similar service) to get
that information.
Thanks, that gives:
TPLink: 51.6.168.71
Plusnet: 91.125.75.32
I used to use one of those PlusNet SageCom 2704N routers.
There is a secret expert menu which you access by logging into it using http://192.168.1.254/expert_user.html with the admin name and password.
Sorry I haven't replied to the other various helpful suggestions, but I simply haven't had time and dare'nt change anything until the rush for artwork and printing for Christmas is over. Just keeping the existing network and printer running has had to take priority.
Sorry I haven't replied to the other various helpful suggestiions, but I simply haven't had time and daren't change anything until the rush for artwork and printing for Christmas is over. Just keeping the existing network and printer running has had to take priority.
Sorry I haven't replied to the other various helpful suggestiions, but I simply haven't had time and daren't change anything until the rush for artwork and printing for Christmas is over. Just keeping the existing network and printer running has had to take priority.
On 06/12/2024 09:07, Liz Tuddenham wrote:
Sorry I haven't replied to the other various helpful suggestiions, but I simply haven't had time and daren't change anything until the rush for artwork and printing for Christmas is over. Just keeping the existing network and printer running has had to take priority.
Did you manage to dig any further into your networking configuration, Liz?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 10:26:45 |
| Calls: | 10,389 |
| Calls today: | 4 |
| Files: | 14,061 |
| Messages: | 6,416,854 |
| Posted today: | 1 |