.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Cannot access companyweb from server or client 2003

Posted By:      Posted Date: September 22, 2010    Points: 0   Category :SharePoint

I have tried a number of different things, none that have worked so far. I am unable to access companyweb from either the sbs 2003 r2 or from clients. I get the "Internet Explorer cannot access the webpage" error. It worked at one time, but we had consultants working on several other things and it quit.

I do not know what specifically changed. RWW works.

Here is nbtstat from the server:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>nbtstat -n

Local Area Connection 3:
Node IpAddress: [] Scope Id: []

    No names in cache

Lan on board nic:
Node IpAddress: [] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    AFPSERVER      <00>  UNIQUE      Registered
    AFPARTNERS     <00>  GROUP     &nb

View Complete Post

More Related Resource Links

SQL Server allowing access with NATIVE CLIENT Protocols are disabled.

I have disabled all client protocols from SQL Server Configuration Manager -> Sql Native Client configuration -> Client Protocols.Still I am able to access sql server with all client protocols disabled. Why ?Also I stopped the SQL Server Services and restarted it again. Then also the system is allowing me to connect with all the client protocol disabled.

Migration of DSN use for SQL Server access from Windows SP-3 clients to Windows 7 64 bit client

We have numerous apps which use a named DSN using SQLSRV32.dll for an ODBC connection from our Windows XP-Pro SP3 32 bit machines client access to remote windows 2003 based SQL servers (mix of 2005 and 2008).  On migrating to Windows 7, this dll will not allow the apps to use the newly constructed DSN (using SQLSRV32.dll with ODBC), even though a test connection is sucessful (abbeit much slower than seen on the XP-Pro machines).  What must I use on the Windows 7 64 bit machine to allow a DSN to be used by the migrated apps?  - I have descerned through Google that WDAC is now the tool to use, but I am cluless how to use it. - The expectations from the app on the Windows XP-Pro and on the Windows 7 64 bit machines is to use a DSN to connect to SQL servers on Windows 2003. I would appreciate any advice, and thanks!

SQL Server 2005 Express - Does it require a Client Access License (CAL)

Do you need a Client Access License (CAL) for each device that will connect to a SQL Server 2005 Express edition database?

How to access RAM above 32gb on Windows 2003 Server Standard x64?

My employers went and maxed out their database server for RAM to 64gb from 32gb. It's running SQL Server 2005 x64 on Windows 2003 Server Standard x64. As far as i'm aware of, 32gb is the RAM limit for the OS but does sql server have the ability to see beyond this limit? I'm about to ship the RAM back... Any insights would be greatly appreciated!

WCF client to access Java SOAP server 1.2


To all WCF experts out there... Maybe you can shed some light on the following questions.  Any pointers regarding WCF client to non-Microsoft implementation on .NET Framework 3.x will be appreciated too.  Thanks in advance.

  1. I already have an object that can serialize to a valid XML input message; minus soap specific elements.  If I pass it directly, it will fail because the object type is so different than type generated by svcutil.exe.  What's the best way of passing this to the service?  I know when I serialize my object, and the one created by svcutil to XML, they are identical. 
  2. I guess this should be the first question.  To access a non-microsoft SOAP 1.2 service, is WCF the way to go on .NET Framework 3.0/4.0?
  3. Reference:  Are there any good books/sites that you can refer regarding WCF client (specially non-Microsoft implementation)?  I've seen so many WCF service, but very less focus on the client.

Security Update for Win 2003 Server (KB980436) causes access error to secure url via WCF



today in the morning i installed 5-6 security updates including (KB980436) on our production server. During the day we got errors when our application calls a secured web service :

An error occurred while making the HTTP request to https://[MyService]. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.

I had nothing to do because we haven't made any change at our application. Then i remembered the security updates and walked through the update informations. I saw that KB is about :

MS10-049: Vulnerabilities in SChannel could allow remote code execution

I removed this update because its about secure channel, then everything worked fine.

So what should we do ? Who should be informed ?

Linked Server Error 7303 for Access 2003 Database

I am having difficulty creating a linked server to and Access 2003 database on my SQL 2005 server.  Whenever I create a linked server through the either the “New Linked Server” tool in the SQL Management Studio or using the sp_addlinkedserver method, receive and error indicating “Cannot initialize the data source object of the OLE DB provider…(Microsoft SQL Server Error: 7303)”.  Although my ultimate goal is to link to a secure Access 2003 database file, the current MDB file I am trying to link to is “unsecured”.  I have already verified that the SQL Service account has read and write access to the folder containing the MDB file as well as the temp directories on the SQL server (suggestions from other forums).  Is there any SQL Server configuration that I need to modify in order to use the Jet 4.0 linked server provider (Microsoft.Jet.OLEDB.4.0)?

How to host self hosting wcf in Windows Server and access from client


  Am developing a windows application. i am using SqlServer in my server and WCF as connecting bridge between the Server and client. My client want to run the WCF in server as self hosting and they will access the wcf from the client. Is it possible?. How can i achive this.

Querying Exchange Server 2003 does not bring all fields in Access 2007


Hello everyone.

I'm importing Outlook contacts shared folder to Microsoft Access 2007, but I can't see all the fields in each contact, what I have done is:

1. Open Access 2007

2. Click in "External Data" and make a Link to Outlook

When I do this, Access brings to me several fields but I can't see ALL fields which I can see in Outlook contact form.

The default form to "add a contact" in Outlook has been modified by adding more fields, DropDownList, TextBoxes and mapping them to a specified storage field.

does someone have a trick to import ALL Outlook contact fields?

thanks in advance.

Client can't connect to WCF on deployment machine Windows 2003 Sp2 server .NET 3.5



I have a WCF service hosted in a Windows service application.  I have a Windows Form client that connects to it.  I am using net.tcp binding for two endpoints.   It all works fine in my environment, but when I deploy it on my cutomer's machine the client does not get a response from the service.

I ran netstat -na and I can see the endpoints listening.  I can even see the connection ESTABLISHED when my client runs the first method.  But my client times out and receives a "Could not communicate with XXX service.  This request operation sent to net.tcp..... did not receive a reply within the configured timeout (00.01.00) The time alloted... etc"

I tried removing all security from the configuration file, but that did not make a difference.

I reinstalled .NET Framework 3.5

I added     System.Net.ServicePointManager.DefaultConnectionLimit = 200 as suggested in another post.

I am creating a trace for the client and the server.  The server does not log any activity of a connection.  The client is catching a communication exception.

Any insight would be greatly appreciated.  What else can I try to see why the client is not able to chake hands with the server on this particular machine?

Many thanks,



SQL Server 2008 -- MS Access 2003 Linked server -- Authentication failed


I am trying to link SQL Server 2008 - 64 to an MS Access database on a network share. I can get the link to work from the SQL management studio but when I try to do a ODBC query (from another machine)  of a view table pointing to the access db through a linked server using the "Microsoft.ACE.OLEDB.12.0"driver.  The error from the odbc trace is:

"        DIAG [01000] [Microsoft][SQL Server Native Client 10.0][SQL Server]OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "STPRD" returned message "Not a valid account name or password.". (7412) "

Yes the login to the password are good.  I have tried various setting using sp_addlinkedsrvlogin function but nothing will handle the extra hop.

issue with linked server from sql server 2008 to access 2003 database



I am trying to create a linked server from sql server 2008 to a secure access 2003 database(database which has a password), whatever options i am trying the result is i am getting the error 7399("Cannot start your application. The workgroup information file is missing or opened exclusively by another user.".) or error 7303.

I am selecting 'Microsoft.Jet.Oledb.4.0' as the provider. I think the problem is somewhere in

the workgroup files

Please help me in creating this linked server.



ClickOnce: Deploy and Update Your Smart Client Projects Using a Central Server


ClickOnce is a new deployment technology that allows users to download and execute Windows-based client applications over the Web, a network share, or from a local disk. Users get the rich interactive and stateful experience of Windows Forms, but still have the ease of deployment and updates available to Web applications. ClickOnce applications can be run offline and support a variety of automatic and manual update scenarios.Learn all about it here.

Brian Noyes

MSDN Magazine May 2004

Windows Server 2003: Discover Improved System Info, New Kernel, Debugging, Security, and UI APIs


There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003

Security Briefs: Exploring S4U Kerberos Extensions in Windows Server 2003


Building Web sites that provide services external to the corporate firewall is tricky. Usually it's not desirable to grant corporate domain accounts to external clients, and from a purely practical standpoint Kerberos does not work well over the Internet due to the typical configuration of client-side firewalls.

Keith Brown

MSDN Magazine April 2003

Return of the Rich Client: Code Access Security and Distribution Features in .NET Enhance Client-Sid


Rich clients employ many of the features and conveniences of the operating system they run on, and the list of these features has been growing since the dawn of the PC. But as apps have migrated to the Web, the trend towards increasing client-side functionality has ground to a virtual halt. There are several reasons for this; chief among them are security and deployment problems. But that's all about to change. With the .NET Framework, you can participate in building the distributable rich client of the future. In this article, the author enumerates the pertinent features of .NET that will allow you to build safe, easily deployable controls. The features discussed include managed code, code access security, versioning control, Windows Forms classes, and isolation.

Jason Clark

MSDN Magazine June 2002

SOAP: Using ATL Server to Build an Asynchronous SOAP Client in Unmanaged C++


SOAP opens up a new world of Web Services, letting you make function calls across a network or the Internet. But this flexibility creates new problems when your app needs to wait for calls to return from halfway around the world. What you need is an asynchronous SOAP client that takes advantage of threading to continue execution while waiting for calls over the wire. This article covers the basics of building such a client with ATL.

Pranish Kumar and Bogdan Crivat

MSDN Magazine April 2002

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend