Problem Solved. First of all thank everyone for all your help.
First problem was firewall. Then something weird with DHCP. It was leasing
out and then it was disconnecting. So, when I opened DHCP console it was
saying not connected. But when I clicked on Server underneath DHCP it said
'Running' and then clicking on DHCP it was Active and running and from here
everything worked as it should until reboot.
Googled 'DHCP not connected' and one of the responses suggested right
clicking on DHCP and clicking Authorize. And, that fixed it. Odd - because I
had already authorised it from the menu.
My apologies for wasted everyone's time; I have no formal training. Once
again thanks for all your responses.
Moral of the story - switch DHCP off when swapping BB routers. Many thanks.
"Brian Cryer" <not.here@localhost> wrote in message
news:%23il$...
> What would be useful to know is:
> ipconfig /all
> on one of the workstations - one where you are experiencing the problems.
> At the very least, IP address, subnet mask, default gateway, DNS servers
> and DHCP Server settings.
>
> I would expect to see:
> subnet mask of 255.255.255.0 on clients.
> DNS server (on clients): 192.168.1.100 (i.e. your server)
> Default gateway: IP address of router.
>
> Assuming your DHCP server is running then what IP address are the clients
> getting?
>
> If a workstation has a unique IP address and is on the same subnet, and
> ping times out then (i.) check that the firewall on the server is set to
> allow ICMP echo requests (i.e. pings) and (ii.) that there is a physical
> connection - so everything is plugged in, router is working, lights are on
> (and flashing) at all the network points.
>
> Hope you get to the bottom o fit.
> --
> Brian Cryer
> http://www.cryer.co.uk/brian
>
> "GoldStar" <> wrote in message
> news:6FDC7D50-BC3C-4F3E-B829-...
>> Ping results:
>> If 'ping name' then host not found
>> If 'ping IP' then request timed out
>> DHCP claims it is running.
>>
>> Server address is 192.168.1.100 and with DHCP on the router 'disabled' ie
>> using DHCP on Server, clients get address '169.xx.xx.10 with Mask of
>> 255.255.0.0.
>>
>> I tried setting client at 192.168.1.112, 255.255.255.0 and DNS of
>> 192.168.1.100 I cannot ping although I can see server in Windows
>> Explorer.
>>
>> "Brian Cryer" <not.here@localhost> wrote in message
>> news:...
>>> Please (as already requested by Larry) do
>>> ipconfig /all
>>> and post the results back. That should also show where your clients are
>>> getting their IP addresses from. It will also show what DNS servers are
>>> being used - which for clients should be the IP address of your server.
>>>
>>> Also, if you run the DHCP manager, does it show DHCP running?
>>> --
>>> Brian Cryer
>>> http://www.cryer.co.uk/brian
>>>
>>>
>>> "GoldStar" <> wrote in message
>>> news:BF6CBB25-10EF-419D-AFD5-...
>>>> Yes, I did change the router because the last one packed up but
>>>> settings are exactly same and DHCP on router was turned off before
>>>> being installed. DHCP on SBS2003 is running but not giving out leases -
>>>> because clients cannot see the server.
>>>>
>>>> "Kerry Brown" <*a*m> wrote in message
>>>> news:...
>>>>> SBS will disable DHCP if it sees another DHCP server on the network.
>>>>> Coupled with the name resolution problem I'd suspect another DHCP
>>>>> server is giving out leases with the wrong DNS options. Have you
>>>>> recently added a new router, wireless access point, reset the router
>>>>> etc?
>>>>>
>>>>> --
>>>>> Kerry Brown
>>>>> MS-MVP - Windows Desktop Experience: Systems Administration
>>>>> http://www.vistahelp.ca/phpBB2/
>>>>>
>>>>>
>>>>>
>>>>> "GoldStar" <> wrote in message
>>>>> news
70B4E71-A9E2-4E1B-A407-...
>>>>>> SBS2003 with 5 PCs - I cannot ping with IP address or Names although
>>>>>> clients can read directory on server. Up until yesterday DHCP was
>>>>>> dishing out leases and today, it didn't. Gave up in the end.
>>>>>>
>>>>>> Any pointer as to where I could find info as to what could be wrong
>>>>>
>>>>
>>>
>>
>