Non XP Pro clients unable to use HTTPS and Email

I have a Windows 2003 small business server in my home, that handles DHCP,
exhange, and hosts a simple website, so I can view my email while away from
the house on my laptop. These functions it does just fine as well (thanks to
www.dyndns.com).

The network topography has a standard cable modem, into a wireless router,
with the server and all of the clients connected to the router. DHCP is
turned off on the router, since the server does that.

The server has 4 computers assigned, and 3 users. Each server defined
computer has Win XP Pro.

My kids also have laptops, with just Windows XP Home on them. These 2
laptops are not defined within the Server, though the server's DHCP knows
about them. The trouble is, these laptops cannot access https websites (port
443), nor can they download or send email (ports 25/110). They always get
some type of cannot connect error message.

It seems to me that the server is blocking most (some) of the access from
the Win XP Home laptops to the outside world...that is, all but http: access
(port 80). I've looked at every server setting I can find, and I can't find
anything that should be blocking it. Right now, Windows Firewall and RRAS
are completely turned off and still the problem persists. No 3rd party
firewall or virus programs run on my server at all.

Where else is there a setting that blocks ports or otherwise blocks access?
If I stop using the server for DHCP, could that possibly fix the problem?

I'm resistant to upgrade the kids laptops to XP Pro, simply do to
cost...particularly, because it seems totally unnecessary.

Thanks in advance.
--
Steve Belt

You would probably get a better response by posting in the sbs
newsgroup. SBS is quite different from the standard version of server 2003.

My guess is that the problem is the fact that XP Home cannot join a
domain, and sbs server is a domain-based system.

Steve Belt wrote:
> I have a Windows 2003 small business server in my home, that handles
> DHCP, exhange, and hosts a simple website, so I can view my email
> while away from the house on my laptop. These functions it does just
> fine as well (thanks to www.dyndns.com).
>
> The network topography has a standard cable modem, into a wireless
> router, with the server and all of the clients connected to the
> router. DHCP is turned off on the router, since the server does that.
>
> The server has 4 computers assigned, and 3 users. Each server defined
> computer has Win XP Pro.
>
> My kids also have laptops, with just Windows XP Home on them. These 2
> laptops are not defined within the Server, though the server's DHCP
> knows about them. The trouble is, these laptops cannot access https
> websites (port 443), nor can they download or send email (ports
> 25/110). They always get some type of cannot connect error message.
>
> It seems to me that the server is blocking most (some) of the access
> from the Win XP Home laptops to the outside world...that is, all but
> http: access (port 80). I've looked at every server setting I can
> find, and I can't find anything that should be blocking it. Right
> now, Windows Firewall and RRAS are completely turned off and still
> the problem persists. No 3rd party firewall or virus programs run on
> my server at all.
>
> Where else is there a setting that blocks ports or otherwise blocks
> access? If I stop using the server for DHCP, could that possibly fix
> the problem?
>
> I'm resistant to upgrade the kids laptops to XP Pro, simply do to
> cost...particularly, because it seems totally unnecessary.
>
> Thanks in advance.