Reply 20 of 27, by another
Now I found out about the realnic parameter and fixed it.
Don't know if you can call my network setup "LAN". It's a desktop computer's and a notebook, either connected by cable to the router or by WLAN. Router is a normal A-DSL router with WLAN.
For debugging I downloaded the wat TCP/IP tools, it includes tcpinfo and ping.
DOSBox's NE2000 is getting a new uniqe IP thought BOOTP and it can ping itself. The name of the router is seen. Subnetmask (default one) is also detected. The gateways (the router) IPis also seen and correct. Nameserver IP is same like gateway IP, all right so far.
I can ping another computer on "lan" (the host comptuer where DOSBox is running) IP successfully.
The strange thing is, when I try to ping the IP of the gateway (router) this will not be answered. (Perhaps this is the reason why Arachne isn't working.)
Windows Firewall is deactivated (I don't need it as the router has NAT and is "stealthing" all but manually forwarded ports.) so this can not be the problem.
Do you have an idea what is blocking the ping between DOSBox and router? (By the way, before someone is asking, yes, I can ping my router successfully form any comptuer on LAN.)