Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
The plot thickens. I power cycled my A500 and left the Ethernet cable unplugged. And voila! When I look at the screen above I have a MAC address now. I was able to boot in and connect to the network. However this was just an anomaly this time around. As I now have 0s again after another reboot. Cable connected or not. So I am now convinced there is something with either the XSurf-500 or the ACA500+ itself. When the MAC is populated I can use it, when it is not, no go.
Please advise, thank you.
See image. BTW - Fresh install of WB3.1 and just the AmiTCP produces the same results.
Just a note, I noticed today when looking at the ACA500+ configuration, the tab where it shows that I have an X Surf500 installed, the MAC address is showing all 0s. Is it supposed to be showing the real MAC address here? Because 00:00:00:00:00:00 is not a valid MAC address and that could be an issue. I am currently reloading my config from scratch to eliminate any software issues here.
Power supply: P/NO:312503-01
DSP-A500
I do not see any dates, nor am I aware of it ever being recapped.
BTW - an update on the Mount iComp script, I discovered that the Iconx executable was different on "C" then my backup folder. I believe it was updated when I recently installed WHDLoad. It changes the Iconx file to a newer version which appears to not work with Mount iComp script. Probably others too. I replaced it with the original and the script runs now.
Sorry yes, it is a SanDisk Ultra 16GB CompactFlash Memory Card Speed Up to 50MB/s- SDCFHS-016G-G46 - Less than a year old. I used the ACA500+ OS3.1 wizard to install originally.
The power supply is the original Amiga 500 which unfortunately I do not have in front of me at the moment. I know it's a revision 5 board if that means anything. I will post the model number later today.
Bits flipped? These are two separate issues I can say that for sure. The interesting thing about the connectivity is that when it works it stays working until the next reboot, soft or hard. I thought maybe a MAC address issue on the switch but no amount of resetting anything helps. I just simply need to turn off the Amiga and wait....quite sometime. Oh and although I can't PING out (to anything LAN or internet) from the A500 I can ping it's interface, and I can ping it's interface from anywhere on the network. Bizarre! I don't see that being a PS issue.
As for the Mount iComp script issue, I restored my SYS: volume from a backup and that seems to have fixed it. But what went wrong?? What was missing?
I still have an issue, where if I haven't used the A500 in a while I am able to connect to the network without issue. But if I need to reboot for any reason I can no longer communicate with anything from the A500. I have to wait, it is as if there is some timeout issue.
However, I have new problem. I was using the Mount iComp script to connect my NAS but something has changed. When I run the command I see a dialog box labelled "IconX" and shows the following info.
network: Unknown command
Must be in a command file
Must be in a command file
Must be in a command file
Then I receive the message "Network could not be Started"
I get this now regardless of the connection status. I can be connected and still get this message. I thought maybe my Startup script was changed but restoring it did not help. I also ran the AmiTCP installer again. Same issue. Thoughts?
Yes, the LED is lit. And yes it does light up again when unplugged and plugged in. But there is no doubt that it just stops after certain amount of use. I used it for several hours on the weekend without issue. Then went into a bunch of other programs. I came back to needing network access again and no go. Same issue as stated above. I can ping the interface from the CLI. I can also ping the interface from other devices on the network. But I can't connect to anything from the Amiga. A reboot does not fix it. I have to leave it off for a while. Very strange.....
I am revisiting this because the same issue has come back, but now I am plugged into a switch. At first it was working then a while later I tried to communicate and I couldn't, rebooting did not help. I'm testing further, but it I am wondering if it's losing connection after prolonged use.
Yeah so it appears to have been the bridge a created using a PC. (I didn't have a switch near the Amiga.) However I thought of that first and removed the cable from the bridge and plugged the XSurf directly into the wall and it still didn't go. I tried again a while later and it worked. The only thing I can surmise is that I didn't reboot the Amiga when I switched it back. the first time.
It was working a few months ago, but right now I cannot connect to anything using my X Surf 500. I can ping it's own interface, I can also ping the X Surf 500 from a PC but I cannot ping anything on my network from the Amiga. Weird? What am I missing? Just to be clear, I have tested the gateway, 8.8.8.8, and other PCs that I can ping from other devices.
