Jump to content

Karen M

Members
  • Gesamte Inhalte

    24
  • Registriert seit

  • Letzter Besuch

Über Karen M

  • Geburtstag 22.05.1968

Profile Fields

  • Member Title
    Newbie

Fortschritt von Karen M

Explorer

Explorer (4/14)

  • Erste Antwort
  • Engagiert
  • Erster eigener Beitrag
  • Eine Woche dabei
  • Einen Monat dabei

Neueste Abzeichen

10

Reputation in der Community

  1. nun hab ich mir eine Vollversion für w2K Server organisiert, eine neue 2000-Domäne aufgesetzt (alles schön). Update auf SP4 ,DC für Schemaänderungen vorbereitet, Schema geändert und wieder zurückgeändert. (Also DARF ich Schema ändern) Unternehmensinitialisierung auf dem DC ausgeführt und PENG! geht wieder nicht!!! ISA 2000 ist immer noch Testversion - ansonsten kann man doch nichts falsch machen ?!? Hab ich irgendetwas Kleines, Doofes übersehen ? Werde mich jetzt wohl nicht länger an dem Kram aufhalten und NLB und Unternehmensrichtlinien etc. doch nur theoretisch durcharbeiten (können) :mad: Vielleicht habt Ihr ja noch konstruktive Tips? danke und lG Karen
  2. bin ja flott dabei.. hab mir nen W2k DC aufgesetzt -Schemaänderungen lt o.g. Anleitung erlaubt, und Unternehmensinitialisierung gestartet ... und wieder kann ich das Schema nicht ändern... :shock: ich habe auch nur ein administratives Konto - den Built-In Administrator -der darf das Schema auch ändern. Muß wohl doch an den Testversionen liegen.Wie soll man sich da ordentlich auf Prüfungen vorbereiten Gruß Karen
  3. Hallo Grizzly, Danke für die schnelle Antwort.Klar hab ich erst mal überall gesucht... Mein ISA läuft ja auch auf einem Windows 2000 Server.Ich hatte alle Artikel so aufgefaßt, dass man den ISA nicht direkt auf Windows 2003 installieren kann, da die Testversion halt nicht updatefähig ist. Im Schulungsraum hatten wir DC´s mit Windows 2000 Server...allerdings wurden dort m.E. die Vorbereitungen für das Ändern des Schemas nicht sorgfältig getroffen ( ich war leider nicht immer da) Du meinst also ich soll noch mal einen 2000 DC aufsetzen und dann funzt das alles ? Gruß Karen
  4. Hallo Ihr lieben Boardmitglieder, auch wenn die Beiträge vorher schon alt sind, möchte ich das Thema noch einmal aufgreifen, dass der DC das neue Schema vom ISA 2000 nicht mag. Auch ich bereite mich gerde auf die 70-227 vor... Ich habe 5 Installationen in einem Schulungsraum gesehen - kein Schemaupdate hat funktioniert. Nun wollte ich unbedingt zu Hause die Konfigurationen mit Unternehmensrichtlinien testen. Habe folgende Konfiguration: 1 DC W2003 Server Testversion 180 Tage 2. W2k Server als Member mit ISA 2000 beides Testversionen Bin natürlich Schemaadmin und habe den DC auch sorgfältig für Schemaänderungen vorbereitet. http://www.msisafaq.de/Anleitungen/2000/Installation/ArrayInstallation.htm ( habe mich auch mit den Abweichungen bei W2003 befasst -->Reg-Einträge gesetzt) Trotzdem wird die Schemaänderung beharrlich verweigert. Nun habe ich die Befürchtung, dass man mit den ganzen Testversionen keine Schemaupdates durchführen kann Vielleicht weiß ja jemand was? Danke schon mal Karen
  5. Using Office 2000 running on Windows XP operating system to connect to a Windows WebDAV share is not supported. - When using Microsoft Office on Windows XP, use Office's WebDAV redirector rather than the Windows XP file redirector. In general, when using Microsoft Office products it is best to use files represented by their HTTP names instead of their UNC paths. For example, use http://<Device Name>/<Virtual Root>/<File Name> instead of \\<Device Name>\<Virtual Root>\<File Name>. Note: - Disabling the WebClient has no effect on Internet WWW Browsing, it is only used for Web Distributed Authoring and Versioning (WebDAV) connections. - When the Universal Naming Conventions (UNC) file name is used, the redirector will use SMB, WebDAV, or a combination of the two depending on what is available on the server. When an application attempts to open a file that exists on a network, the I/O Manager passes the request to a system component called the Multiple UNC Provider (MUP) which sits logically above all the redirectors. When a network path is passed to MUP, it polls all the registered redirectors to determine if they understand the path. The redirectors in turn contact the server to establish if the path is valid for the specific protocol. If the server can satisfy the connection then the redirector will return success back the MUP. If not, then the redirector returns a failure. All the future File I/O requests for this file are passed to the redirector that accepted the path. If more than one redirector accepts the path, MUP picks the one with the highest priority (as defined in the registry). 171386 Connectivity Delay with Multiple Redirectors Installed http://support.microsoft.com/?id=171386 - URLScan blocks WebDAV requests by default Before you install URLScan 2.5, see the white paper on the following Microsoft Web site: http://www.microsoft.com/technet/security/tools/tools/URLScan.asp - Registry Settings: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\ServerNotFoundCacheLifeTimeInSec Type: REG_DWORD Value: Default 60 (Decimal) No Max and No Min To change the WebDAV timeout: The timeout represents the number of seconds WebDAV will wait for WinInet after issuing a request (e.g. Get file, put file). The timeout is stored in the following registry key: \HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRxDAV\Parameters\RequestTimeoutInSec Value: Default 600 (decimal) seconds = 10 minutes REFERENCES =========== 171386.KB.EN-US Connectivity Delay with Multiple Redirectors Installed 312181.KB.EN-US Long Delays When You Open Resources on a DFS Share Windows SP1 317506.KB.EN-US You May Not Be Able to Log On to the Domain with VPN If a Winsock Proxy 810401.KB.EN-US "Local Device Name Is Already in Use" Error Message After You Interrupt preSP2 830561.KB.EN-US WD2002: Documents Take a Long Time to Open When They Have Attached 823372.KB.EN-US Your Word Documents Take a Long Time to Open When They Have Attached preSP2 16-Jul-2003 21:59 5.1.2600.1248 62,976 Webclnt.dll X86 817929.KB.EN-US Files Do Not Appear When You Use WebDAV to Add a Network Place Shortcut 812924.KB.EN-US Access to Windows NT 4.0 or Windows 2000 Share May Stop Responding IE6 829909.KB.EN-US I: KB ARTICLE IDEA: Delay when accessing network resources with Windows 826286 New User Cannot Access the Internet and Proxy Settings Are Blank preSP2 03-Mar-2003 12:58 5.1.2600.1178 61,952 Webclnt.dll 320507.KB.EN-US Internet Explorer Does Not Retry Bad Proxy Server for 30 Minutes 271361.KB.EN-US How to Disable Internet Explorer Automatic Proxy Caching 819961 How to Configure Client Proxy Server Settings by Using a Registry File 262981 Internet Explorer Uses Proxy Server for Local IP Address Even if the 209252 Maximum Number of Characters That Can Be Specified in the Proxy External Web Links http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windo wsserver2003/proddocs/standard/pub_dav_aboutwebdav.asp Internet Explorer Administration Kit 6 Service Pack 1 http://www.microsoft.com/windows/ieak/downloads/ieak6/ieak6sp1.asp fertich :-))) !!!
  6. In Windows XP and later, the Windows file redirector has a built-in WebDAV client. Microsoft Office 2000 and Microsoft Office XP adn 2003 have built-in WebDAV redirectors, working independent from the WebClient service. - Windows XP WebDAV Redirector Windows XP includes a new component - the WebDAV redirector, which allows applications on Windows XP to connect to the Internet, and to natively read and write data on the Internet. The WebDAV protocol is an extension to Hypertext Transfer Protocol (HTTP) that allows data to be written to HTTP targets such as the Microsoft MSN? Web Communities. The WebDAV redirector provides file system-level access to these servers in the same that the existing redirector provides access to SMB/CIFS servers. One way to access a WebDAV share is to use the net use command, for example: NET USE * http://webserver/davscratch'>http://webserver/davscratch To connect to an MSN Community, use http://www.msnusers.com/yourcommunityname/files/ as the target. The credentials you need in this case are your Passport credentials; enter these details in the Connect Using Different User Name dialog if you are using mapped network drive, or use the /u: switch with the net use command. For example: NET USE http://www.msnusers.com/fooname/files /u:yourpassportaccount@hotmail.com - WinXP: The WebClient service is used if you connect a WebFolders without specifying a port, i.e. http://webserver/davscratch A network trace will show in the HTTP header: HTTP: User-Agent = Microsoft-WebDAV-MiniRedir/5.1.2600 Office: However when using the syntax including a port number, you are connecting via Office' WebDAV http://webserver:80/davscratch A network trace will show: HTTP: User-Agent = Microsoft Data Access Internet Publishing Provider DAV Note: this may or may not show as "HTTP" traffic in netmon because the proxy port can vary. The following list shows some of the known interoperability issues with WebDAV: - On Windows 2003 Server, the WebDAV client is not enabled by default for security reasons. You need to enable the WebClient service. - Using Microsoft Office 2000 to connect to a Windows WebDAV share is only supported if Office 2000 is running on Windows 2000 or earlier operating systems.
  7. Note: For the current logged on user, the registry location is at: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings] ProxyOverride will be assigned the entries of the proxy exception list which you can type into the Exceptions area: 1. In Internet Explorer, on the Tools menu, click Internet Options. 2. On the Connections tab, click LAN Settings. 3. Click Advanced, and type the appropriate information in the Exceptions area. Note: The values of these keys can bee seen in a WinMSD report under 'Internet Explorer' -> Connectivity You can also use the Microsoft Internet Explorer Administration Kit (IEAK) to configure proxy server settings on client computers. For additional information about IEAK, visit the following Microsoft Web site: http://www.microsoft.com/windows/ieak/downloads/ieak6/ieak6sp1.asp Note: When using a .PAC file, WebDAV requests are generated if the .pac file includes: function FindProxyForURL(url, host) { } You can modify the .pac to avoid WebDAV traffic: function FindProxyForURL(url, host) { if (shExpMatch(host, "DCNAME*")) { return "DIRECT"; } WORKAROUND ========== - Stop the service that listens on TCP port 80 on the DC as long as it does not need to run. or - Disable the WebClient service on the Windows XP client. To check the status, or to disable the WebClient service on a WebDAV client machine: 1. From the Start menu, point to Administrative Tools, and click Computer Management . 2. In the details pane, double-click Services and Applications. 3. Double-click Services. 4. Scroll down, right-click WebClient, and click Properties. 5. In the Startup type list box, click Disabled. 6. Click Apply. 7. Click OK. Note: You can savely disable the WebClient service, as long as you do not need to modify or write files on Web Distributed Authoring and Versioning (WebDAV) servers. Windows 2000 does not have implemented the WebClient service. Windows Server 2003 has turned off WebClient service by default, see 812519 Services That Are Turned Off by Default in Windows Server 2003 http://support.microsoft.com/?id=812519 There are some alternatives to WebClient, i.e If you are running Windows XP, follow these steps: 1. Disable the WebClient service. 2. Install a program that uses Web folders. For example, install Microsoft Office XP or later on the client. 3. Delete your original Network Place. 4. Create a new Network Place. For more information see KB817929. STATUS ======= Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article MORE INFORMATION ================= The WebClient service enables Windows-based programs to create, access, and modify Internet-based files using Win32 APIs. If this service is stopped, these functions will not be available. Turning off WebClient service will stop the WebDAV redirector. You will not be able to do a 'net use', dir, copy, rename etc to a web server. Also 'Add Network Place' will not work to a Web DAV location and you will not be able to use Publishing Wizard to MSN Communities. However, you can still continue to use SMB servers.
  8. RESOLUTION =========== 1. Verify that you have applied Windows XP Service Pack 1 2. Configure Internet Explorer's proxy server settings to "Bypass proxy for local addresses" and ensure that local Intranet FQDNs are entered in the exclusion list. 3. Change the order of 'Network Providers' To verify and change the Network Provider Order a. On the desktop, right-click 'My Network Places', and then click Properties. b. On the Advanced menu, click 'Advanced Settings'. c. Click the 'Provider Order' tab. d. In 'Network Providers', click the 'Web Client Network' provider, and then click the Down Arrow button so that it is the last one in the list. (Ensure that 'Microsoft Windows Network' is listed with higher priority.) e. Click "OK" 'Web Client Network' should be at the bottom by default. You can also find the Provider order in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order\ProviderOrder The default order for the ProviderOrder value is: RDPNP,LanmanWorkstation,WebClient 4. Apply latest WebClient hotfix (KB823372, Webclnt.dll V5.1.2600.1248, 16-Jul-2003, or soon Q824383) on the Windows XP system. After you install this fix, follow these steps to set the ServerNotFoundCacheLifeTimeInSec registry key as documentet in KB823372. 826286 New User Cannot Access the Internet and Proxy Settings Are Blank http://support.microsoft.com/?id=826286 5. If you have deployed Internet Explorer using IEAK with Internet Settings set on the .DEFAULT registry hive: IAEK is the Internet Explorer Administration Kit to allow for scripted install and configuration of Internet Explorer. The WebClient service uses the .DEFAULT registry setting. So every time we try to make a web client request, we get sent to the proxy. The proxy request eventually times out. Windows XP boots up and looks for a computer policy to apply (policy file ntconfig.pol ). a. MUP is notified that the client needs to connect to domaincontroller1.domain.com (or just a netbios name of the logon server) and informs available redirectors. b. WebClient tries to handle the request. c. WinInet loads and reads the proxy configuration from the registry: [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings] ProxyEnable ProxyOverride ProxyServer d. If these three keys are set to use a proxy server WinInet sends request to the proxy server. This may fail with a time-out (this can vary depending on proxy dns cache) and the web client will return a negative response to the MUP. In this case you can workaround by providing the DC's netbios name (- or depending on the name that is seen in the WebDAV request - the domain name for the internal domain) for the ProxyOverride value, i.e. "ProxyEnable"=1 "ProxyServer"="http://<ProxyServername>:<PortNumber>" "ProxyOverride"="*.intranet; domaincontroller1;*.domain.com;10.10.*;<local>" where <ProxyServername> is the name of your proxy server, and <PortNumber> is the TCP port number for HTTP, in most cases it is 80 or 8080. Key | Value ProxyEnable | 0 = Manual proxy detection is disabled. 1 = Manual proxy detection is enabled. ProxyServer | The name and the port of the proxy server. ProxyOverride | The Domain Name System (DNS) addresses, separated by semi-colons, that should not be passed on to the proxy server. You can use the value <local> to bypass the proxy server for local addresses. If you include this value, it should be the final value in the string.
  9. Hallo liebe Boardmitglieder, ich hatte auch das Problem ... nach Domänenmigration an 50 Workstations. Deshalb habe ich mich schon kümmern müssen... Diese Informationen werden allen helfen, zu verstehen und entsprechend zu konfigurieren. Liebe Grüße, Karen ------------------------------------------------------------------------------ The information in this article applies to: - Microsoft Windows XP 64-Bit Edition - Microsoft Windows XP Professional - Microsoft Windows XP Professional SP1 (Version: SP1) - Microsoft Windows XP Tablet PC Edition ------------------------------------------------------------------------------- SUMMARY ======== Slow logon to domain from Windows XP client machine if WebClient is running. SYMPTOMS ========= - At logon after you hit Control-Alt-Delete a Windows XP machine may appear to hang at various places, from processing group policy to waiting at a blank (by default blue) screen before the desktop icons appear. This can last several minutes (up to 15 minutes, entries in the MUP cache are held for 15 minutes). - Windows XP computer stays for several minutes in stage 'Applying Computer Settings' The same Windows XP machine will log in immediately with cached credentials if the NIC is unplugged, - Windows XP clients are accessing network shares slowly - When you try to open a file or document that resides on a Distributed File System (DFS) share, it may take a long amount of time to open the resource (from 90 seconds to 15 minutes). However, you may be able to quickly open the same resource by using a UNC path. (KB312181) - When you use Microsoft Internet Explorer 6 to access shares on a Microsoft Windows NT 4.0-based server or a Microsoft Windows 2000-based server, access to the shares may appear to stop responding (hang). Note: You may gain access to the requested shares if you wait a long time, for example, 10 minutes. (KB812924) CAUSE ====== When entering a Uniform Naming Convention (UNC) path \\Servername\Sharename\Directory\Filename.ext the UNC location is first passed to the Web Client service which attempts to connect to "http://Servername/Sharename". WebClient uses port 80 to contact WEBDAV enabled servers and this needs to go via WinInet through the proxy. The proxy server will then attempt to contact the destination server (Servername). The Web Client waits for a response from the proxy server which may never be sent, resulting in a delay until the Web Client times out (default 10 minutes). If the destination server does not support HTTP on port 80 or the destination server is offline, the proxy server may fail to send the expected HTTP error code back to the Web Client. If there is a dead external (DFS) server reference on the proxy that the request is passed to then the delay can be due to the timeout for the external (DFS) connection failure. Significant delays may also occur on a Windows XP client if all of the following is true - You have enabled the WebClient service (which is the default) and the Network Provider Order lists 'Web Client Network' before 'Microsoft Windows Network'. - The domain controller which is used for authentication runs a service that listens on TCP port 80, i.e. Exchange server with Outlook Web Access (OWA). - Internet Explorer's proxy server settings are not configured to "Bypass proxy for local addresses" and local Intranet FQDNs are not entered in the exclusion list.
  10. Hallo, ... ich schäm mich ja auch schon- eigentlich hätte ich sowas Grundlegendes wissen sollen... Nun ja - bei den TrueType Schriften funktioniert es wohl auch (ausnahmsweise) und wenn man dann noch lokaler Admin ist... ich hab trotzdem keine Lust alle Clients abzuklappern... vielleicht hat ja jemand was Schlaues auf Lager... Trotzdem Vielen Dank!
  11. Hallo YAMBOS! Hab ich´s nicht verstanden - oder die anderen? Ich arbeite in erster Linie im Client- Support vor Ort. Die Domäne ist letztens auf AD umgestellt worden. Jetzt haben wir den Auftrag bekommen, an allen Clients neue Schriften zu installieren- PER HAND Ich dachte so etwas könnte man gut mit GPO´s abhandeln? Einfach per script die Schriften in den Ordner %windir%\Fonts kopieren und ab dem nächsten Neustart funzt es oder ???
  12. Hallo, wofür benutzt Du die ISDN- Leitung denn noch? Zum Surfen für alle? Ich werde das Gefühl nicht los, dass einfach nur ein günstiger Zeitpunkt für die große Mail abgewartet wird. Karen
  13. Hi 004, das kannst Du ja noch reklamieren... klappt gut bei IBM Karen
  14. Hallo , mein Kollege hat mir letztens erzählt, dass die T40 nur WI-FI vorbereitet sind und dass Aufrüsten 150 € ( meine ich) kostet...ich hab extra bei IBM auf der HP nachgesehen... nur ausgewählte Modelle haben WI-FI hier ein Auszug: Modell1: ThinkPad T40 TC17CGE Fragen Sie Ihren Händler nach dem Preis 1.50GHz Intel Pentium M processor Microsoft Windows XP Professional 256MB/ 2GB/PC2100 DDR SDRAM 40GB (ATA-100 (Enhanced IDE)) 14.1'' 1024 x 768TFT ATI Mobility RADEON 7500 2.24Kg IBM ThinkPad UltraNav -- CD-RW/DVD-ROM Combo -- 10/100 Ethernet 56K V.92 designed modem Wi-Fi wireless upgradable IBM Embedded Security Subsystem 2.0 Modell2: ThinkPad T40 TC182GE Fragen Sie Ihren Händler nach dem Preis 1.50GHz Intel Pentium M processor Microsoft Windows XP Professional 256MB/ 2GB/PC2100 DDR SDRAM 40GB (ATA-100 (Enhanced IDE)) 14.1'' 1024 x 768TFT ATI Mobility RADEON 7500 2.25Kg IBM ThinkPad UltraNav -- DVD-ROM -- Integrated Intel PRO/1000 Gigabit Ethernet 56K V.92 designed modem Intel PRO/Wireless Network Connection 802.11b IBM Embedded Security Subsystem 2.0 Du wirst wohl eins ohne haben :-((( Da is Nachrüsten mit USB-WLAN wohl günstiger ... Karen
  15. Hi, hast Du die Stellvertretungsrechte schon mal auf einem anderen Client ausprobiert? Gruß Karen
×
×
  • Neu erstellen...