Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: carvedeye on January 03, 2017, 09:04:09 PM
-
Hi all, as a lot of you may know already I am having trouble connecting to the internet with my towered 1200 (which is in my siggy) but I am still having no luck. I have tried every tcp/ip that's available like genesis, roadshow, miamidx and of course easynet. But I am stuck at a break wall and I don't know what else to do. I have configured all the correct settings with all the tcp/ip's. i have put in the correct IP the correct gateway dns settings and all i have ping all my systems on the network including the router itself but I am getting 100% packet loss. If anyone could please, please help me get online i would be forever grateful.
-
If you can ping the server, it's down to one of two thing, I guess.
1) TCP-IP stack isn't configured right with a default gateway. Or isn't configured to use the Realtek card for internet access, so is trying to default connect through a serial port.
2) Your browser isn't happy talking to your TCP-IP stack.
Could be something else, but I'd check the default IP address for the gateway... similar thread from a few days ago, I'll dig it out.
EDIT: Here you go.
http://www.amiga.org/forums/showthread.php?t=71771&page=2&highlight=gateway+TCP-IP
-
If none of the available TCP/IP stacks are working, are you certain your network card isn't at fault? Or damaged pins in the PCMCIA port? Are you able to verify that the card and port are both working correctly?
Did it work previously and now is not working, or has it never worked? If it worked before and now is not working, what changed?
-
If none of the available TCP/IP stacks are working, are you certain your network card isn't at fault? Or damaged pins in the PCMCIA port? Are you able to verify that the card and port are both working correctly?
Did it work previously and now is not working, or has it never worked? If it worked before and now is not working, what changed?
i am using a realtek 8139d.
-
well I decided to turn the amiga off and put the network card into another pci slot and now the damn thing wont turn on, I stripped it down just the motherboard and psu and it dead as a dodo :(
-
i am using a realtek 8139d.
That's great, but you didn't address any of the questions I posed, which might have helped troubleshoot the issue. Oh well, good luck! :(
-
well I decided to turn the amiga off and put the network card into another pci slot and now the damn thing wont turn on, I stripped it down just the motherboard and psu and it dead as a dodo :(
Check the power outputs with a multimeter on the PSU - with that setup, you can't possibly be using a standard A1200 PSU.
ATX PSU's have a lot of inbuilt safety features, if they aren't happy with supplies they are giving, they often won't turn on at all.
-
If none of the available TCP/IP stacks are working, are you certain your network card isn't at fault? Or damaged pins in the PCMCIA port? Are you able to verify that the card and port are both working correctly?
Did it work previously and now is not working, or has it never worked? If it worked before and now is not working, what changed?
The card was working before I got the Virgin Hub 3 but the hub is still a dlink router as was my previous hub so it should work with the new one as the DNS and gateway are exactly the same.
There are no damaged pins on the PCMCIA port, The Network card has been tested on my pc and is definitely working.
It worked previously so I have had it working in the past and nothing has changed other than getting the new Virgin Hub.
-
have you changed back to your old. a different router to test ?
Does the Virgin router have some settings that are stopping it connecting ? MAC access control etc ?
-
have you changed back to your old. a different router to test ?
I don't have a spare router to test it.
Does the Virgin router have some settings that are stopping it connecting ? MAC access control etc ?
I can access the routers settings but I wouldn't know where to start when it comes to MAC address.
-
What other systems do you have on your network, and do they get IPv4 addresses? I ask because I know Virgin are using more and more IPv6 these days.
-
What other systems do you have on your network, and do they get IPv4 addresses? I ask because I know Virgin are using more and more IPv6 these days.
All my systems are on IPv4.
-
Would I be better off adding a MAC address rule for my Amiga to my hub?
-
I don't have a spare router to test it.
I can access the routers settings but I wouldn't know where to start when it comes to MAC address.
What happened to the router it replaced ?
-
If everything worked fine before you replaced the router, and now no longer works since changing the router, than your problem is most likely with the router. I'd try swapping back to the old one and see if things start working again before spending a whole bunch of time poking and prodding at settings.
Once you've verified the single source of failure, then you could start checking if it's (a) something in the router blocking the Amiga from connecting, or a setting that needs to be enabled, or (b) something on the Amiga that needs to be updated to allow it to "talk" to the new router. For example a DHCP setting or a static IP assign, etc.
-
Would I be better off adding a MAC address rule for my Amiga to my hub?
Either that or disable MAC address filtering yes. Is it enabled? It shouldn't be by default.
-
First of all, use DHCP instead of fiddling around with static IP addresses. I recommend Roadshow 68k.
-
I never got that siftware (yes siffware) to run either. Not with modern network cards nor plenty of old ones. Maybe its good for wifi and 1200ers?
-
My ques is that your D-Link router allow internet Access only for devices wich get IP address from it, or has added to mac address table.
Try roadshow with DHCP.
-
First of all, use DHCP instead of fiddling around with static IP addresses.
I could never get my A2000 to play nice with a Windows Server running as a DHCP server (it's set up at my office). Am sure it would be fine using a normal consumer-level home router serving DHCP addresses to just a few devices, but in my particular case, I assign a static IP address to my Miggy and be done with it (so it doesn't need to try to pull one from the server).
No real point to this post, just saying that DHCP isn't always the answer. ;)
-
So Mike, so how do you add the static IP to your Amiga, am having the same issue with EasyNet and would love to solve it.
Thanks Brad Hansen
-
So Mike, so how do you add the static IP to your Amiga, am having the same issue with EasyNet and would love to solve it.
I use MiamiDX, but it should be easy enough to just assign an IP address that's within your range, but outside of the DHCP scope, with any TCP/IP software.
For example if your router is configured as 192.168.1.1 and it has the DHCP scope of 192.168.1.2 - 192.168.1.199, set your Amiga to the IP address of 192.168.1.200. Voila, it will be able to talk to everything on the network without conflicting with another device.
-
One possibility is that the old router used (for example) the range 192.168.0.x and the new router uses 192.168.1.x or 192.168.10.x and carvedeye hasn't updated the static ip accordingly. That's one of the reasons for using DHCP.
Edit: or the new router has another gateway ip, for example 192.168.1.254 instead of 192.168.1.1.