Windows 2008 Local network access problem

Dell Inspiron 1545
June 29, 2011 at 19:45:18
Specs: Windows vista, 1.995 GHz / 2GB
I have Windows 2008 Std installed with firewall off. For some reason I cannot access it through my network via IP or PC name. I can how ever connect to it using VPN. I never had this problem with windows 2000 Server though so I'm lost on why its doing this as it doesn't make sense (to me anyways.)

I believe everything I need on my router is also configured correctly as far as I can tell.

The reason why I need to access it via IP is so I can get my website set up and all. I've done this before and had no problems.

Right now my router is configred to allow port 80 on my local ip for the server but again can't access it using the local ip.

Would anyone happen to know why its doing this?

Thanks


See More: Windows 2008 Local network access problem

Report •


#1
June 30, 2011 at 07:16:47
Open a command prompt window (ie: Start >> Run >> type cmd and hit Enter) and perform the following command:

ipconfig /all

Once you've finished, copy/paste the output into a response on here so we can have a look.

For info on how to copy/paste from a command prompt window click on my name above and read my "how-to" guide titled, "Post the output of ipconfig (version 2)"

Also, include your router's LAN IP and subnet mask and the DHCP Scope configuration as well.

One last thing, have you enabled "Remote Desktop" on the server to allow remote connections?

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
June 30, 2011 at 09:38:34
Well i'm not home atm to get the info but I can tell you what it is as I aissinged a static local ip to it.


I'm using a Linksys router by the way
Also I disabled/unchecked IPv 6 off;

Server IP nfo:

IP:192.1681.190
SubMask:255.255.255.0
Default Gateway:192.168.1.1

Primary DNS1:192.168.1.1
Primary DNS2: Not Set

Remote Desktop is on but the port for it is diabled through the router as I allow VPN to connect to Remote Desktop using 100.100.100.100 VPN ip I set for it.

Also if I'm on the server and I type in my local ip 192.168.1.190 I can view my files and printers but yet if I do that outside of my computer say my laptop that I have connected to it it will bring up an error Cannot find network path or something slimliar to that. The same goes for the server name as well.

Now the funny thing is on my laptop my server is listed under the network and if I click on it it brings up the same error. There was one time where it asked for a username and password (which I typed in correctly) and after that it still showed the same error.

Also I need to be able to view that IP as well because I have a site running on it that I can view on my server via local ip or computer name. If I do the same thing with another computer using the same ip or server name I can't view it and get a website not found.

Now when I had 2000 installed I never had this problem.

I'm using vertrigo 2.24 as my main php server and on my router port 80 and the ports for VPN is open.

On my server computer the firewall is turned off just in-case it was interfering with it.

Thanks

Also the server is not a DC. It might be one down the road though but not atm.


Report •

#3
June 30, 2011 at 10:34:21
Your settings look OK as long as the LAN IP of the router is 192.168.1.1

If it is, you should have LAN connectivity with other LAN clients. However you say whenever you attempt to connect using IP or Hostname, you get the error you mention.

You need to verify your TCP/IP settings with the rest of your network. I would go on another client that is communicating properly and do the ipconfig /all and compare to the server.

Also if I'm on the server and I type in my local ip 192.168.1.190 I can view my files and printers

Type that where exactly?

if I do that outside of my computer say my laptop that I have connected to it it will bring up an error Cannot find network path or something slimliar to that. The same goes for the server name as well

The usual format to connect to a server is as follows: \\servername\share

NOTE: you can use the actual IP or the server's hostname to connect to it.

Are you sure you're attempting to connect to shares correctly?

Sadly, I can't be of any help with websites, my forte is in other areas of computing.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Related Solutions

#4
June 30, 2011 at 10:44:55
well if I was on my server and under run the ip would work but under my other computer and I type in the ip it doesn't and I get that error. Also It my router ip tcp and all is set up correctly because my mom has her computer(vista) shared and I can access files off of it with my laptop(another vista). But I can't with my server though. Also on my server I do have access to the routers login page which I can access with my other computers also. I can access the internet on it as well so I don't know ifs its something with my server.

The first time I installed it I couldn't get any network or internet and found out I had to add a feature for it. Also my server is connected via USB linksys wireless card.



Report •

#5
June 30, 2011 at 11:02:47
If this server is running active directory your dns ip addressing is incorrect.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#6
June 30, 2011 at 11:14:16
I have it set to my routers dns. If I remember correctly when I tried using my isp DNS it failed and I don't think I have AD enabled/installed. Would have to check because this os is a lot different and harder to understand then 2000 ><

Report •

#7
June 30, 2011 at 11:35:59
routers don't do dns unless they are running dnsmasq

pointing to a gateway just means 'shove it out here and hope someone answers'
whereas pointing to a known dns server means 'go here directly for the answer'

when you used the isp dns how did you determine it wasn't working? It should have.

If not running AD then your dns addressing is fine.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#8
June 30, 2011 at 11:37:29
Well the dns and ip address from my ISP is displayed on the status page of my router.

Report •

#9
June 30, 2011 at 12:15:09
I'm a little stumped. From the sounds of it, you have the TCP/IP settings done correctly so it should work.

Are you able to ping the server from other LAN clients? If the server's built-in firewall software is disabled, or set to respond to ICMP requests (ping) then you should get a proper response if it's configured correctly.

Rather than use the "Run" command from remote computers, try mapping a network drive via Windows Explorer (open it then go "Tools >> Map Network Drive") using the format I detailed in my last post. If it doesn't connect using the hostname, try the IP address instead. Report back on your results and any error message you get if it doesn't work.

If the network side of the server is configured correctly and you have a shared folder accessible to the client, mapping a drive should work.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#10
June 30, 2011 at 13:24:12
Well I tried that a few nights ago when I was searching for info about this. I tried pinging and I just got a timed out if I'm not mistaken. So the ping did not work. It as if the server is on its own network of some kind. It doesn't make any sense.

By any chance is it a problem with the os and maybe and update or hot fix is needed?


Also is there any other options, roles, or features I need to install.

O and if I connect via VPN I can use 100.100.100.100 to access my computer and see my folders and printers that I have shared, but thats only if I connect to it using VPN. Other then that my server doesn't want anything to do with my network from the sounds of it.

I have not tried mapping a drive to the shared folder so when I'm back home I'll give that a go and see what happens.


Thanks you all for helping me out with this issue.


Report •

#11
June 30, 2011 at 13:28:18
Earlier I told you to check your TCP/IP settings. When you get home tonight I want you to check the ones on the server and then do the same on another client PC that is working properly.

Post the output in here. Here's what to do:

Open a command prompt window (ie: Start >> Run >> type cmd and hit Enter) and perform the following command:

ipconfig /all

Once you've finished, copy/paste the output into a response on here so we can have a look.

For info on how to copy/paste from a command prompt window click on my name above and read my "how-to" guide titled, "Post the output of ipconfig (version 2)"

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#12
June 30, 2011 at 13:52:17
ok well on my laptop my ip is:

IP: 192.168.1.189
SubMask: 255.255.255.0
GateWay 192.168.1.1

DNS1: 192.168.1.1
DNS2: Not Set

Also the ip on my laptop is static also

CMD output:

Windows IP Configuration


Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::4957:a953:9842:34a7%10
IPv4 Address. . . . . . . . . . . : 192.168.1.189
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2838:d89:bbda:8c78
Link-local IPv6 Address . . . . . : fe80::2838:d89:bbda:8c78%12
Default Gateway . . . . . . . . . : ::

Tunnel adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :


Report •

#13
June 30, 2011 at 16:36:36
ok so when i'm back and this is the info:

C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.1.190
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

PPP adapter RAS (Dial In) Interface:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 100.100.100.100
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 13:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2002:6464:6464::6464:6464
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301

C:\Users\Administrator>


Also now this is strange, On my laptop which is running vista I can gain access to my moms pc who is also running vista and I can view her files. Now this is where its odd.

If I try to do that under my server I also get the network path not found.

So on my server if I try to access my moms computer its the same effect as my laptop trying to access my server.


Any idea whats going on here?

thanks


Report •

#14
July 2, 2011 at 12:15:30
OK I found the problem!!!!!!

About time too >< (I almost went back to 2000)

IT has to do with your routing and remote access (Static Packet Filter option)

Here are the steps copied from the link below by chicagotech:

Pleas note that you need to apply theses steps from within the console its self and not through VPN or Remote Desktop

Analysis
======
When we configure RRAS on a server that has two NICs, static packets filtering is selected by default. If that is true, only VPN traffic is allowed to reach or pass the server and that should be the reason why we are not able to RDP to the server. if that is the case, we can turn of static packets filtering when configuring RRAS.

Suggestion
========
Please try the following for troubleshooting:
1. On the server, open Routing and Remote Access from Administrative Tools.
2. Right click the server name and select “Disable Routing and Remote Access”.
3. After we disable it, right click and select “Configure and Enable Routing and Remote Access”.
4. Follow the wizard and select VPN.
5. When selecting the network that connects to Internet, ensure we de-select “Enable security on the selected interface by setting up static packets filtering”.
6. Finish the reset of the wizard and check whether we are able to connect or not.


Here is the link to the fix:

http://www.chicagotech.net/netforum...


Report •


Ask Question