RE: Client IP/DHCP

Have you checked your DHCP settings, for ex. scope range? lease time? Is this
a Windows XP machine? Do you have the local SP2 firewall on the client
machine enabled? if yes, disable it.




"Matt Stephenson" wrote:

> 1. Yes, several other clients are.
> 2. Yes I can ping and the NIC is connected
>
> As it happens one other machine has just gone the same way in the last hour
> in not getting an IP assigned to it. Had to manually assign one to get it
> back up and running on the network. Don't want to have to do this wth every
> client.
>
> "pQi" wrote:
>
> > Hello,
> >
> > Questions:
> > 1. Are your other clients receiving an IP from your DHCP Server?
> > 2. Can you ping the server from the client pc? if not check * note below
> >
> >
> > *It appears that your media (NIC) is disconnected on the client pc. Check
> > the enternet adapter to make sure you have a link on the card.
> >
> > "Matt Stephenson" wrote:
> >
> > > Question from a newbie so please be understanding.
> > >
> > > I have been running SBS 2003 Premium (with 2 NICs) succuessfully for nearly
> > > the past 6 months. I have recently installed SP1 along with ISA 2004. There
> > > were a few minor problems with FTP which I resolved.
> > >
> > > All the client machines except one are working properly. I can't figure out
> > > what is wrong with this one client machine and hope someone can help?
> > >
> > > Bacially if I assign it a manual IP address and some other settings it
> > > connects to network. It won't automatically assign an IP and when connected
> > > manually the internet and intranet seem very slow.
> > >
> > > Here is the IP config for the Server:
> > >
> > > Windows IP Configuration
> > >
> > > Host Name . . . . . . . . . . . . : server
> > > Primary Dns Suffix . . . . . . . : taylorsyms.local
> > > Node Type . . . . . . . . . . . . : Unknown
> > > IP Routing Enabled. . . . . . . . : Yes
> > > WINS Proxy Enabled. . . . . . . . : Yes
> > > DNS Suffix Search List. . . . . . : taylorsyms.local
> > >
> > > Ethernet adapter Server Local Area Connection:
> > >
> > > Connection-specific DNS Suffix . :
> > > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
> > > Physical Address. . . . . . . . . : 00-0F-1F-F9-F9-7A
> > > DHCP Enabled. . . . . . . . . . . : No
> > > IP Address. . . . . . . . . . . . : 192.168.16.2
> > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > Default Gateway . . . . . . . . . :
> > > DNS Servers . . . . . . . . . . . : 192.168.16.2
> > > Primary WINS Server . . . . . . . : 192.168.16.2
> > >
> > > Ethernet adapter Network Connection 2:
> > >
> > > Connection-specific DNS Suffix . :
> > > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Server
> > > Adapter #3
> > > Physical Address. . . . . . . . . : 00-04-23-AF-2C-2F
> > > DHCP Enabled. . . . . . . . . . . : No
> > > IP Address. . . . . . . . . . . . : 83.100.184.58
> > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > Default Gateway . . . . . . . . . : 83.100.184.57
> > > DNS Servers . . . . . . . . . . . : 192.168.16.2
> > > NetBIOS over Tcpip. . . . . . . . : Disabled
> > >
> > > Here is the problem client IP:
> > >
> > > Windows IP Configuration
> > >
> > > Host Name . . . . . . . . . . . . : STUDIO
> > > Primary Dns Suffix . . . . . . . : taylorsyms.local
> > > Node Type . . . . . . . . . . . . : Hybrid
> > > IP Routing Enabled. . . . . . . . : No
> > > WINS Proxy Enabled. . . . . . . . : No
> > > DNS Suffix Search List. . . . . . : taylorsyms.local
> > >
> > > Ethernet adapter Local Area Connection:
> > >
> > > Media State . . . . . . . . . . . : Media disconnected
> > > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
> > > Connecti
> > > on
> > > Physical Address. . . . . . . . . : 00-12-3F-02-47-BD
> > >
> > > Ethernet adapter Wireless Network Connection:
> > >
> > > Connection-specific DNS Suffix . :
> > > Description . . . . . . . . . . . : Dell Wireless 1350 WLAN Mini-PCI
> > > Card
> > > Physical Address. . . . . . . . . : 00-0B-7D-18-1C-84
> > > Dhcp Enabled. . . . . . . . . . . : No
> > > IP Address. . . . . . . . . . . . : 192.168.16.19
> > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > Default Gateway . . . . . . . . . : 192.168.16.2
> > > DNS Servers . . . . . . . . . . . : 192.168.16.2
> > > Primary WINS Server . . . . . . . : 192.168.16.2
> > >
.

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Fax service on W2003Sbs - client dont send fax
    ... follow the steps to Update the Windows Small Business Server ClientApps ... Please paste the full content of the file to the Newsgroup. ... Microsoft CSS Online Newsgroup Support ... >the same day I do a system restore to monday;-) and client can send fax. ...
    (microsoft.public.windows.server.sbs)
  • Re: Changes in 2005.
    ... The client base I currently have makes transitioning to new technologies ... out over the UK which is Windows 2000 with SP4. ... > VS.NET 2003 does not compile to unmanaged code. ... > the JIT compiler handles the compilation to unmanaged code from IL. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: [opensuse] best file distribution technology for my case?
    ... It must be accessible from Windows linearly, ... It must be accessible from Linux randomly, with no client side ... in HTTP header and charset conversion is done automatically; ... users may not be to happy if it the server collapses under the load. ...
    (SuSE)
Loading