VoxVirilis
08-05-2007, 21:08
My home network is setup with a gateway (role, not manufacturer) machine running Windows 2000 that I am attempting to run a TeamSpeak server on. This machine shares the internet connection with the rest of my home network but it IS NOT behind the router. I have no firewalls running on this machine.
The IP's listed for this machine are: ( WAN: 71.49.187.235) (LAN: 192.168.0.1 & 192.168.1.33) I understand that the 192.168.0.1 IP comes from the machine using Internet Connection Sharing.
Within the LAN I can connect to the server ONLY on the 192.168.0.1 IP and not on the 192.168.1.33 one. No one outside the LAN can connect on the WAN IP.
Do I have to enact some kind of port forwarding that passes requests to the WAN IP to the LAN IP? If so how would I do that? Maybe I'm missing the boat entirely! Either way, your help will be greatly appreciated...
Edit: to add info
This is what I get with an "ipconfig /all" command:
[I]Windows 2000 IP Configuration
Host Name . . . . . . . . . . : vox
Primary DNS Suffix . . . . . :
Node Type . . . . . . . . . . : Broadcast
IP Routing Enabled . . . . . : Yes
WINS Proxy Enabled . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . . . . : NETGEAR FA311/312 PCI Adapter #2
Physical Address . . . . . . . . . . . : 00-0F-B5-FA-DE-69
DHCP Enabled . . . . . . . . . . . . . : No
IP Address . . . . . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . :
DNS Servers. . . . . . . . . . . . . . . . :
Ethernet adapter Internet Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . . . . : NETGEAR FA311/312 PCI Adapter
Physical Address . . . . . . . . . . . : 00-0F-B5-FE-78-D1
DHCP Enabled . . . . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . : Yes
IP Address . . . . . . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . . . . . : 192.168.1.1
Lease Obtained . . . . . . . . . . . . . . : Tuesday, blah blah blah
Lease Expires . . . . . . . . . . . . . . . : Friday, blah blah blah
Maybe that'll shed more light on the problem...
Vox
The IP's listed for this machine are: ( WAN: 71.49.187.235) (LAN: 192.168.0.1 & 192.168.1.33) I understand that the 192.168.0.1 IP comes from the machine using Internet Connection Sharing.
Within the LAN I can connect to the server ONLY on the 192.168.0.1 IP and not on the 192.168.1.33 one. No one outside the LAN can connect on the WAN IP.
Do I have to enact some kind of port forwarding that passes requests to the WAN IP to the LAN IP? If so how would I do that? Maybe I'm missing the boat entirely! Either way, your help will be greatly appreciated...
Edit: to add info
This is what I get with an "ipconfig /all" command:
[I]Windows 2000 IP Configuration
Host Name . . . . . . . . . . : vox
Primary DNS Suffix . . . . . :
Node Type . . . . . . . . . . : Broadcast
IP Routing Enabled . . . . . : Yes
WINS Proxy Enabled . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . . . . : NETGEAR FA311/312 PCI Adapter #2
Physical Address . . . . . . . . . . . : 00-0F-B5-FA-DE-69
DHCP Enabled . . . . . . . . . . . . . : No
IP Address . . . . . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . :
DNS Servers. . . . . . . . . . . . . . . . :
Ethernet adapter Internet Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . . . . : NETGEAR FA311/312 PCI Adapter
Physical Address . . . . . . . . . . . : 00-0F-B5-FE-78-D1
DHCP Enabled . . . . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . : Yes
IP Address . . . . . . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . . . . . : 192.168.1.1
Lease Obtained . . . . . . . . . . . . . . : Tuesday, blah blah blah
Lease Expires . . . . . . . . . . . . . . . : Friday, blah blah blah
Maybe that'll shed more light on the problem...
Vox