I've read about this problem, but I didn't experience it until tonight.
I was trying to set up my server to host races during the weekends, since I
don't use it that much on Sat and Sunday.
However, it's a multi-homing setup (two NIC cards, one WAN and one LAN) and
I've run into the problem where the N4 Server program picks up on the LAN
card instead of the WAN card for listening.
I know that one way around this verified bug is to disable the LAN card.
However, I can't do that or I wouldn't be able to race in my own races on my
client machine :)
Is there another way to force the N4 Server to use the right (WAN) card?
Something in one of the INI's that can be changed?
I know it's a known, verified bug that they are working on, but I'd like to
put the server on line now.
Thanks :)
-Larry
At the moment if you set up the server to report to sierra.com (this is on
by default) you will run into this problem. However if you're feeling
adventurous and don't want to wait for the patch, you might try uninstalling
your NIC's and reinstalling them such that the WAN IP shows up above the LAN
IP in N4's 'Connect Via' drop-down list. The bug is that the sierra.com
login uses the first TCP/IP device, so this should work around that problem
by moving the preferred device to the top.
--
Eric
"Larry" <[email hidden]> wrote in message
news:3Q7h6.57420$[email hidden]...
> Is there another way to force the N4 Server to use the right (WAN) card?
Eric,
I'm not sure this would work. I'm only showing one IP, the WAN (private) ip
in the drop down right now.
Oddly, every other IP server program I run treats the WAN card as the first
connection. Only N4 skips it and goes to the second address.
Thanks for the info!
Oh, and the WAN card _is_ the first card installed already.
-Larry
"Eric Busch" <[email hidden]> wrote in message
news:963r3l$nfu$[email hidden]...
> At the moment if you set up the server to report to sierra.com (this is on
> by default) you will run into this problem. However if you're feeling
> adventurous and don't want to wait for the patch, you might tryuninstalling
> your NIC's and reinstalling them such that the WAN IP shows up above theLAN
> IP in N4's 'Connect Via' drop-down list. The bug is that the sierra.com
> login uses the first TCP/IP device, so this should work around thatproblem
Quoted text (10 lines)
> by moving the preferred device to the top. > > -- > Eric > > "Larry" <[email hidden]> wrote in message > news:3Q7h6.57420$[email hidden]... > > Is there another way to force the N4 Server to use the right (WAN) card? > >Are you behind a router or firewall? This is a separate but related
sierra.com login problem with N4 reporting the non-routable LAN IP of the
NIC to sierra.com, not the routable WAN IP of the router/firewall. This
will be patched, but there is no workaround at the moment.
--
Eric
"Larry" <[email hidden]> wrote in message
news:Ldkh6.61704$[email hidden]...
>
> I'm not sure this would work. I'm only showing one IP, the WAN (private)
ip
> in the drop down right now.
>
> Oddly, every other IP server program I run treats the WAN card as the
first
> connection. Only N4 skips it and goes to the second address.
>
> Thanks for the info!
>
> Oh, and the WAN card _is_ the first card installed already.
That is precisely my problem. Sad that there is no work-around :(
This really should have been caught in testing.
-Larry
"Eric Busch" <[email hidden]> wrote in message
news:966a88$pme$[email hidden]...
(private)
