Computing.Net > Forums > Networking > Lan Server Not Visible again

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Lan Server Not Visible again

Reply to Message Icon

Name: coreytroy
Date: October 13, 2008 at 18:20:55 Pacific
OS: XP Pro
CPU/Ram: AMD 3200 1gig
Comment:

Having problems with the LAN Server again.
I removed it and plugged it to another PC to test a Cat5 cable, then put it back.
Now it cannot be found.

If i plug it directly to my pc, i can access the web control panel ans see the files on it.
When i plug my pc to the 4 port switch, and the Lan Server to the switch also, i get nothing.
I cannot see the Lan Server or bring up the web control panel.

All pc's have a Static IP of 169.254.0.x with a subnet mask of 255.255.0.0.
Not Gateway or DNS.

I cannot get the Lan Server setting correct. It can act as a DHCP server, but i was sure i had it disabled, as the pc's do not have 169.254.0.1 set as the Gateway.

What settings do i need to put in the Lan Server?

I have the correct Workgroup name as the Lan Server also.
Why does it work great when directly connected to the PC, but NOT when connected to a switch ?



Sponsored Link
Ads by Google

Response Number 1
Name: guapo
Date: October 13, 2008 at 18:59:28 Pacific
Reply:

3. Private Address Space
Use one of the subnets below.

The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private networks:

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255


0

Response Number 2
Name: Curt R
Date: October 14, 2008 at 06:03:08 Pacific
Reply:

All network devices need to have IP addresses in the same subnet in order to communicate with each other.

The fact that your LAN server is showing an APIPA address (169.254.....) tells me it's set to get it's IP from DHCP and it's not getting one. (The apipa address being self assigned when it doesn't get a response from a DHCP server).

First off, with a server, or network printer, you want them to have a statically assigned IP address....you do not want them getting their IP from DHCP as it can change and lead to similar issues as what you're having now.

Check all your other PC's/laptops IP addresses by opening a command prompt window and typing:

ipconfig /all

Make note of the subnet, subnet mask, and gateway address of each. Then, statically assign your server an IP within the same range and use the exact same subnet mask and gateway IP's. Then, all devices should be able to communicate with each other properly.


0

Response Number 3
Name: coreytroy
Date: October 14, 2008 at 15:17:55 Pacific
Reply:

Curt R,
When i use the config /all i get an IP a 10.0.0.4; 255.0.0.0
Which is the network for the DSSL Wireless modem/router(Dlink DSL G604T).
The Lan Server(External HDD in a case) is only ever plugged via cat5 cable to the switch, but as the switch is not connected to the Router, i cannot see how anything(including LAN Server) could be on the wireless network to be seen.
The Lan Server has DCHP Disabled, but if i try to have NO GATEWAY set, i get an error.
But if i put 10.0.0.1 as the GATEWAY(Router's IP Address) i do not get the error, but i feel it will not work, as the LAN Server and the Wireless Router cannot se each other as there is no Wireless connection to the LAN Server.

Am i correct ?

I can cat5 connect any of the Pc's and LAN Server to the switch, but cannot connect anything via cat5 to the router.


0

Response Number 4
Name: coreytroy
Date: October 14, 2008 at 16:50:10 Pacific
Reply:

I have changed the LAN Server to a static Ip of 10.1.1.11 - 255.0.0.0 inline withe the wireless network Ip ranges.

If i connect a cat5 cable from my PC to the LAN Server, i can view the LAN Server and share the files.
I then disconnect the cat5 cable and connect BOTH PC and LAN Server to the switch.
Then i get NOTHING again.

Why does the switch prevent the PC to see the LAN Server ?
How can i fix that ?


0

Response Number 5
Name: guapo
Date: October 14, 2008 at 17:40:29 Pacific
Reply:

Exactly, what are you calling a "LAN server" and what is it running? What router do you have?


0

Related Posts

See More



Response Number 6
Name: coreytroy
Date: October 14, 2008 at 18:16:58 Pacific
Reply:

The LAN Server is a simple external Hard Drive(400gig) case with a Ethernet port + usb on the back.
I has DHCP capabilities, but i have it disabled at the moment.
Currently i have change it to static 10.1.1.11 - 255.0.0.0.
I have it visible in networks now, only after i unplugged and re-plugged in the switch for some reason.


0

Response Number 7
Name: guapo
Date: October 15, 2008 at 05:31:50 Pacific
Reply:

So it's really a network storage device being used as a file server. However, that subnet mask is wrong. It should be 255.255.255.0 since it's really a Class C subnet.

Secondly, you still didn't tell me what router you have. If you don't have a router, it would make things a lot easier if you did.


0

Response Number 8
Name: Curt R
Date: October 15, 2008 at 06:14:02 Pacific
Reply:

You said:

When i use the config /all i get an IP a 10.0.0.4; 255.0.0.0
Which is the network for the DSSL Wireless modem/router(Dlink DSL G604T).

and

I have changed the LAN Server to a static Ip of 10.1.1.11 - 255.0.0.0 inline withe the wireless network Ip ranges

If you're trying to set things up so your LAN works and all clients on the LAN have internet access you need to redo the configuration on your router to start with.

I suggest you reset it to factory defaults. Leave it set to DHCP on the WAN port (which connects to the DSL modem) so it can get it's correct TCP/IP information from your provider.

Then, leave the router to use the default Class C private IP's (192.168.0.0) and stop monkeying around with Class A.

Check that DHCP is setup correctly. In my experience D-Link tends to use 192.168.0.1 as the router's LAN IP. They usually define a DHCP scope of 192.168.0.100 to 192.168.0.199.

Plug your PC's/laptops in and test. Can they communicate with each other, are they all getting internet access? If yes, then everything is as it should be.

Now all you have to do is statically assign your NAS device a proper IP and subnet mask. In this case, pick an IP outside of the DHCP scope. I'd recommend using 192.168.0.10 with subnet mask 255.255.255.0

Now everything should work.


0

Response Number 9
Name: guapo
Date: October 15, 2008 at 15:53:17 Pacific
Reply:

"Then, leave the router to use the default Class C private IP's (192.168.0.0) and stop monkeying around with Class A."

Curt R:

You are correct in what you are saying ^^^ but to be more accurate a Class C network should be noted as 192.168.0.x since 192.168.0.0 denotes a Class B network. In a way, I'm nitpicking but a beginner may get confused.


0

Response Number 10
Name: coreytroy
Date: October 16, 2008 at 02:59:15 Pacific
Reply:

I am still confused with the reply's.

Can you confirm then:
1). What do i set the Modem/Router DHCP to Enabled or Disabled?
2) Do i change it from the default 10.1.1.1 - 255.0.0.0 to a static 192.168.0.1 - 255.255.255.0?
3). What do i set the Lan Server DHCP to, Disabled or Enabled?
3). What do i set the Lan Server IP address to, 192.169.0.2 - 255.255.255.0?
4). How do i have a Wireless Netwok for internet access to each PC from the Modem/Router on the same network as the PC's and Lan Server, when they are only cable connected to the Netcomm Smart 5 port Switch?
5). What do i set the PC IP's to? Static 192.169.0.x?
6). How do i set the Workgroup up if i need(as present) 2 network connections (1 x Wireless + 1 x Cat5 to/from Switch) ?

My GOAL is the have ALL Pc's to have Access to the Internet(DONE NOW through the Wireless Network)
AND ALL Pc's to access to the files on the LAN Server.


0

Response Number 11
Name: Curt R
Date: October 16, 2008 at 06:26:18 Pacific
Reply:

1) I would enable DHCP and make sure all client PC's/laptops are set to get their TCP/IP info from DHCP.

2) By default most (if not all) routers use the class C (just for you guapo) 192.168.0.0/24 or 192.168.1.0/24 IP range for the local IP of the router itself as well as DHCP. Once you reset the router to it's factory defaults (don't forget, you'll want the setup guide in-hand before you do the reset you'll see what IP range it's using.

3) This will depend on the DHCP scope that's configured on the router. Once you've reset it, and verified it's IP address then check the DHCP configuration on the router and make note of the scope. So let's say for example you router's LAN address is: 192.168.0.1 with subnet mask 255.255.255.0 (Class C private) your DHCP scope will likely be: 192.168.0.100 to 192.168.0.199 The IP you choose for your NAS device should be outside of the defined DHCP scope. Since your router is 192.168.0.1 I personally would use 192.168.0.10 for the NAS device.

4) Here's how your setup should look physically (this is assuming your modem is a combo device that is a modem and router in one)

Internet >> Modem/Router >> Switch >> clients (wireless and wired including the NAS)

Because the TCP/IP information for all clients comes from the DHCP service on the router, all clients will get IP's within the defined DHCP scope.

5) As I said above, set them to "automatically" get their TCP/IP information (that's DHCP)

6) For wired connections, plug the client in with a network cable to your switch. For a wireless client, connect wirelessly. If everything is setup correctly, they will be able to both:
A) communicate with each other on the LAN
and
B) access the internet


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: Lan Server Not Visible again

Primary SQL Server Not Available www.computing.net/answers/networking/primary-sql-server-not-available/15121.html

W2k nat lan www.computing.net/answers/networking/w2k-nat-lan/31406.html

Lan Server www.computing.net/answers/networking/lan-server/34104.html