General discussion

Locked

Intranet

By jotwee ·
I do have problems connecting workstations to the Intranet. I do have the IE 5 installed, the mappings and Batchfiles are also ok but I cannot connect. It displays always "Server not found" or "DNS ERROR"
Is it possible to send me a setup guide or to tell me what i have made wrong? I guess i have to change something in the IE 5 or in the network neighbourhood.
Thanks Juergen

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Intranet

by guidos In reply to Intranet

Do you have TCP/IP installed and DNS configured within it?

Collapse -

Intranet

by jotwee In reply to Intranet

The question was auto-closed by TechRepublic

Collapse -

Intranet

by eBob In reply to Intranet

When you say "Intranet" I will take that you mean an internal website. This is likely running on IIS, or perhaps Apache. You do have TCP/IP running on your network (right?).

Given that, then "PC/Windows" concepts like "mappings" and "Network Neighbourhood" are (largely) irrelevant.

On your Intranet server, what happens when you fire up the browser and type "http://127.0.0.1"? You should see your Intranet's homepage. If not, then your Intranet server is not setup correctly.

Again, on your server, what happens when you try to contact "http://localhost"? It should again be your Intranet's homepage. if not, then the name "localhost" is not being resolved properly. This may be a DNS problem or some other "name resolution" strategy, like the hosts file ("lmhosts" in Win32, I believe). Go to a command prompt and try to "ping localhost". You should see ping comeback with either your IP address, or with "127.0.0.1" (which is a special IP address meaning "your local system"). This willhelp you debug this problem.

If you can get to your Intranet's homepage from the server then you can start debugging from the clients (see part 2).

Collapse -

Intranet

by eBob In reply to Intranet

(Part 2)

From a client's browser, "http://172.16.1.14" (or whatever is the IP address of your Intranet server). Do you see your Intranet's homepage? If not, then the problem is with the IP config on the client. Use simple tools like PING and TRACEROUTE (TRACERT in Windoze-speak) to track this down.

If you got the homepage, try surfing the Intranet from browsers on BOTH a client and the server. If you start getting a lot of broken images, 404s and 500s then it's likely that the links inside your HTML use what I call "absolute references" (http://mysite/myfile.gif) rather than simple "relative references" (myfile.gif).

There are a couple of ways to fix this: either get DNS running so that "mysite" is resolved correctly, or change your references (yuck!).

Assuming that you can connect to your Intranet site using the IP address you now need to find out if you can hit it by "name". Oh, but what name?

Do you have DNS running? If so can you PING the server by this name, from the client. (Trick question, since if you can do this, and hit the homepage by address then you really should be able to hit the homepage with this name.)

Do you know the NetBIOS name of your Intranet server (another assumption: a Windoze network)? Can you PING this? Can you "http://netBIOSname"?

If this works, then you can choose to just work like that.

Otherwise, you need to "take it up a notch" and deploy a DNS structure, etc. That is at least one whole other topic...

Collapse -

Intranet

by jotwee In reply to Intranet

The question was auto-closed by TechRepublic

Collapse -

Intranet

by jotwee In reply to Intranet

This question was auto closed due to inactivity

Back to Desktop Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums