Can not get GR8NET in Symbos

Página 2/3
1 | | 3

Por JohnFante

Expert (72)

Imagen del JohnFante

28-10-2017, 16:04

Thank you once again for all your help :-)

First som specs - just in case :-): I have a TurboR ST with 512K. The GR8NET is installed in the top slot. In the back slot I have an SE-One. I have a d-link DIR-655 router with tons of things connected to. Normally it just works.

I can get on my LAN with no problem. When I login to my router GR8NET is added to the list of IPs that the DHCP server has handed out. In this case: 192.168.0.188. An I can login to my Synology diskstation via telnet at 192.168.0.198 (where it is located). So LAN is fine - at least when I use IP-numbers.

Your questions:

-Is the MAC address correctly displayed in SymbOS?
Yes. The same MAC as when I boot.

https://www.dropbox.com/s/2wjsu4ktqbmv6tl/IP.jpg

-Could you remove network.ini file from the disk and setup the daemon again.
I have done that but no change. I have also reinstalled. Still nothing in netstat (version 1.0)

-can you resolve a HOSTNAME in your local network ? (for example your PC?) you can use nslookup in the SymShell for this to test

No. I get an request timeout every time and the same when I try to use nslookup for google.com or network.symbos.org it timesout.

https://www.dropbox.com/s/o4l577sswo8k1ki/nslookup.jpg?dl=0

- can you use google dns 8.8.8.8 (so let it on DHCP for the IP but for DNS set it fixed to 8.8.8.8)
Still the same problem if I go to static DNS 8.8.8.8. Request time out.

- What is the firmware of the GR8NET?
I am using v.00.07 (2017/9/27). The firmware that came with the card.

- Do you use mapper mode 24,1?
Yes. I have also tried just callnetsetmap (24). The same.

Por edoz

Prophet (2445)

Imagen del edoz

28-10-2017, 17:30

JohnFante wrote:

Thank you once again for all your help :-)

I can get on my LAN with no problem. When I login to my router GR8NET is added to the list of IPs that the DHCP server has handed out. In this case: 192.168.0.188. An I can login to my Synology diskstation via telnet at 192.168.0.198 (where it is located). So LAN is fine - at least when I use IP-numbers.

Do you mean that you used SymbOS to connect with telnet ? Or did you used a PC?
So if you are able to use telnet in symbos and can connect to your local network (in your own subnet) .. that is what i like to know.

Por JohnFante

Expert (72)

Imagen del JohnFante

28-10-2017, 17:34

edoz wrote:

Do you mean that you used SymbOS to connect with telnet ? Or did you used a PC?
So if you are able to use telnet in symbos and can connect to your local network (in your own subnet) .. that is what i like to know.

Yes. I used telnet in Symbos to connect to my DiskStation.

Por edoz

Prophet (2445)

Imagen del edoz

28-10-2017, 17:47

OK! So now we can conclude that your local network is working in SymbOS in the same subnet.
Does this DiskStation has a hostname? And if so, is this host name registerd by your local DNS server (your router?)
And could you connect by hostname in telnet to the DiskStation? So in other words.. does DNS works in your local subnet?

And next, in the SymbOS chat program did you try to use to the IP of network.symbos.org (87.106.252.130) so not the hostname but the IP. If that works we are sure it is somehow DNS related.

and in MSX basic can you preform a CALLNETSETHOST("www.google.com") (then we can see if DNS works here as well)

Por JohnFante

Expert (72)

Imagen del JohnFante

29-10-2017, 09:13

I think I found the problem and a solution :-)

My router setup is as follows: Broandband modem/router from my ISP ---> d-link router that runs my LAN. Both wired and wireless. The one I communicate to. This is the setup my ISP recommends if you have a functioning LAN already as I did when I got the modem.

The d-link router has fixed DNS settings from openDNS - works fine normally and it gives me access to all the sites I want to go - no DNS blocking .... - and is located at 192.168.0.1. The broadband modem/router from my ISP is located at 192.168.1.1. If I change DNS setting in Symbos to manually set at 192.168.1.1 DNS now works in Symbos and I can join network.symbos.org via the URL. Before I changed I could only get on using the IP.

So somehow my setup confused GR8NETs DNS query. At least in Symbos.

Now I am a bit unsure If have to change the DNS in MSX Basic also. When I write callnetbrowse it works fine at least on Eugenys site and I can also use the online database from Eric Boez and Victor Martinez.

No matter what thank you very, very much for your help :-D

Por edoz

Prophet (2445)

Imagen del edoz

29-10-2017, 12:07

Good that it works now! However i still wonder if in basic the IP is used or the DNS name Wink But don't change anything in a working setup LOL!

Por AxelStone

Prophet (3140)

Imagen del AxelStone

25-10-2018, 08:18

I've read the whole thread and I'm facing exactly the same problem, just installed SymbOS on my GR8Net updated to last firmware and can't solve DNS. According to your indications @JohnFante, it seems I could have same issue, automatic DNS sets my server to 192.168.0.1 and I don't know if changing to 192.168.1.1 it'll solve it.

Now I'm in the office, I'll try this evening your suggestion Smile

Por AxelStone

Prophet (3140)

Imagen del AxelStone

25-10-2018, 19:03

Definitively I've no network under SymbOS :-(. From basic I can perform perfectly telnet to bbs.hispamsx.org:23, but using symbos I allways get nslooup error even using direct IP, so I've no conection on SymbOS :-(.

GR8Net correctly detected by driver and suposely it's online. Any idea?

Por edoz

Prophet (2445)

Imagen del edoz

26-10-2018, 16:49

Could you check firmware (please look at the date stamp as well!) :

In SymbOS could you connect to:

Or try to resolve the hostname on other PC and fill in the IP.

Which version do you use ? .02 ?

What is the file size of the GR8NET daemon you use?

And did you set the card index correct in the driver tab ?

Here it works with GR8NET version displayed in the image.

Por DarkSchneider

Paladin (944)

Imagen del DarkSchneider

26-10-2018, 17:35

Do a:
PING 8.8.8.8
If works, the internet is enabled. It could be a DNS client was not implemented yet.

Quote:

Or try to resolve the hostname on other PC and fill in the IP.

That's harder, because your network names are not using DNS but usually NetBIOS in a Windows network, or even a Linux network with a Samba server with Master Browser option enabled, and probably that is not implemented as it could get many resources. Nslookup will not find your local hosts unless you have your own DNS server configured in your LAN to resolve those names. External DNS servers will not know anything about your local network so they will not resolve.

Página 2/3
1 | | 3