Help for setting everything up (NAT problems)

[Paradise]

Ok, after getting the web working on all PC's i need help for setting everything up perfectly.

The NIC to my cable modem and all the other PC's NIC's are set to IP address automatically.
The NIC to the private network is set to 192.168.0.1 / 255.255.255.0

Network Connections:
LAN-Connection: external untrusted
LAN-Connection 2: internal protected

DHCP Service properties:
DHCP Mode: Semi Automatic, Assign DNS, Assign Gateway

DHCP Settings:
Scope: 192.168.0.2 - 192.168.0.254
--------[192.168.0.5]Xbox 360
--------[192.168.0.4]00:1C:4A:25:4A:48 (FritzBox)
--------[192.168.0.3]Serving-bird
--------[192.168.0.2]Paradise-one

Extended Network Driver > Port Security > Connections from Internet:
UDP 3074
UDP 53
UDP 88
UDP 62742
TCP 53
TCP 80
TCP 3074
TCP 62742
TCP 3075 - 4096 (was allready there)
TCP 1024 - 3073 (was allready there)

1. I just need the NAT/DHCP stuff. What Services can i disable?
2. Why does Windows Network and Sharing Center show the private network NIC as not identifiable and the modem NIC has the homenetwork?
3. I set all ports from "support.xbox.com/support/en/us/nxe/kb.aspx?ID=979000&lcid=1033&category=xboxlive" but the Xbox check still says there are problems.
4. If i check ports with "whatsmyip.org/ports/" it says allways say are closed. The Firewall tab shows nothing...
5. The WinGate Engine Monitor that i have in the Windows 7 autostart folder is not starting after i boot my PC.
6. Most important point. If i call my VoIP number (FritzBox) from my handy then my handy has the free line signal, but my housephone is not ringing. The Firewall tab shows port UDP 5060. If my friend calls me from his handy the Firewall also shows port 5060, but my phone is ringing and we can talk. If i add UDP 5060 to Port Security then the Firewall tab shows nothing but i still cant call from my handy.

[logan]

1. I just need the NAT/DHCP stuff. What Services can i disable?

For NAT you need the Extended Networking Driver (ENS) driver.
For DHCP, the DHCP service.
For DNS, the DNS service.
And to manage WinGate, make sure you don't disable the Remote Control Service.
The rest of the services can be disabled as required.

2. Why does Windows Network and Sharing Center show the private network NIC as not identifiable and the modem NIC has the homenetwork?

Windows Vista/7 uses the default gateway of a network adapter to identify the network. When you connect to a network with a known default gateway, it can recall what security settings you had for that network.
On networks with no default gateway, Windows cannot identify the network so you can't change it from public to private. Unfortunately, I have not discovered any way to change this behavior of Windows Vista/7.

3. I set all ports from "support.xbox.com/support/en/us/nxe/kb.aspx?ID=979000&lcid=1033&category=xboxlive" but the Xbox check still says there are problems.

Are there any other firewalls on the WinGate computer? If so, could they be blocking the packets? Do you see the forwarded ports in WinGate's activity or firewall tabs when the xbox connects to the internet?

4. If i check ports with "whatsmyip.org/ports/" it says allways say are closed. The Firewall tab shows nothing...

The fact that the firewall tab in WinGate shows nothing suggests that the ports aren't reaching WinGate, or they are being redirected but are being blocked further withing your network (unlikely considering it's a home network). Again, check for any other firewalls on the WinGate computer, and check that the ports are also forwarded from your internet modem/router if applicable.

5. The WinGate Engine Monitor that i have in the Windows 7 autostart folder is not starting after i boot my PC.

The engine monitor uses a hook into the OS that allows it to stop/start /monitor the WinGate daemon. On Windows 7, this hook requires administrator privileges, so UAC prevents it from loading at startup.

6. Most important point. If i call my VoIP number (FritzBox) from my handy then my handy has the free line signal, but my housephone is not ringing. The Firewall tab shows port UDP 5060. If my friend calls me from his handy the Firewall also shows port 5060, but my phone is ringing and we can talk. If i add UDP 5060 to Port Security then the Firewall tab shows nothing but i still cant call from my handy.

I'm not familiar with FritzBox, so I gathered some information and found it uses TCP/UDP port 5060, and nothing else. Now when you said the firewall tab showed UDP5060, what direction was that in? client(phone) to server(fritz) or vice versa?

[Paradise]

Ok, i bought WinGate and its now time to get everything running :-)

But my network changed. I have now a cable modem router from my ISP. So VoC (VoIP) not longer goes trough WinGate. Thats better, cause if the WinGate Server is down the phone is still working.
One drawback is that there is no traffic shaping for the phone's. My idea is to limit the bandwith on the WinGate Server to reserve bandwith for VoC. Don't know if this will work and how much i need to clip off for HD-phoning.

So first here is my network:


And here the settings:

FRITZ!Box 6360 Cable Router:
Internal IP: 192.168.100.1
DHCP: off

WAN (NIC 1 to Modem):
IP: 192.168.100.2
Subnet: 255.255.255.0
Standard-Gateway: 192.168.100.1
Primärer DNS-Server: 192.168.100.1
Sekundärer DNS-Server: blank

LAN (NIC 2 to LAN):
IP: 192.168.0.1
Subnet: 255.255.255.0
Standard-Gateway: blank
Primärer DNS-Server: blank
Sekundärer DNS-Server: blank

I turned off the firewall in WinGate, cause the FRITZ!Box 6360 does it.
Windows firewall is also off. And here are the FRITZ!Box 6360 port settings:

I need to forward to the NIC 1 (192.168.100.2), right?

On my PC Paradise-One http://www.whatsmyip.org/ports/ tells me:
Port 62742 is Open
Port 45275 is Open
Port 45740 is Closed (eMule port-test says open)
Port 88 is Closed
Port 53 is Closed
Port 3074 is Closed
Port 80 is Closed
Port 53 is Closed

The other thing is that Paradise-One does not see the FRITZ!Box 6360 Cable Router:


The WinGate Server can see it:


In the Network Map on Paradise-One are some devices are not in place. Karin-PC, Sharry (WinGate Server), TV and the small FRITZ!Box 7170. Don't now if the TV can be shown. But Karin-PC is Vista and the WinGate Server is Win7, so they have LLTD (Link Layer Topology Discovery):


The Network Map on Sharry (WinGate Server) shows just:

[Paradise]

Support???

[logan]

Sorry for the delay. I haven't been around the office for the past few months.

One drawback is that there is no traffic shaping for the phone's. My idea is to limit the bandwith on the WinGate Server to reserve bandwith for VoC. Don't know if this will work and how much i need to clip off for HD-phoning.

If I understand the fritzbox correctly, it should still be able to to perform QoS shaping for the VoIP as it's external to WinGate and the last port of call before the internet, so is actually the best place to do bandwidth shaping. For VoIP clients connecting through WinGate to the fritzbox, bandwidth shaping need not apply since the fritzbox is local and there will be ample bandwidth over ethernet.

I need to forward to the NIC 1 (192.168.100.2), right?

Correct, and from there, use WinGate's Extended Networking to forward to the rest of the computers on the LAN.

The other thing is that Paradise-One does not see the FRITZ!Box 6360 Cable Router

The WinGate server sits on a different subnet, obscured by WinGate. The clients see WinGate as their gateway, and are not concerned about anything beyond that. You should still be able to access the router using it's IP address, but it won't show up in your network map because LLTD only maps the local subnet.

The Network Map on Sharry (WinGate Server) shows just

LLTD uses the DHCP server of a network adapter to identify the network and a network must be identified before it will use LLTD will do any form of discovery on that network, but WinGate itself is the DHCP server and doesn't require a DHCP server to be set on the local network adapter. Therefore Windows LLTD will discover the external network (where the router is) but it won't search for devices on your internal network. This is a shortcoming of the LLTD system, and something that you cannot fix from WinGate. However, it won't effect your internet/network connectivity at all. LLTD is a protocol for information purposes only.

[Nev]

Sorry for the delay. I haven't been around the office for the past few months.

Hey 'loges' where you been?

Tripping in the Caribbean perhaps. ;)

[logan]

Hey 'loges' where you been?

Tripping in the Caribbean perhaps. ;)

I wish :D, but no. I've been studying at university.