New SBS 2003 computer no longer connects

Customer received SBS 2003 Standard Server installed and partially setup we
were asked to finish the setup of accounts, etc. Server seemed OK apart from
some odd naming convention and all the accounts went on and we set up the 2
desktops and 4 laptops - all done with the connectcomputer - all OK. Next day
set up VPN and Remote desktop all OK and working. After leaving, the Boss
returned (missing when we did the VPN, etc) and his laptop would not connect
to the server or the internet. At present the DHCP is supplied by the router.
We tried everything we could think of obvious cabling etc. No luck.
Disconnected it from the Domain back to workgroup and then with the
connectcomputer - could not find the server - said network path not found. It
shows on the server but error again with network path. The server can ping
the laptop OK - strange. Could the VPN issue have anything to do with this.
We really would appreciate any help.

Lanwench
Fri Mar 28 06:35:38 PDT 2008

Cheryl <cheryl@discussions.microsoft.com> wrote:
> Customer received SBS 2003 Standard Server installed and partially
> setup we were asked to finish the setup of accounts, etc.

Note for future installs ....it's a good idea to wipe/reinstall a
preinstalled server to make sure it's set up properly.

> Server
> seemed OK apart from some odd naming convention

Such as ?

> and all the accounts
> went on and we set up the 2 desktops and 4 laptops - all done with
> the connectcomputer - all OK. Next day set up VPN and Remote desktop
> all OK and working. After leaving, the Boss returned (missing when we
> did the VPN, etc) and his laptop would not connect to the server or
> the internet. At present the DHCP is supplied by the router.

Turn that off, and make sure SBS handles DHCP. You'll need to install and
configure it manually (unless re-running some of the wizards will do this).

Basics: set the scope to xxx.xxx.xxx.1 - xxx.xxx.xxx.254
Set exclusions for .1 - .50
(make sure your server/router/printers or other statics are in the excluded
range)
I also like to exclude something at the end .... .200 - .254 - for future
use

Set the domain name to your AD domain name (mydomain.local)
Set the DNS server to the SBS server's LAN IP
Set the WINS server to the SBS server's LAN IP (and set the node type to
0x8, for hybrid node)

> We tried
> everything we could think of obvious cabling etc. No luck.
> Disconnected it from the Domain back to workgroup and then with the
> connectcomputer - could not find the server - said network path not
> found. It shows on the server but error again with network path. The
> server can ping the laptop OK - strange. Could the VPN issue have
> anything to do with this. We really would appreciate any help.

No, not VPN. DNS, more likely.

Merv
Fri Mar 28 06:52:08 PDT 2008

Try disabling the wireless NIC in the laptop and then re-connecting to the
SBS server using ConnectComputer. And as Lanwench mentioned, make the SBS
server the DHCP Server for the LAN.

--
Merv Porter [SBS-MVP]
============================

"Cheryl" <cheryl@discussions.microsoft.com> wrote in message
news:23AA3BDE-2D63-4D36-8464-F4BC46E86F7F@microsoft.com...
> Customer received SBS 2003 Standard Server installed and partially setup
> we
> were asked to finish the setup of accounts, etc. Server seemed OK apart
> from
> some odd naming convention and all the accounts went on and we set up the
> 2
> desktops and 4 laptops - all done with the connectcomputer - all OK. Next
> day
> set up VPN and Remote desktop all OK and working. After leaving, the Boss
> returned (missing when we did the VPN, etc) and his laptop would not
> connect
> to the server or the internet. At present the DHCP is supplied by the
> router.
> We tried everything we could think of obvious cabling etc. No luck.
> Disconnected it from the Domain back to workgroup and then with the
> connectcomputer - could not find the server - said network path not found.
> It
> shows on the server but error again with network path. The server can ping
> the laptop OK - strange. Could the VPN issue have anything to do with
> this.
> We really would appreciate any help.

cheryl
Fri Mar 28 06:55:38 PDT 2008

Many thanks for your speedy reply will try out on Monday and let you know the
outcome. Have a great weekend and thanks again.

"Lanwench [MVP - Exchange]" wrote:

> Cheryl <cheryl@discussions.microsoft.com> wrote:
> > Customer received SBS 2003 Standard Server installed and partially
> > setup we were asked to finish the setup of accounts, etc.
>
> Note for future installs ....it's a good idea to wipe/reinstall a
> preinstalled server to make sure it's set up properly.
>
> > Server
> > seemed OK apart from some odd naming convention
>
> Such as ?
>
> > and all the accounts
> > went on and we set up the 2 desktops and 4 laptops - all done with
> > the connectcomputer - all OK. Next day set up VPN and Remote desktop
> > all OK and working. After leaving, the Boss returned (missing when we
> > did the VPN, etc) and his laptop would not connect to the server or
> > the internet. At present the DHCP is supplied by the router.
>
> Turn that off, and make sure SBS handles DHCP. You'll need to install and
> configure it manually (unless re-running some of the wizards will do this).
>
> Basics: set the scope to xxx.xxx.xxx.1 - xxx.xxx.xxx.254
> Set exclusions for .1 - .50
> (make sure your server/router/printers or other statics are in the excluded
> range)
> I also like to exclude something at the end .... .200 - .254 - for future
> use
>
> Set the domain name to your AD domain name (mydomain.local)
> Set the DNS server to the SBS server's LAN IP
> Set the WINS server to the SBS server's LAN IP (and set the node type to
> 0x8, for hybrid node)
>
> > We tried
> > everything we could think of obvious cabling etc. No luck.
> > Disconnected it from the Domain back to workgroup and then with the
> > connectcomputer - could not find the server - said network path not
> > found. It shows on the server but error again with network path. The
> > server can ping the laptop OK - strange. Could the VPN issue have
> > anything to do with this. We really would appreciate any help.
>
> No, not VPN. DNS, more likely.
>
>
>
>

cheryl
Wed Apr 02 01:19:00 PDT 2008

As suggested changed the DHCP on to server (as we would have done) and now
all seems fine. Also found a load of odd DHCP and WINS entries once enabled
(down to the people who installed the software.) Many thanks for your help,
also disabled the wireless on the laptop (other members suggestion).


"Lanwench [MVP - Exchange]" wrote:

> Cheryl <cheryl@discussions.microsoft.com> wrote:
> > Customer received SBS 2003 Standard Server installed and partially
> > setup we were asked to finish the setup of accounts, etc.
>
> Note for future installs ....it's a good idea to wipe/reinstall a
> preinstalled server to make sure it's set up properly.
>
> > Server
> > seemed OK apart from some odd naming convention
>
> Such as ?
>
> > and all the accounts
> > went on and we set up the 2 desktops and 4 laptops - all done with
> > the connectcomputer - all OK. Next day set up VPN and Remote desktop
> > all OK and working. After leaving, the Boss returned (missing when we
> > did the VPN, etc) and his laptop would not connect to the server or
> > the internet. At present the DHCP is supplied by the router.
>
> Turn that off, and make sure SBS handles DHCP. You'll need to install and
> configure it manually (unless re-running some of the wizards will do this).
>
> Basics: set the scope to xxx.xxx.xxx.1 - xxx.xxx.xxx.254
> Set exclusions for .1 - .50
> (make sure your server/router/printers or other statics are in the excluded
> range)
> I also like to exclude something at the end .... .200 - .254 - for future
> use
>
> Set the domain name to your AD domain name (mydomain.local)
> Set the DNS server to the SBS server's LAN IP
> Set the WINS server to the SBS server's LAN IP (and set the node type to
> 0x8, for hybrid node)
>
> > We tried
> > everything we could think of obvious cabling etc. No luck.
> > Disconnected it from the Domain back to workgroup and then with the
> > connectcomputer - could not find the server - said network path not
> > found. It shows on the server but error again with network path. The
> > server can ping the laptop OK - strange. Could the VPN issue have
> > anything to do with this. We really would appreciate any help.
>
> No, not VPN. DNS, more likely.
>
>
>
>

Lanwench
Wed Apr 02 06:26:05 PDT 2008

Cheryl <cheryl@discussions.microsoft.com> wrote:
> As suggested changed the DHCP on to server (as we would have done)
> and now all seems fine. Also found a load of odd DHCP and WINS
> entries once enabled (down to the people who installed the software.)
> Many thanks for your help, also disabled the wireless on the laptop
> (other members suggestion).

Glad you've got it working now - thanks for posting back.
>
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Cheryl <cheryl@discussions.microsoft.com> wrote:
>>> Customer received SBS 2003 Standard Server installed and partially
>>> setup we were asked to finish the setup of accounts, etc.
>>
>> Note for future installs ....it's a good idea to wipe/reinstall a
>> preinstalled server to make sure it's set up properly.
>>
>>> Server
>>> seemed OK apart from some odd naming convention
>>
>> Such as ?
>>
>>> and all the accounts
>>> went on and we set up the 2 desktops and 4 laptops - all done with
>>> the connectcomputer - all OK. Next day set up VPN and Remote desktop
>>> all OK and working. After leaving, the Boss returned (missing when
>>> we did the VPN, etc) and his laptop would not connect to the server
>>> or the internet. At present the DHCP is supplied by the router.
>>
>> Turn that off, and make sure SBS handles DHCP. You'll need to
>> install and configure it manually (unless re-running some of the
>> wizards will do this).
>>
>> Basics: set the scope to xxx.xxx.xxx.1 - xxx.xxx.xxx.254
>> Set exclusions for .1 - .50
>> (make sure your server/router/printers or other statics are in the
>> excluded range)
>> I also like to exclude something at the end .... .200 - .254 - for
>> future use
>>
>> Set the domain name to your AD domain name (mydomain.local)
>> Set the DNS server to the SBS server's LAN IP
>> Set the WINS server to the SBS server's LAN IP (and set the node
>> type to 0x8, for hybrid node)
>>
>>> We tried
>>> everything we could think of obvious cabling etc. No luck.
>>> Disconnected it from the Domain back to workgroup and then with the
>>> connectcomputer - could not find the server - said network path not
>>> found. It shows on the server but error again with network path. The
>>> server can ping the laptop OK - strange. Could the VPN issue have
>>> anything to do with this. We really would appreciate any help.
>>
>> No, not VPN. DNS, more likely.