I need help getting my A4000 online

  • Thread starter Thread starter RMK
  • Start date Start date
  • Replies Replies 19
  • Views Views 3750

RMK

Member
AmiBayer
Joined
Jun 5, 2008
Posts
76
Country
UK
Region
Glasgow
Hi guys,

I'm back to messing around with my A4000 project and am currently trying to get it online via my Deneb, Easynet and Amigakit's USB to Ethernet adapter all through a DLink router on Virgin.

So far the USB Ethernet is setup as per recent discussions with Amigakit and from a bit of to-and-frowing it looks like it's the settings of the router that are the issue. When I enter a website in Aweb eg. www.amigakit.co.uk I get the following mesage:

FORBIDDEN you dont have permission to access/on this server. Apache server at www.amigakit.co.uk Port 80.

Can someone dive me some ideas as I'm struggling trying to get my head round all the network settings.

Thanks,

Robert
 
Robert,

I'm struggling with my USB Ethernet from AmigaKit as well :Doh:

Any tips you wanna throw in my direction are welcome :thumbsup:

Good luck and I'll be keeping an eye on the thread.

Dave G :cool:
 
I never had much luck with USB-Ethernet, it always dropped connection. I tested a powered Hub, it seemed to help at first but then kept dropping.

(Thats when I even managed to get online)

In the end I just went back to my trusty X-Surf, I can leave it online for hours at a time, no issues :cool:
 
Dave,

I was going wrong from the start and had to upgrade Posiden to V4.4 and then I'm using dm9601eth.device to get it to do something. Do you get any message in your browser?

Steve,

Unfortunatley I don't have an X-Surf and thought that the USB soulution would be ideal since I already have the Deneb. Hmmm.

Amigakit have confirmed that the settings are correct and the Amiga is connecting and to check the NAT and firewall settings (in the router I presume?). I've attached a pic of the firewall rules in the router if it makes sense to anyone? The Amiga is on ip 192.168.0.10 and the router is 192.168.0.1 Interfaces, port rages etc are completley beyond me.




Cheers,

Robert


UPDATE

For some reason I can load up www.yahoo.com. From there I have managed to search for Amibay and managed to load up the mobile version of the site. Tried EAB mobile but that did not work...
 
Last edited:
Robert,

Yes it seems funny that you have to update the supplied proggy before you can do anything :oops:

I also had to get V4.4 before I could get the dm9601eth.device

I did have a play for a couple of hours and then ran out of time with fixing my daughters laptop and doing some video jobs.

I'll have another go tomorrow and see what happens.

Dave G :cool:
 
Dave,

Keep me poted on how you get on. I'm calling it a night but will give it another bash on Tuesday night.

Robert
 
I've just had a quick mess and managed to ping my router :thumbsup:

I'll see if I can get on the new fangled world wide web tomorrow night :whistle:

Dave G :cool:
 
I've got USB Ethernet working fine for my A4000T using a DENEB and the Genesis TCP/IP stack. I also have EasyNet from AmigaKit and used that for my A1200 wireless connector without trouble.

I can post through the steps that I used to get it online, the only tricky thing I remember was finding the device name for the USB Ethernet card, something like rl840.device or something similar. There is no device file, it's basically created in memory but you need to type in the correct name in the Genesis options screen.

I have my A4000T connected into my router and I have assigned it a static IP, I could not get it working with a dynamic IP. Genesis was pretty simple to setup, pretty much just fill in the right TCP/IP address for your Amiga and router along with the details of my DNS server etc., and all was good.

I've never had any drop outs or disconnections.

Cheers

Mark
 
I'm wondering if it's maybe an Aweb issue with me as I've tried everything I can think of and getting no further - was up till 5 am the other night working on this and then had to call it a night due to work at 9! :blink:

Dave, are you any further forward with yours?
 
Amigakit have confirmed that the settings are correct and the Amiga is connecting and to check the NAT and firewall settings (in the router I presume?). I've attached a pic of the firewall rules in the router if it makes sense to anyone? The Amiga is on ip 192.168.0.10 and the router is 192.168.0.1 Interfaces, port rages etc are completley beyond me.

Well I don't know anything about how to network an Amiga, specifically, but I can say that firewall rule won't be helping, and may be causing some of your problems.

What you've asked for there is for all packets originating from the Amiga to have their final destination address changed to be that of the router. That's not what you want. You want the router to *forward* those packets to their final destination, which it should be doing by default - that's its job.

Have you configured the Amiga with a static IP address (192.168.0.10) or has the router assigned that address via DHCP?

I can't tell you where to look for these settings, but you need to make sure, on the Amiga, that the "gateway" is set to 192.168.0.1, and that the DNS servers are set correctly. Most routers will happily handle DNS on your behalf so you can probably set the DNS server (might be called nameserver) to 192.168.0.1 as well.

Having done that, the best diagnosis method is to use a "ping" program - no idea whether you'll already have one for the Amiga or how to find one if you haven't - but assuming you have, try this:

ping 192.168.0.1
(the router should respond)
ping 209.85.147.106
(That's the address I get if I ping www.google.com
finally
ping www.google.com
(To see if name resolution's working.)

Also from another computer on the network try:
ping 192.168.0.10
(Can other computers ping the Amiga?)

Post your results and we'll have more clues to work from.
 
Well I don't know anything about how to network an Amiga, specifically, but I can say that firewall rule won't be helping, and may be causing some of your problems.

What you've asked for there is for all packets originating from the Amiga to have their final destination address changed to be that of the router. That's not what you want. You want the router to *forward* those packets to their final destination, which it should be doing by default - that's its job.

I've removed it now. :)


Have you configured the Amiga with a static IP address (192.168.0.10) or has the router assigned that address via DHCP?

The Amiga has a static IP address pf 192.168.0.10 When I look at the list of machines connected to the router it lists every other machine except for the Amiga.

On the router DHCP server is enabled with DHCP IP address range of 100 to 199 (I never entered this, it was preset). The other 4 machines connected up have been issued IP's 192.168.0.100, 101, 102 & 103.



I can't tell you where to look for these settings, but you need to make sure, on the Amiga, that the "gateway" is set to 192.168.0.1, and that the DNS servers are set correctly. Most routers will happily handle DNS on your behalf so you can probably set the DNS server (might be called nameserver) to 192.168.0.1 as well.

I can confirm that is correct, 192.168.0.1 and the DNS setings in Easynet match those in the router.


Having done that, the best diagnosis method is to use a "ping" program - no idea whether you'll already have one for the Amiga or how to find one if you haven't - but assuming you have, try this:

ping 192.168.0.1
(the router should respond)
ping 209.85.147.106
(That's the address I get if I ping www.google.com
finally
ping www.google.com
(To see if name resolution's working.)

Also from another computer on the network try:
ping 192.168.0.10
(Can other computers ping the Amiga?)


Typing 192.168.0.1 into Aweb on the Amiga brings up the routers login page, just as it does on the PC.

Typing in 209.85.147.106 takes me to Google (if I type something into the box and hit search I get the message "Cannot connect to www.google.com.virgin.net"

If I type in www.google.com into Aweb I get the message "FORBIDDEN you dont have permission to access/on this server. Apache server at www.google.com Port 80"

If I try to ping the Amiga from the PC internet explorer just takes me to the Bing! search engine so I'm guessing it can't see the Amiga.

I'm wondering if bloody Easynet is the problem as everything looks to match at both ends :help:
 
Try MiamiDX, it's very easy to setup via the Wizard and the version supplied with the Classic Workbench packs includes full reg key.

I'm using it on all my Amiga's without any issues :thumbsup:
 
@robinsonb5 LOL I should read thread names more often.

This is for RMK and not robinsonb5 - apologies

I've just got mine working tonight :oops:

I was going to be clever and put this reply up with my Miggy but it's that :censored: slow I gave up.

Have you updated Easynet?

My settings are

Amiga's IP Address 192.168.1.10 Amiga's Host Name amiga

Network Mask 255.255.255.0 Network Domain Name btbroadband.com

Gateway IP Address 192.168.1.1 DNS Addresses Primary 217.32.145.5

Secondary 192.168.1.1 which is the one Easynet is using

@fitzy

What browser are you using matey? I'm trying Aweb with all graphics turned off and it's like watching paint dry :thumbsdown:

Dave G :cool:
 
Last edited:
Hi Dave!

I'm using IBrowse on my Classic Miggy's, but don't expect a fun experience on modern Websites :lol:

I use the Amibay/EAB Mobile sites and Aminet also BBC News/Sport Mobile sites. These run nice and fast on my 060 and 040 setups but as expected no frills.

I also use WookieChat which is an awesome IRC client and chat with my AmiFriends online :cool:

All the best,
Steve.
 
Typing 192.168.0.1 into Aweb on the Amiga brings up the routers login page, just as it does on the PC.

OK good - so the basic TCP/IP settings and subnet are working OK.

Typing in 209.85.147.106 takes me to Google
OK good - so basic routing is working correctly.

(if I type something into the box and hit search I get the message "Cannot connect to www.google.com.virgin.net"
Now that's just bizarre. Where on earth did that virgin.net come from? You don't have that entered anywhere in the Easynet settings do you? If so remove it. Also if you entered anything to do with proxies, remove that too.

If I try to ping the Amiga from the PC internet explorer just takes me to the Bing! search engine so I'm guessing it can't see the Amiga.
Open a command prompt on the PC and type:
ping 192.168.0.10
I'm guessing it'll work.
 
Where on earth did that virgin.net come from? You don't have that entered anywhere in the Easynet settings do you? If so remove it. Also if you entered anything to do with proxies, remove that too.

Virgin.net is in Easynet under network domain name. Easynet requires something in this field and this is what was automatically entered when I selected my ISP from their list. As DaveG is up and running with his entered as btbroadband.com, I assume that is not causing my issue.


Open a command prompt on the PC and type:
ping 192.168.0.10
I'm guessing it'll work.

Edit: Yes, it works.


Enable DNS Relay is ticked in the router settings - made no difference if it wasn't ticked.
Enable DHCP server is ticked in the router settings - made no difference it is wasn't ticked.
DHCP address range is 100 to 199 - the other machines on the network are issued with 100, 101, 102 and 103 IP's.
 
Virgin.net is in Easynet under network domain name. Easynet requires something in this field and this is what was automatically entered when I selected my ISP from their list. As DaveG is up and running with his entered as btbroadband.com, I assume that is not causing my issue.

Ah OK. Maybe it's automatically adding it somewhere along the line when an attempt to access the net without it fails?

Just for the hell of it, try setting your primary and secondary DNS servers in Easynet settings to:
8.8.8.8
8.8.4.4
(Those are Google's public DNS servers.)
See if that makes any difference.

Also check that you don't have anything proxy- or domain- related set in the web browser settings?
 
@fitzy

What browser are you using matey? I'm trying Aweb with all graphics turned off and it's like watching paint dry :thumbsdown:

Dave G :cool:


Funnily enough, with my 040 and GFX card the one page I'm managed to look at (yahoo.com) that also had graphics loaded and displayed in acceptable time. Just a bloody shame I can't look at anything else appart for yahoo.com though :lol: Ahhh, not funny really. Spending all my time messing about with this stuff instead of actually using the machine :(

---------- Post added at 20:33 ---------- Previous post was at 20:22 ----------

Ah OK. Maybe it's automatically adding it somewhere along the line when an attempt to access the net without it fails?

I think so.

Just for the hell of it, try setting your primary and secondary DNS servers in Easynet settings to:
8.8.8.8
8.8.4.4
(Those are Google's public DNS servers.)
See if that makes any difference.

No difference at all.


Also check that you don't have anything proxy- or domain- related set in the web browser settings?

I have selected proxy's to be disabled within Aweb. However, after having tried nearly every option on/off in the router settings I'm starting to wonder if it is Aweb causing problems. I really don't understand why this isn't working.

I will try Ibrowse in the next couple of days. I've spent all night on this and have to call it a night for tonight. I can't afford staying up till 5pm again :roll:
 
Just for the hell of it, try setting your primary and secondary DNS servers in Easynet settings to:
8.8.8.8
8.8.4.4
(Those are Google's public DNS servers.)
See if that makes any difference.

I'm a bit late to the party here but I was reading through this thread and the above is exactly what I was going to suggest before I reached robinsonb5's post.

However - how about trying the IP of your router as the DNS server?

Googling Easynet DNS problem took me here (symptoms seem very similar):

http://www.amiga.org/forums/showthread.php?t=38369
 
Hi Lewis,

Thanks for the siggestion. I'll try to play around ith this again over the weekend and report back on how I get on. As I mentioned over the weekend since I last tried I've now got a Virgin Media superhub so that may well give better results than I was having with the previous model.
 
Back
Top Bottom