PDA

View Full Version : Slimserver and SB3 on PC with 2 NiC



sorenson
2006-08-28, 07:44
My HTPC has 3 NiC, two onboard, one of which that I use to connect to my LAN, the other is disabled, and a PCi Wi-Fi NiC that I use to connect wirelessly to my SB3 thru an ad-hoc connection.

The problem arises when at least two NiC are active, if I enable my onboard LAN NiC for internet and network access and then enable either one of the others the slimserver fails to find the SB3, but if I disable my LAN NiC and then use either one of the others to connect to the SB3 it works.

It seems to me that with two open network connections the slimserver doesnt know were to listen.

I know that if I connected the SB3 to my switch or had a wireless gateway it would be much easyer, but those options are not available right now.

so in a nut shell, I need to make slimserver listen on the PCi Wi-Fi NiC iP, even though there is another ethernet connection active, and be able to route the internet access requests the SB3 makes to the proper place.

Paul_B
2006-08-28, 08:05
What operating system are you using? Do you have the ability to set the binding options?

sorenson
2006-08-28, 09:25
OS: MS Win XP SP2 MCE 2005 UR2

the iP are static and are manually assigned, the Wi-Fi part has no security options enabled and just TCP-iP as protocol.

LAN NiC iP: 192.168.0.11
Wi-Fi NiC iP: 192.168.0. 8
SB3 iP: 192.168.0. 7
Gateway iP: 192.168.0. 9
SSiD: htpc
Subnet mask: 255.255.255.0
and DNS servers are also indicated

Paul_B
2006-08-28, 10:47
Okay what does a "netstat -a" from the command-line give you?

sorenson
2006-08-28, 14:53
ok with only the Wi-Fi NiC enabled it returns this:

Proto Local Address Foreign Address State
TCP htpc:epmap htpc:0 LISTENING
TCP htpc:microsoft-ds htpc:0 LISTENING
TCP htpc:1110 htpc:0 LISTENING
TCP htpc:3389 htpc:0 LISTENING
TCP htpc:3483 htpc:0 LISTENING
TCP htpc:8058 htpc:0 LISTENING
TCP htpc:9000 htpc:0 LISTENING
TCP htpc:9090 htpc:0 LISTENING
TCP htpc:1031 htpc:0 LISTENING
TCP htpc:1041 localhost:1042 ESTABLISHED
TCP htpc:1042 localhost:1041 ESTABLISHED
TCP htpc:1150 localhost:9000 ESTABLISHED
TCP htpc:9000 localhost:1150 ESTABLISHED
TCP htpc:netbios-ssn htpc:0 LISTENING
TCP htpc:3483 192.168.0.7:29359 ESTABLISHED
TCP htpc:9000 192.168.0.7:29386 ESTABLISHED
UDP htpc:microsoft-ds *:*
UDP htpc:isakmp *:*
UDP htpc:1025 *:*
UDP htpc:1032 *:*
UDP htpc:1060 *:*
UDP htpc:1900 *:*
UDP htpc:3483 *:*
UDP htpc:4500 *:*
UDP htpc:8008 *:*
UDP htpc:netbios-ns *:*
UDP htpc:netbios-dgm *:*

----------------------------------------------------------------

and with both NiC enabled:

Proto Local Address Foreign Address State
TCP htpc:epmap htpc:0 LISTENING
TCP htpc:microsoft-ds htpc:0 LISTENING
TCP htpc:1110 htpc:0 LISTENING
TCP htpc:3389 htpc:0 LISTENING
TCP htpc:3483 htpc:0 LISTENING
TCP htpc:8058 htpc:0 LISTENING
TCP htpc:9000 htpc:0 LISTENING
TCP htpc:9090 htpc:0 LISTENING
TCP htpc:1031 htpc:0 LISTENING
TCP htpc:1151 localhost:9000 TIME_WAIT
TCP htpc:1152 localhost:1110 TIME_WAIT
TCP htpc:1153 localhost:1110 TIME_WAIT
TCP htpc:netbios-ssn htpc:0 LISTENING
TCP htpc:3483 192.168.0.7:29389 SYN_RECEIVED
TCP htpc:netbios-ssn htpc:0 LISTENING
TCP htpc:1154 66.102.11.99:http TIME_WAIT
TCP htpc:1155 66.102.11.99:http TIME_WAIT
UDP htpc:microsoft-ds *:*
UDP htpc:isakmp *:*
UDP htpc:1025 *:*
UDP htpc:1032 *:*
UDP htpc:1060 *:*
UDP htpc:1900 *:*
UDP htpc:3483 *:*
UDP htpc:4500 *:*
UDP htpc:8008 *:*
UDP htpc:netbios-ns *:*
UDP htpc:netbios-dgm *:*
UDP htpc:netbios-ns *:*
UDP htpc:netbios-dgm *:*

----------------------------------------------------------------

what was amazing was the SB3 working perfectly, but as soon as I enabled the LAN NiC it lost connection, but when I disabled it the SB3 came back instantly.

I even tried enabling ICS but with mixed results, so its off now.