PHWinfo - Afficher un message

08/06/2007, 15h19

Read inline please.

In news:87DE75E0-FFBC-479D-9071-3FE3E830744A@microsoft.com,
Andy Langley <Andy Langley@discussions.microsoft.com> typed:
> Hi I have Windows Server 2003 SBS running, its been configured and
> working
> fine for about 18 months but all of a sudden last night all the
> clients have
> been disconnected and now can no longer see the server, or connect to
> it

When you say "no longer see" are you referring to My Network Places?

Since this is SBS, I assume it is multihomed?
SBS accepts being Multihomed better than other Windows Servers, but still
requires some special configuration. In Control Panel open Network
Connections,
1. in the Advanced Menu, select Advanced settings, move the internal NIC to
the top of the connections pane, and make sure File sharing and Client for
MS Networks is enabled only on the internal interface.
2. Enable NetBIOS over TCP/IP only on the internal NIC.
3. "Register this connections addresses in DNS" only on the internal NIC.
4. As with all Members of an AD domain, the only DNS server's IP you can use
is the internal NIC IP address of the DC or another internal DNS that has a
zone for the AD Domain.
5. If SBS has two NICs but only one is used and connected, make sure the
unused NIC is disabled and not just left in a disconnected state, it will
still attempt to obtain an IP address and will be assigned an APIPA
(169.254.x.x address)
6. In the DNS management console, on the server properties sheet, interfaces
tab, listen only on the IP of the internal interface. And check that the
Root hints are resolved and contain only the root hint servers.
7. Make sure these services are set to Automatic and running: DHCP Client
Service, and TCP/IP NetBIOS er Service (many people don't understand
that these are requiired services and try to disable them) There are many
other required services, these are the two most commonly disabled required
services. Running the cmd 'net start' (without quortes) will list the
running services

Install the Support Tools from the CD and run these cmd line tools netdiag
and dcdiag for a list of options use /h. Start with using netdiag /fix and
dcdiag /fix. Post errors.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================

08/06/2007, 15h19	#2
Kevin D. Goodknecht Sr. [MVP] Messages: n/a Hébergeur:	Re: Sudden problem Read inline please. In news:87DE75E0-FFBC-479D-9071-3FE3E830744A@microsoft.com, Andy Langley <Andy Langley@discussions.microsoft.com> typed: > Hi I have Windows Server 2003 SBS running, its been configured and > working > fine for about 18 months but all of a sudden last night all the > clients have > been disconnected and now can no longer see the server, or connect to > it When you say "no longer see" are you referring to My Network Places? Since this is SBS, I assume it is multihomed? SBS accepts being Multihomed better than other Windows Servers, but still requires some special configuration. In Control Panel open Network Connections, 1. in the Advanced Menu, select Advanced settings, move the internal NIC to the top of the connections pane, and make sure File sharing and Client for MS Networks is enabled only on the internal interface. 2. Enable NetBIOS over TCP/IP only on the internal NIC. 3. "Register this connections addresses in DNS" only on the internal NIC. 4. As with all Members of an AD domain, the only DNS server's IP you can use is the internal NIC IP address of the DC or another internal DNS that has a zone for the AD Domain. 5. If SBS has two NICs but only one is used and connected, make sure the unused NIC is disabled and not just left in a disconnected state, it will still attempt to obtain an IP address and will be assigned an APIPA (169.254.x.x address) 6. In the DNS management console, on the server properties sheet, interfaces tab, listen only on the IP of the internal interface. And check that the Root hints are resolved and contain only the root hint servers. 7. Make sure these services are set to Automatic and running: DHCP Client Service, and TCP/IP NetBIOS er Service (many people don't understand that these are requiired services and try to disable them) There are many other required services, these are the two most commonly disabled required services. Running the cmd 'net start' (without quortes) will list the running services Install the Support Tools from the CD and run these cmd line tools netdiag and dcdiag for a list of options use /h. Start with using netdiag /fix and dcdiag /fix. Post errors. -- Best regards, Kevin D. Goodknecht Sr. [MVP] Hope This s =================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue, to respond directly to me remove the nospam. from my email address. =================================== http://www.lonestaramerica.com/ http://support.wftx.us/ http://message.wftx.us/ =================================== Use Outlook Express?... Get OE_Quotefix: It will strip signature out and more http://home.in.tum.de/~jain/software/oe-quotefix/ =================================== Keep a back up of your OE settings and folders with OEBackup: http://www.oe.com/OEBackup/Default.aspx ===================================