Cannot resolve host name

[pneron]

I seem to be having an issue with Aweb3.3
I have my TCP/IP stack working but now getting this message:

Cannot resolve host name

I can ping google.com or any other DNS site and I get a ping back.
I can FTP to Aminet from from CLI

I have an entry in my resolv.conf file that points to my DNS server.


thoughts?

[pneron]

No change

BTW: My IP stack is Inet-225 and when I ping from that dir via CLI, I get DNS responses back. When I FTP to anminet I can log-on.

Do I need to ASSIGN or ADD paths to DEVS: Internet dir or does Aweb "know" where Inet lives?

Thanks

[pneron]

Thanks Matt...I did have it running a few days ago so not sure what happened

Appreciate the bkg info

[pneron]

correct...just don't know where else. Like I said, I can ping google.com or FTP into AMinet with no issues, so it seems to be at the "application" layer I **think**
I was going to try and install the version of Aweb you sent me

[pneron]

Matt and team, here's a video that I hope will shed some light

https://youtu.be/TeIvbXP-zsw

[pneron]

OK, to be clear, I should try adding 8.8.8.8 to my "resolv.conf" file and see if I can get out?

[pneron]

Same  issues:

Ping aminet.net....message "alive"
Ping google.com ....message "alive"

Resolv.conf file:
nameserver 192.168.1.1 ---> my router
nameserver  8.8.8.8


Aweb3:
cannot resolve host name

FTP aminet.net

host name lookup failure

[pneron]

Thanks...to be clear, I did not choose Inet-225, I had it running for a few years and just recently started experiencing  this issue. I am thus just trying to understand why I would now be having this issue. But it sounds like I should now move away from this TCP/IP stack?

[pneron]

Thank you for the info, time to "upgrade" 

[pneron]

ok, will try this tonight

Thanks Matt

[pneron]

yep, I get an alive but still get "cannot resolve hostname" from Aweb

BTW: I only get an alive pinging from Inet:c  and not sys: c and assume this is ok?
Also my Inet-225 dir is located DEVS: Internet and assume that also ok and don't need any paths/assign statements.


My Amiga = 192.168.1.75
Gate/router = 192.168.1.1

netstat -nr:

Dest                  Gateway
127.0.0.1          127.0.0.1   
192.168.1.75     127.0.0.1
default               192.168.1.1
192.168.1.1       192.168.1.75

My resolv.conf file:

domain 192.168.1.1
nameserver 192.168.1.1
search hsd1.ma.comcast.net


I am going to try a new version on AWEB  and see if that helps. I am going to get Roadshow.

[pneron]

Yes for the Gateway - as long as I ping from Inet: dir....otherwise I get "unknown protocol ICMP". I would assume that NOT to be a concern since the "ping" command within DEV: Internet dir is not the same as Inet: C?

netstat -nr does not show any masking info, is there another command I can use to check?


Thanks

[pneron]

While I wait for Roadshow, I ended up installing Genesis and everything works now, so I suspect (as Matt & Kolla) said, must have been a "socket" issue with Inet-225...well time to move on. Thanks for all the help

[pneron]

Thanks for the bkg info, I am online now. I gave up trying to get Inet to work and went with Genesis stack and it works fine. I also order Roadshow which I will test at some point