Static IP issues

  • Thread starter Thread starter A
  • Start date Start date
A

A

I own a linksys 4 port wireless router and some time ago I assigned one
of my machines a static IP, so that it wouldn't have its IP stolen by
other machines on the network. This was required for port forwarding
issues. I'm wondering is anyone can shed a little light on what I did,
as I ran into countless problems with the set-up.

initailly set to automatically obtain an IP addy, it would usually read
192.168.1.(100 - 105). Under the advice of a friend I gave the machine a
static IP of 192.168.1.2. This worked, but caused some strange things to
happen.

Shaw, my service provider, allows me to use 'shawmail' for the POP3 in my
email settings. All of a sudden this no longer worked. I solved the
problem by pinging 'shawmail' and assigning the actual IP of the mail
server as the POP3 address. I also was unable to get WOL magic packets
to work.

Can anyone offer any advice or direction on why this is and the best way
to set up a home network to accomodate port forwarding. Does it make
sense that 192.168.1.102 and 192.168.1.2 behave differently? as I believe
this was the case also.

Andrew
 
I own a linksys 4 port wireless router and some time ago I assigned one
of my machines a static IP, so that it wouldn't have its IP stolen by
other machines on the network. This was required for port forwarding
issues. I'm wondering is anyone can shed a little light on what I did,
as I ran into countless problems with the set-up.

initailly set to automatically obtain an IP addy, it would usually read
192.168.1.(100 - 105). Under the advice of a friend I gave the machine a
static IP of 192.168.1.2. This worked, but caused some strange things to
happen.

Shaw, my service provider, allows me to use 'shawmail' for the POP3 in my
email settings. All of a sudden this no longer worked. I solved the
problem by pinging 'shawmail' and assigning the actual IP of the mail
server as the POP3 address. I also was unable to get WOL magic packets
to work.

Can anyone offer any advice or direction on why this is and the best way
to set up a home network to accomodate port forwarding. Does it make
sense that 192.168.1.102 and 192.168.1.2 behave differently? as I believe
this was the case also.

Andrew
Click to expand...

Andrew,

When you setup your computer for a static ip address, did you manually setup the
DNS server addresses also?
 
yes, i used the ones that I found in network connections >> properties >>
support >> details.

This is where I pulled all my info from. Here's the info

Physical Address: 99-20-EG-6D-47-02
IP Address: 192.168.1.100
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DHCP Server: 192.168.1.1
Lease Obtained: 12/11/2004 2:22:22 PM
Lease Expires: 13/11/2004 2:22:22 PM
DNS Servers: 64.59.144.18, 64.59.144.19
WINS Server:

A
 
yes, i used the ones that I found in network connections >> properties >>
support >> details.

This is where I pulled all my info from. Here's the info

Physical Address: 99-20-EG-6D-47-02
IP Address: 192.168.1.100
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DHCP Server: 192.168.1.1
Lease Obtained: 12/11/2004 2:22:22 PM
Lease Expires: 13/11/2004 2:22:22 PM
DNS Servers: 64.59.144.18, 64.59.144.19
WINS Server:

A
Click to expand...

Did your problem start at the same time as you started using a fixed
configuration?

DNS resolution is affected by the LSP / Winsock subsystem.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

If XP SP2, Start - Run - "cmd". Type "netsh winsock reset catalog" into the
command window.

Give LSP-Fix and WinsockXPFix <http://www.cexx.org/lspfix.htm>, or WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257> a shot.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.
 
Back
Top