NWLink NetBIOS

[sn0wflake]

What's so special about a NAT router compared to a switch?
Sorry, I'm crossposting this in the hardware forum as well

[garyng]

Using a switch, every PC in your network sees the outside world(isp) and they get the ip from there which can be on different subnet. As a result, when they communicate, they need to go through your isp's router, i.e. slow(adsl modem round trip).

Using a NAT router, PC in your network get an internal ip from the router and they cannot see the outside world(the router would do the dirty job). Then, all ip traffic behind the router would be full speed and only when you need, you go out to the outside world through the router.

BTW, when I said add static internal ip, it is in additional to the dynamic ip given by your isp and is still invisible to the outside world. But I am not sure ip Windows is smart enough to use it first. I know how to do it in Samba.

[sn0wflake]

How do I use static IP's in Knoppix by Samba?

[garyng]

in smb.conf

bind interfaces only = yes
interfaces = 192.168.1.1/24 127.0.0.1

[sn0wflake]

garyng: Binding didn't work. Maybe because I'm not sure what your smb.conf hack does. Why 192.168.1.1 and what is the number 24 for?

[garyng]

show me the ipconfig/all on Windows and ifconfig on knoppix. I need to know your current network setup to go further.

[sn0wflake]

The following is quikly translated from danish to english:

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

Windows IP-konfiguration

Hostname. . . . . . . . . . . . . . . . . . : winter
Primary DNS-suffiks. . . . . . . . . . . . . :
Nodetype . . . . . . . . . . . . . . . . . . : Unknown
IP-routing aktiveret . . . . . . . . . . . . : Nej
WINS-proxy aktiveret . . . . . . . . . . . . : Nej

Ethernet-netværkskort Internet:

Connectionspecific DNS-suffix. . . . . . : opasia.dk
Description. . . . . . . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC (3C905B-TX)
Physical adresse . . . . . . . . . . . . . . . : 00-20-5B-39-38-00
Dhcp aktiveret . . . . . . . . . . . . . . . : Ja
Automatisk configuration activated . . . . . : No
IP-adresse . . . . . . . . . . . . . . . . . : 80.164.38.47
Subnet mask. . . . . . . . . . . . . . . . : 255.255.255.0
Standardgateway. . . . . . . . . . . . . . . : 80.164.38.1
DHCP-server. . . . . . . . . . . . . . . . . : 80.166.137.5
DNS-servere. . . . . . . . . . . . . . . . . : 193.162.153.164
194.239.134.83

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

eth1 Link encap:Ethernet HWaddr 00:00:B2:58:EA:58
inet addr:80.161.126.52 Bcast:80.161.126.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43239 errors:0 dropped:0 overruns:0 frame:0
TX packets:33773 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:5710261 (5.4 MiB) TX bytes:3478752 (3.3 MiB)
Interrupt:11 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:116 errors:0 dropped:0 overruns:0 frame:0
TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8120 (7.9 KiB) TX bytes:8120 (7.9 KiB)

[Durand Hicks]

Snowflake,

Change your subnet mask to read: 255.0.0.0 on all of your machines and reboot to take effect on the windows machines. As for the linux machines, just do ifdown eth1 and then ifconfig eth1 subnet 255.0.0.0 <enter> and ifup eth1 and you're good to go. If you're not comfortable using the command line, then netcardconfig (GUI) alone should do it for you.

[sn0wflake]

My IP's are given by my ISP. I think the best solution is to buy a router. No weird configuration files, etc.

[garyng]

You need to give an 192.168.1.x address to each machine IN ADDITION to the existing one given by your ISP.

On linux,

ip addr add 192.168.1.10/24 dev eth1

On XP,

netsh interface ip add address "lan" 192.168.1.100 255.255.255.0

you need to replace "lan" with your device name(which is in danish and I don't know what it is) on your machine. I usually rename in in the network folder to something more manageable like "lan" instead of that long and cumbersome name with space given by microsoft !


After addition these two address, you can try ping from one machine to another with the 192.168.1.x address and if you get it, they will not go out to the wild internet when trying to communicate and the samba configuration I have given should work.