Corona

Yeah, all different subnets. I decided against ever setting up bridging, nat did all I needed (except maybe udp broadcast forwarding, but that's a different story) ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : tonal Primary Dns Suffix . . . . . . . : Corona Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : swin.edu.au Ethernet adapter Ext Eth: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : SMC EtherPower II 10/100 Ethernet Adapter Physical Address. . . . . . . . . : 00-E0-29-24-AE-80 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.94 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 136.186.1.111 136.186.20.9 Ethernet adapter Int Eth: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel® PRO/100+ Management Adapter Physical Address. . . . . . . . . : 00-D0-B7-49-8C-61 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 136.186.1.111 136.186.20.9 Ethernet adapter rtl wireless: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8180 Wireless LAN (Mini-)PCI N IC Physical Address. . . . . . . . . : 00-30-BD-4D-4E-A2 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Autoconfiguration IP Address. . . : 169.254.115.41 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : Ethernet adapter usb wireless: Connection-specific DNS Suffix . : wl.swin.edu.au Description . . . . . . . . . . . : Belkin 11Mbps Wireless USB Network Adapter #2 Physical Address. . . . . . . . . : 00-30-BD-63-44-F7 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 136.186.49.11 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 136.186.49.1 DHCP Server . . . . . . . . . . . : 136.186.1.123 DNS Servers . . . . . . . . . . . : 136.186.1.123 Primary WINS Server . . . . . . . : 136.186.3.47 Secondary WINS Server . . . . . . : 136.186.3.31 Lease Obtained. . . . . . . . . . : Saturday, 22 May 2004 9:08:22 PM Lease Expires . . . . . . . . . . : Sunday, 23 May 2004 12:08:22 AM Ethernet adapter cisco vpn virtual tunnel: Connection-specific DNS Suffix . : swin.edu.au Description . . . . . . . . . . . : Cisco Systems VPN Adapter Physical Address. . . . . . . . . : 00-05-9A-3C-78-00 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 136.186.252.116 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 136.186.252.116 DNS Servers . . . . . . . . . . . : 136.186.1.111 136.186.20.9 yes there's a couple more adaptors than I said in original post, but it amounts to the same thing. and I'll agree it looks like RRA wont do it, does using other 3rd party software routers mean I'll likely have significant loss of performance, or are they usually low enough in the network layers that it's not an issue? by significant I mean say under 5MB/s throughput on 100Mbit ethernet. I currently get around 7MB/s throughput (with direct connect file sharing) between the two ethernet's. thanks, Corona

ok, yeah I'd already enabled that setting, but I still haven't recognised anything in event viewer that looks like firewall hits. I'm assuming they're supposed to be under the system log in there? Do you know how I could find firewall hits, I can't find any events in there with a source that sounds like something firewall related, just general browsing through the logs hasn't helped me any. Do you know anywhere I could get documentation for this stuff? I've been combing the windows help and trying to find something on the web, but can't find anything. I would have expected notification to be one of the key features of any firewall? Thanks for your help so far, Corona

I'm on a uni network, with 3 different networks running. There's an 'external' ethernet, and 'external' wireless and my own 'internal' ethernet. I've got my server, now running win 2k3 server, sitting on all 3, trying to nat between them. I'm currently using the built in Routing and Remote Access service for nat. I can happily enable nat on the two external ones and gain access to them from my internal, but I would like to be able to go the other direction as well, which is what I used to do with linux on the server. By that I mean I want people on the external ethernet to be able to access the wireless connection, and people on the wireless to access my internal and external ethernets. With nat enabled on all interfaces, nothing works at all. When I ran linux, I could have nat enabled on all interfaces, make sure forwarding was allowed by the packet filter, and with the server's ip set as gateway on any other computer, I could access any of the networks from any other one. I'm hoping this is possible from windows. Thanks Corona

ah, I've just tried enabling ICF and turn on logging as suggested, and it tells me that ICS and ICF cannot be enabled becuase routing and remote access is enabled. The two obviously are seperate things, and don't co-operate. Corona

I actually didn't have ICF enabled, I'm just using the 'basic firewall' that seems to be part of routing and remote access, in the IP Routing section. These appear to be two seperate firewall's, are they? Because while the basic firewall and packet filtering that I have going are working, ICF wasn't enabled on the interface. Corona

I'm converting my linux server to win 2k3 for the better wireless support, but am having some difficulty setting up the built in firewalling/packet filtering. I'm setting up my IP Routing rules, specifically the inbound and outbound filters, both from gui and netsh. That's going alright, but my main problem just now is trying to find a log of packets that are being denied, ie what is hitting the firewall. When trying to run network based programs, and finding them not working, it's hard to know whether the problem is with the program, the network, of just the firewall. Under linux I'd just have a qiuck look at the system log to see if there had been any packets blocked, if so copy down the protocol and port and then open up them up in my firewall script. I'm trying to find something similar for windows. Thanks, Corona