RE: Email and Internat connection wizard

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

anonymous_at_discussions.microsoft.com
Date: 04/06/04


Date: Mon, 5 Apr 2004 20:59:04 -0700

Thanks Ray,

I have checked the GUID's and they all match the internal
nic. I noticed two other interfaces listed in the
registry as well (making four), both with ip address
0.0.0.0, is that right?

I was trying to run the CEICW again as the clients are
having intermittant browsing problems not experienced
before the server was installed. I have tested the dsl
connection and everything seems okay.
Since yesterday I have reconfigured the server so that it
only uses one network card and no longer firewalls the
clients behind it. The clients now use (and are
firewalled by) the dsl router as their gateway. The
server and clients sit on the same subnet behind the dsl
router. They are still configured to use the SBS server
for DNS.
The clients still experience intermittant problems
browsing. they enter the address and the 'This page
cannot be displayed' page appears, if they click on
refresh the page will appear.
I have reconfigured one client pc with external dns (same
dns servers being used as forwarders) to see if it fixes
the browsing problems, so far this pc has had no more
problems (only 2 hours so far) - so it is looking like a
DNS issue, are there any known DNS issues with SBS2003?

Thanks again,
Ryan
>-----Original Message-----
>Did you make any changes to the network card? Like swap
it or add a new one?
>
>Resolution:
>============
>Check
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpi
p\Parameters\Interf
>aces\{GUID}. Identify the GUID of the internal network
card.
>
>Make sure these keys are set to the GUID of the internal
network card
>
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer
\LANNIC
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer
\Connectivity\ICW\L
>ast_1st_Nic_Guid
>
>After you make the changes, start the CEICW again.
>
>Ray Fong
>Microsoft SBS Product Support
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>>
>>Hi All,
>>
>>Im trying to run the EICW again and am getting the
>>following message:
>>
>>titled:"Configure Email and ICW"
>>"The wizard caanot set the DHCP scope options. Ensure
>>that the DHCP service is running and that a scope is
>>defined. Alternatively, disable the DHCP service
>>manually, and then configure your client computer IP
>>address properties. For more information......see Help
>>and Support"
>>
>>As far as I am aware, the DHCP server is functioning
OK.
>>Any ideas?
>>
>>Thanks in advance,
>>Ryan
>>
>
>.
>



Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)