Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Weird FQDN / proxy settings behavior

  Asked By: Jena    Date: Apr 19    Category: Sharepoint    Views: 893

Anyone experience anything similar or could
possibly explain what I did, if anything, to cause the problem?

I'm not sure when it started, but sometime between yesterday and today users
could not access SPPS. Normally, when they go to http://server/workspace,
it uses NTLM authentication and they just cruise right in. Starting this
morning, everyone was challenged with the authentication window and the
realm was server.domain.com.

Now, I know that FQDN stuff is squirrelly and I didn't want to go down that
extranet path. We only access our SPPS server over a LAN or VPN'ed in and
Netbios/wins works ok for us. We've always used the FakeProxy settings
mentioned in the installation manuals.

So, the problem was this: people couldn't browse web folders or view the
http pages because it kept bringing up this authentication window and no
matter what we tried, it just never let us in. Eventually, we'd get the
classic proxycfg message that people get if their proxycfg settings are

So I went in, checked the settings with proxycfg (they were correct), then
did a proxycfg -u, then restarted IIS and now everything's working correctly
again. Why? The settings of proxycfg now are still the exact same.

Now, I don't pretend to know of some other things going on in our network
that could be factors. The biggest one -- we recently converted to Active
Directory. Like a week ago. However, the server wasn't rebooted and I
double and triple checked the default domain policy for anything that might
be related and couldn't find anything.

The only weird thing in the event log was:

Event Type: Error
Event Source: Srv
Event Category: None
Event ID: 2012
Date: 8/8/2002
Time: 3:36:33 PM
User: N/A
Computer: GO
The server has encountered a network error.
0000: 00 00 04 00 01 00 54 00 ......T.
0008: 00 00 00 00 dc 07 00 c0 ....Ü..À
0010: 00 00 00 00 3d 02 00 c0 ....=..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 9e 08 00 00 z...

and that happened at 3:36pm yesterday and I was using the server up until
6pm yesterday.



2 Answers Found

Answer #1    Answered By: Kartik Athani     Answered On: Apr 19

This is just a guess based on my past experiences. Sounds like a NetBIOS
issue. I had a similar  problem with a development box. Try removing the
box from the domain. Renaming, and then adding back to the domain. Try to
hit the new name of the box http://newname/workspace If that works, then
rename the box back to the original name and you should be ok.

Couple of other things... Can People access  regular webs that might reside
on the box? Can you reach the site from the box it self (i.e. logged on as
administrator can you access the site)

Answer #2    Answered By: Ira Knox     Answered On: Apr 19

I have noticed similar  issue with SQL server  after a AD conversion, it stopped
NTLM authentication  after a few days. My advice is after you upgrade to AD,
every server should be restarted.

Maybe restarting IIS fixed the NTLM authentication issue you were having. Just
guessing !

Didn't find what you were looking for? Find more on Weird FQDN / proxy settings behavior Or get search suggestion and latest updates.