Hello,

I am having this strange problem on a Windows 2003 server that I'm trying to use as NeoRouter server:

I setup everything as documented, and it works.

But suddenly the server tries to talk to the internet using the virtual network card (Zebra) instead of using the real network connection.

I mean, doing a pathping to an external server, I see that the connection starts from 8.0.0.1 instead of from 192.168.1.11 which is the static IP for the server real network.

So, the server is no longer able to communicate through the internet and everything stops working from then on.

The server is also a domain controller, and has a DNS. the DNS maps the server name with both the IPs (virtual and real); can this be the problem?

If so, can I just tell the zebra connection not to write to the DNS?

Thanks,
Mario

Hi mabian,

Thanks for using NeoRouter.

NeoRouter should work on a Windows Server 2003 (with Domain Controller, DNS and any services). The Zebra Virtual Adapter can be traded as a dumb adapter, so you don't want to use the virtual IP assigned to the virtual adapter in your configurations, such as DNS settings or any other settings, as the virtual IP is dynamically allocated by NeoRouter Server.

Would you put more information about your machine, so that we can dig deeper?
1. ipconfig /all
2. route print
3. pathping www.neorouter.com

Let us know if you still have problem.

Thanks!
_________________
KevinZ
NeoRouter team

I had the same problem - it would be nice if the installer took care of this or if they told you in the FAQ. There is a priority to the network adapters, which you can adjust by going into your Network Connections. There you will see the list of adapters. Click on Advanced in the drop-down menus, then Advanced Settings. You can then change the order in which Windows will use the various network adapters.

*Side note: About 20 minutes after making this change, I managed to screw up something and Neorouter would stall at connect. I reinstalled Neorouter, which put it's adapter back to the top of the priority list, but I am not having the network troubles I had before. Perhaps a re-install would be worth a try before my above suggestion?

Thanks, I can read only now because it seems the email notification doesn't seem to work.

I already tweaked the order of network cards, but to no avail.

I'll soon be able to give more information, but the problem is that the virtual network adapter messes with the network config and prevents the server from correctly connect to the internet.

- Mario

Hi mabian,

We cannot repro your issue in our site. We'd like to help you fix this problem, but we are lack of the detailed information about your server.

My feeling is some applications binds on it right now and it's better to find it out. The Adapter Binding Order does effects some applications, check http://www.neorouter.com/wiki/index.php/NeoRouterWiki:FAQ For details. But you mentioned it does not work for you. You can Disable the neorouter adapter see what happens.

It would be nice if you can provide more information. You can send email to support@neorouter.com from any email client, instead our website, if you don't mind.


BTW, thanks sifuchar for sharing your experience with us. So far, NeoRouter installer always set NeoRouter virtual adapter to the first position. We will change the logic to put it in the last position from next release.


Thanks!
_________________
KevinZ
NeoRouter team

kevinz, I also would like to nail the problem, unfortunately it happens on a production machine, so I don't know how deep I'll be able to test.

Anyway, I'm going to send you in a few days the route print, pathping and DNS configurations so that you can see better what happens.

Worst thing is that it works for a while, then it suddenly starts to want to use the neorouter virtual adapter address to reach the internet...

Please fix the forum email notification system, I have to go to the forum each time to see if there are answers to my posts...

- Mario

Hi Mario,

The forum email notification system has been enabled and the feed back form is opened to users as well.

thanks,
KevinZ

I confirm the emails work

Thanks, back soon.

- Mario

Ok, here are relevant info:

IP Config /ALL
-------------

Configurazione IP di Windows
Nome host . . . . . . . . . . . . . . : INFOSERVER
Suffisso DNS primario . . . . . . . . : prj.team
Tipo nodo . . . . . . . . . . . . . . : Sconosciuto
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Elenco di ricerca suffissi DNS. . . . : prj.team

Scheda Ethernet Connessione alla rete locale (LAN):
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Indirizzo fisico. . . . . . . . . . . : 00-0E-A6-C6-B2-88
DHCP abilitato. . . . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . . . : 192.168.1.11
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
Server DNS . . . . . . . . . . . . . : 192.168.1.10

Scheda Ethernet NeoRouter Connection:
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Zebra Network Interface
Indirizzo fisico. . . . . . . . . . . : 00-FF-B7-6D-1D-93
DHCP abilitato. . . . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . . . : 8.0.0.1
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . : 8.0.0.1


Route print:
-----------
IPv4 Tabella route
===========================================================================
Elenco interfacce
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0e a6 c6 b2 88 ...... VIA Rhine II Fast Ethernet Adapter
0x30004 ...00 ff b7 6d 1d 93 ...... Zebra Network Interface
===========================================================================
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfaccia Metrica
0.0.0.0 0.0.0.0 8.0.0.1 8.0.0.1 9000
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.11 20
8.0.0.0 255.255.255.0 8.0.0.1 8.0.0.1 30
8.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 30
8.255.255.255 255.255.255.255 8.0.0.1 8.0.0.1 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.11 192.168.1.11 20
192.168.1.11 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.11 192.168.1.11 20
224.0.0.0 240.0.0.0 8.0.0.1 8.0.0.1 30
224.0.0.0 240.0.0.0 192.168.1.11 192.168.1.11 20
255.255.255.255 255.255.255.255 8.0.0.1 8.0.0.1 1
255.255.255.255 255.255.255.255 192.168.1.11 192.168.1.11 1
Gateway predef.: 8.0.0.1
===========================================================================
Route permanenti:
Nessuna


A pathping test:
----------------
Rilevazione route verso www.prjteam.com [81.208.4.243]
su un massimo di 30 punti di passaggio:
0 INFOSERVER.prj.team [8.0.0.1]
1 * * *
Statistiche di calcolo per 25 secondi...
Da orig. a qui questo nodo/collegamento
Hop RTT Persi/Inv.= Pct Persi/Inv.= Pct Indir.
0 INFOSERVER.prj.team [8.0.0.1]
100/ 100 =100% |
1 --- 100/ 100 =100% 0/ 100 = 0% INFOSERVER.prj.team [0.0.0.0]

Rilevazione completata.

Other info:

- the network connection binding is set so that NeoRouter is AFTER the LAN main connection.

- if I remove the 0.0.0.0 route that uses the 8.0.0.1 interface everything is back fine.

- If I disable and enable the neorouter network connection it works for a while then suddenly it starts again using the 8.0.0.1 connection as route for the internet (could it be because the main connection fails?) and everything breaks.

- Even though I set the network connection to not write to the DNS, I find anyway an 8.0.0.1 entry for infoserver.prj.team.

Feel free to ask for more info, in the meanwhile I check if the system is stable without the route I removed.

I'm using 0.9.3 BTW.

Cheers,
Mario