"Jim" <jrwo***@comcast.net> wrote in message
news:%232l7gj1xJHA.1424@TK2MSFTNGP02.phx.gbl...
> While this is not a WHS (Windows Home Server) newsgroup, I'm hoping
> someone with networking experience could advise me on what appears to be
> an Internet access problem.
>
>
>
> I'm operating 3 Windows XP computers on a LAN. I also run a WHS system
> which has been going great for many months. BUT just recently I've been
> unable to access this system via the Internet. I've tried just about
> everything with no success. The following ports are forwarded to
> (198.162.1.102) on my Linksys BEFS41 V.2 router as per the instructions.
>
>
>
> HTTPS            port 443 TCP
>
> HTTP              port 80 TCP
>
> Remote            port 3389 TCP
>
> RDP                port 4125 TCP
>
>
>
> I've also changed my domain name (xxx.homeserver.com) several times with
> no difference - still unable to access it.
>
>
>
> Someone said that Comcast may be blocking access but I've pointed out that
> I'm also running an IIS Web server on another XP machine with no access
> problems.
>
>
>
> GREATHY appreciate any/all suggestions.
>
>
>
>

"Jim" <jrwo***@comcast.net> wrote in
news:#2l7gj1xJHA.1424@TK2MSFTNGP02.phx.gbl:

> While this is not a WHS (Windows Home Server) newsgroup, I’m
> hoping someone with networking experience could advise me on what
> appears to be an Internet access problem.
>
>
>
> I’m operating 3 Windows XP computers on a LAN. I also run a WHS
> system which has been going great for many months. BUT just
> recently I’ve been unable to access this system via the Internet.
> I’ve tried just about everything with no success. The following
> ports are forwarded to (198.162.1.102) on my Linksys BEFS41 V.2
> router as per the instructions.
>
>
>
> HTTPS            port 443 TCP
>
> HTTP              port 80 TCP
>
> Remote            port 3389 TCP
>
> RDP                port 4125 TCP
>
>
>
> I’ve also changed my domain name (xxx.homeserver.com) several
> times with no difference – still unable to access it.
>
>
>
> Someone said that Comcast may be blocking access but I’ve pointed
> out that I’m also running an IIS Web server on another XP machine
> with no access problems.
>

> "Jim" <jrwo***@comcast.net> wrote innews:#2l7gj1xJHA.1***@TK2MSFTNGP02.phx.gbl:
>
>
>
> > While this is not a WHS (Windows Home Server) newsgroup, I’m
> > hoping someone with networking experience could advise me on what
> > appears to be an Internet access problem.
>
> > I’m operating 3 Windows XP computers on a LAN. I also run a WHS
> > system which has been going great for many months. BUT just
> > recently I’ve been unable to access this system via the Internet.
> > I’ve tried just about everything with no success. The following
> > ports are forwarded to (198.162.1.102) on my Linksys BEFS41 V.2
> > router as per the instructions.
>
> > HTTPS            port 443 TCP
>
> > HTTP              port 80 TCP
>
> > Remote            port 3389 TCP
>
> > RDP                port 4125 TCP
>
> > I’ve also changed my domain name (xxx.homeserver.com) several
> > times with no difference – still unable to access it.
>
> > Someone said that Comcast may be blocking access but I’ve pointed
> > out that I’m also running an IIS Web server on another XP machine
> > with no access problems.
>
> My first observation is that you seem to be port forwarding to an
> address that is part of the BEFSR41's default DHCP range.  Is it
> possible that your device's IP address has changed to something besides
> .102?  Usually a Server device is assigned a fixed IP address that is
> outside of the DHCP range to sidestep this eventuality.
>
> -- John

news:2b73df2e-41e4-4c80-bf1b-7b44f933e30c@y34g2000prb.googlegroups.co
m:

> On Apr 27, 9:09 pm, John Wunderlich <jwunderl***@lycos.com> wrote:
>> "Jim" <jrwo***@comcast.net> wrote
>> innews:#2l7gj1xJHA.1***@TK2MSFTNGP02.ph x.gbl:
>>
>>
>>
>>> While this is not a WHS (Windows Home Server) newsgroup, I’m
>>> hoping someone with networking experience could advise me on
>>> what appears to be an Internet access problem.
>>
>>> I’m operating 3 Windows XP computers on a LAN. I also run a WHS
>>> system which has been going great for many months. BUT just
>>> recently I’ve been unable to access this system via the
>>> Internet. I’ve tried just about everything with no success. The
>>> following ports are forwarded to (198.162.1.102) on my Linksys
>>> BEFS41 V.2 router as per the instructions.
>>
>>> HTTPS            port 443 TCP
>>
>>> HTTP              port 80 TCP
>>
>>> Remote            port 3389 TCP
>>
>>> RDP                port 4125 TCP
>>
>>> I’ve also changed my domain name (xxx.homeserver.com) several
>>> times with no difference – still unable to access it.
>>
>>> Someone said that Comcast may be blocking access but I’ve
>>> pointed out that I’m also running an IIS Web server on another
>>> XP machine with no access problems.
>>
>> My first observation is that you seem to be port forwarding to an
>> address that is part of the BEFSR41's default DHCP range.  Is it
>> possible that your device's IP address has changed to something
>> besides .102?  Usually a Server device is assigned a fixed IP
>> address that is outside of the DHCP range to sidestep this
>> eventuality.
>>
>> -- John
>
> You might forget that some routers offer DHCP IP reservation.
> With IP address reservation, once the router sees the Network
> Interface Card (NIC) MAC address, that network card will always be
> assigned the same IP address.
>

> "Jim" <jrwo***@comcast.net> wrote
> innews:#2l7gj1xJHA.1***@TK2MSFTNGP02.phx.gbl:
>
>
>
> > While this is not a WHS (Windows Home Server) newsgroup, I’m
> > hoping someone with networking experience could advise me on what
> > appears to be an Internet access problem.
>
> > I’m operating 3 Windows XP computers on a LAN. I also run a WHS
> > system which has been going great for many months. BUT just
> > recently I’ve been unable to access this system via the Internet.
> > I’ve tried just about everything with no success. The following
> > ports are forwarded to (198.162.1.102) on my Linksys BEFS41 V.2
> > router as per the instructions.
>
> > HTTPS port 443 TCP
>
> > HTTP port 80 TCP
>
> > Remote port 3389 TCP
>
> > RDP port 4125 TCP
>
> > I’ve also changed my domain name (xxx.homeserver.com) several
> > times with no difference – still unable to access it.
>
> > Someone said that Comcast may be blocking access but I’ve pointed
> > out that I’m also running an IIS Web server on another XP machine
> > with no access problems.
>
> My first observation is that you seem to be port forwarding to an
> address that is part of the BEFSR41's default DHCP range. Is it
> possible that your device's IP address has changed to something besides
> .102? Usually a Server device is assigned a fixed IP address that is
> outside of the DHCP range to sidestep this eventuality.
>
> -- John

"Jack-MVP" <j***@discussgroups.com> wrote in message
news:eauQMg5xJHA.1196@TK2MSFTNGP03.phx.gbl...
> Hi
> If you run a server on another computer using port 80 you can not use it
> on a second computer.
> A port can be Opened only toward one Computer/IP.
> Any computer that uses a port Opening through a Linksys BEFS41 V.2 should
> be configured with a static IP since the Router can Not do IP reservation.
> Beside the Router you have to check WHS Firewall too.
> I do not know what you mean by "domain name (xxx.homeserver.com)".
> But after a change it might take some time for the Remote DNS to update
> itself.
> Jack (MS, MVP-Networking).
>
> "smlunatick" <yves***@gmail.com> wrote in message
> news:2b73df2e-41e4-4c80-bf1b-7b44f933e30c@y34g2000prb.googlegroups.com...
> On Apr 27, 9:09 pm, John Wunderlich <jwunderl***@lycos.com> wrote:
>> "Jim" <jrwo***@comcast.net> wrote
>> innews:#2l7gj1xJHA.1***@TK2MSFTNGP02.phx.gbl:
>>
>>
>>
>> > While this is not a WHS (Windows Home Server) newsgroup, I’m
>> > hoping someone with networking experience could advise me on what
>> > appears to be an Internet access problem.
>>
>> > I’m operating 3 Windows XP computers on a LAN. I also run a WHS
>> > system which has been going great for many months. BUT just
>> > recently I’ve been unable to access this system via the Internet.
>> > I’ve tried just about everything with no success. The following
>> > ports are forwarded to (198.162.1.102) on my Linksys BEFS41 V.2
>> > router as per the instructions.
>>
>> > HTTPS port 443 TCP
>>
>> > HTTP port 80 TCP
>>
>> > Remote port 3389 TCP
>>
>> > RDP port 4125 TCP
>>
>> > I’ve also changed my domain name (xxx.homeserver.com) several
>> > times with no difference – still unable to access it.
>>
>> > Someone said that Comcast may be blocking access but I’ve pointed
>> > out that I’m also running an IIS Web server on another XP machine
>> > with no access problems.
>>
>> My first observation is that you seem to be port forwarding to an
>> address that is part of the BEFSR41's default DHCP range. Is it
>> possible that your device's IP address has changed to something besides
>> .102? Usually a Server device is assigned a fixed IP address that is
>> outside of the DHCP range to sidestep this eventuality.
>>
>> -- John
>
> You might forget that some routers offer DHCP IP reservation.  With IP
> address reservation, once the router sees the Network Interface Card
> (NIC) MAC address, that network card will always be assigned the same
> IP address.

"Jack-MVP" <j***@discussgroups.com> wrote in message
news:eauQMg5xJHA.1196@TK2MSFTNGP03.phx.gbl...
> Hi
> If you run a server on another computer using port 80 you can not use it
> on a second computer.
> A port can be Opened only toward one Computer/IP.
> Any computer that uses a port Opening through a Linksys BEFS41 V.2 should
> be configured with a static IP since the Router can Not do IP reservation.
> Beside the Router you have to check WHS Firewall too.
> I do not know what you mean by "domain name (xxx.homeserver.com)".
> But after a change it might take some time for the Remote DNS to update
> itself.
> Jack (MS, MVP-Networking).
>
> "smlunatick" <yves***@gmail.com> wrote in message
> news:2b73df2e-41e4-4c80-bf1b-7b44f933e30c@y34g2000prb.googlegroups.com...
> On Apr 27, 9:09 pm, John Wunderlich <jwunderl***@lycos.com> wrote:
>> "Jim" <jrwo***@comcast.net> wrote
>> innews:#2l7gj1xJHA.1***@TK2MSFTNGP02.phx.gbl:
>>
>>
>>
>> > While this is not a WHS (Windows Home Server) newsgroup, I’m
>> > hoping someone with networking experience could advise me on what
>> > appears to be an Internet access problem.
>>
>> > I’m operating 3 Windows XP computers on a LAN. I also run a WHS
>> > system which has been going great for many months. BUT just
>> > recently I’ve been unable to access this system via the Internet.
>> > I’ve tried just about everything with no success. The following
>> > ports are forwarded to (198.162.1.102) on my Linksys BEFS41 V.2
>> > router as per the instructions.
>>
>> > HTTPS port 443 TCP
>>
>> > HTTP port 80 TCP
>>
>> > Remote port 3389 TCP
>>
>> > RDP port 4125 TCP
>>
>> > I’ve also changed my domain name (xxx.homeserver.com) several
>> > times with no difference – still unable to access it.
>>
>> > Someone said that Comcast may be blocking access but I’ve pointed
>> > out that I’m also running an IIS Web server on another XP machine
>> > with no access problems.
>>
>> My first observation is that you seem to be port forwarding to an
>> address that is part of the BEFSR41's default DHCP range. Is it
>> possible that your device's IP address has changed to something besides
>> .102? Usually a Server device is assigned a fixed IP address that is
>> outside of the DHCP range to sidestep this eventuality.
>>
>> -- John
>
> You might forget that some routers offer DHCP IP reservation.  With IP
> address reservation, once the router sees the Network Interface Card
> (NIC) MAC address, that network card will always be assigned the same
> IP address.

"Jim" <jrwo***@comcast.net> wrote in message
news:eal1NX6xJHA.3404@TK2MSFTNGP02.phx.gbl...
> Hello Jack,
>
> You were absolutely correct, I was using port 80 on two different computer
> servers (IIS Web and WHS). I removed the one on IIS Web and now WHS access
> is working just fine. Is there any (simple) way around this problem or
> should I just run one server at a time?
>
> MANY, MANY THANKS. I just spent about 3 days trying to figure out this
> problem and you were the only one who understood it!!
>
> Jim
>
>
>
>
> "Jack-MVP" <j***@discussgroups.com> wrote in message
> news:eauQMg5xJHA.1196@TK2MSFTNGP03.phx.gbl...
>> Hi
>> If you run a server on another computer using port 80 you can not use it
>> on a second computer.
>> A port can be Opened only toward one Computer/IP.
>> Any computer that uses a port Opening through a Linksys BEFS41 V.2 should
>> be configured with a static IP since the Router can Not do IP
>> reservation.
>> Beside the Router you have to check WHS Firewall too.
>> I do not know what you mean by "domain name (xxx.homeserver.com)".
>> But after a change it might take some time for the Remote DNS to update
>> itself.
>> Jack (MS, MVP-Networking).
>>
>> "smlunatick" <yves***@gmail.com> wrote in message
>> news:2b73df2e-41e4-4c80-bf1b-7b44f933e30c@y34g2000prb.googlegroups.com...
>> On Apr 27, 9:09 pm, John Wunderlich <jwunderl***@lycos.com> wrote:
>>> "Jim" <jrwo***@comcast.net> wrote
>>> innews:#2l7gj1xJHA.1***@TK2MSFTNGP02.phx.gbl:
>>>
>>>
>>>
>>> > While this is not a WHS (Windows Home Server) newsgroup, I’m
>>> > hoping someone with networking experience could advise me on what
>>> > appears to be an Internet access problem.
>>>
>>> > I’m operating 3 Windows XP computers on a LAN. I also run a WHS
>>> > system which has been going great for many months. BUT just
>>> > recently I’ve been unable to access this system via the Internet.
>>> > I’ve tried just about everything with no success. The following
>>> > ports are forwarded to (198.162.1.102) on my Linksys BEFS41 V.2
>>> > router as per the instructions.
>>>
>>> > HTTPS port 443 TCP
>>>
>>> > HTTP port 80 TCP
>>>
>>> > Remote port 3389 TCP
>>>
>>> > RDP port 4125 TCP
>>>
>>> > I’ve also changed my domain name (xxx.homeserver.com) several
>>> > times with no difference – still unable to access it.
>>>
>>> > Someone said that Comcast may be blocking access but I’ve pointed
>>> > out that I’m also running an IIS Web server on another XP machine
>>> > with no access problems.
>>>
>>> My first observation is that you seem to be port forwarding to an
>>> address that is part of the BEFSR41's default DHCP range. Is it
>>> possible that your device's IP address has changed to something besides
>>> .102? Usually a Server device is assigned a fixed IP address that is
>>> outside of the DHCP range to sidestep this eventuality.
>>>
>>> -- John
>>
>> You might forget that some routers offer DHCP IP reservation.  With IP
>> address reservation, once the router sees the Network Interface Card
>> (NIC) MAC address, that network card will always be assigned the same
>> IP address.
>
>

"Jack-MVP" <j***@discussgroups.com> wrote in message
news:OuUo4lAyJHA.3920@TK2MSFTNGP02.phx.gbl...
> Hi
> Hey, it can happen to the best of us ;).
> You can run a second server provided that it is running on port 80.
> Change the port of IIS, http://support.microsoft.com/kb/149605
> If let say you change it to 61111, open 61111 toward the IP of the server.
> To access it from the outside you type into the browser,
> www.xxx.homeserver.com:61111
> Or if it does not work with the domain xxx.homeserver.com you can use
> another Domain name from a DNS provider that does port redirection at the
> DND Server.
> Jack (MS, MVP-Networking)
>
> "Jim" <jrwo***@comcast.net> wrote in message
> news:eal1NX6xJHA.3404@TK2MSFTNGP02.phx.gbl...
>> Hello Jack,
>>
>> You were absolutely correct, I was using port 80 on two different
>> computer servers (IIS Web and WHS). I removed the one on IIS Web and now
>> WHS access is working just fine. Is there any (simple) way around this
>> problem or should I just run one server at a time?
>>
>> MANY, MANY THANKS. I just spent about 3 days trying to figure out this
>> problem and you were the only one who understood it!!
>>
>> Jim
>>
>>
>>
>>
>> "Jack-MVP" <j***@discussgroups.com> wrote in message
>> news:eauQMg5xJHA.1196@TK2MSFTNGP03.phx.gbl...
>>> Hi
>>> If you run a server on another computer using port 80 you can not use it
>>> on a second computer.
>>> A port can be Opened only toward one Computer/IP.
>>> Any computer that uses a port Opening through a Linksys BEFS41 V.2
>>> should be configured with a static IP since the Router can Not do IP
>>> reservation.
>>> Beside the Router you have to check WHS Firewall too.
>>> I do not know what you mean by "domain name (xxx.homeserver.com)".
>>> But after a change it might take some time for the Remote DNS to update
>>> itself.
>>> Jack (MS, MVP-Networking).
>>>
>>> "smlunatick" <yves***@gmail.com> wrote in message
>>> news:2b73df2e-41e4-4c80-bf1b-7b44f933e30c@y34g2000prb.googlegroups.com...
>>> On Apr 27, 9:09 pm, John Wunderlich <jwunderl***@lycos.com> wrote:
>>>> "Jim" <jrwo***@comcast.net> wrote
>>>> innews:#2l7gj1xJHA.1***@TK2MSFTNGP02.phx.gbl:
>>>>
>>>>
>>>>
>>>> > While this is not a WHS (Windows Home Server) newsgroup, I’m
>>>> > hoping someone with networking experience could advise me on what
>>>> > appears to be an Internet access problem.
>>>>
>>>> > I’m operating 3 Windows XP computers on a LAN. I also run a WHS
>>>> > system which has been going great for many months. BUT just
>>>> > recently I’ve been unable to access this system via the Internet.
>>>> > I’ve tried just about everything with no success. The following
>>>> > ports are forwarded to (198.162.1.102) on my Linksys BEFS41 V.2
>>>> > router as per the instructions.
>>>>
>>>> > HTTPS port 443 TCP
>>>>
>>>> > HTTP port 80 TCP
>>>>
>>>> > Remote port 3389 TCP
>>>>
>>>> > RDP port 4125 TCP
>>>>
>>>> > I’ve also changed my domain name (xxx.homeserver.com) several
>>>> > times with no difference – still unable to access it.
>>>>
>>>> > Someone said that Comcast may be blocking access but I’ve pointed
>>>> > out that I’m also running an IIS Web server on another XP machine
>>>> > with no access problems.
>>>>
>>>> My first observation is that you seem to be port forwarding to an
>>>> address that is part of the BEFSR41's default DHCP range. Is it
>>>> possible that your device's IP address has changed to something besides
>>>> .102? Usually a Server device is assigned a fixed IP address that is
>>>> outside of the DHCP range to sidestep this eventuality.
>>>>
>>>> -- John
>>>
>>> You might forget that some routers offer DHCP IP reservation.  With IP
>>> address reservation, once the router sees the Network Interface Card
>>> (NIC) MAC address, that network card will always be assigned the same
>>> IP address.
>>
>>
>