Little Confused Any help appreciated :S

[Danny D]

Ok guys. On the D link i disconnected 2 wires and on 2 computers you could not connect to the server or internet. As far as I can see both of these switches are being used...

[+BudMan MVC]

It would seem pretty clear there is no special routing -- since both nics are in the same network and pointing to the same gateway, and from the ipconfig its also quite clear they are not teamed. Nor from his explanation of the network would there be any need for special routing - they have 1 "server" xp box ;) So what are they going need special routing to?

The so called "server" for example has a wired and wireless interface both connected to the same 192.168.1.0/24 network.. You can not "team" wired and wireless interfaces ;) Nor would there be any point to even if you could.

edit:

Which wires did you disconnect? Its quite possible you had a computer(s) with both cables connected to the dlink?

Depends on where your router is connected as well.

router (192.168.1.1) --- switch1 (dlink or linksys) --- switch2 (linksys or dlink)

or

Router -- dlink

|

linksys

You need to understand how your switches are connected to your router the gateway address shown in your ipconfig 192.168.1.1

If the linksys has enough ports (that all work) then your linksys needs to be connected to your router and the computers connected to it.

router -- linksys -- computers

Edited September 17, 2009 by BudMan

[Danny D]

Ok the only kind of router I see is the wireless one. The modem wire goes into the router (internet port). Then there are 2 wires going out from port 1 and 2 from the router. The thing is i dont know where they go because the wiring is done on top of the ceiling.

[Max Veteran]

Thread Cleaned

Now that I've eliminated most of the hissing, spitting and venom in this thread - keep it on topic.

[+BudMan MVC]

Well I would guess the 2 cables from the router 1 and 2 lan ports go to the 2 different routers, 1 each..

If the cables are not labeled, check the lights on the switches ports.. then unplug one of the wires from routers lan ports -- which port light goes out on one of the routers.. Then do the same thing for the other one.

keep in mind this will disconnect users from the internet - so you might want to do this after hours ;)

[Danny D]

Ok. So lan port #1 i took the wire off the wireless router and no lights went off on the switch. I took off lan port #2 and Number 5 on the d link went off.

[+BudMan MVC]

So maybe lan 1 goes to a PC? If was lighted on the router, but when you unplugged it no lights went out on the switches? Then I would assume it went elsewhere - PC most likely.. Do you have any pcs in the building/office where the router and modem are that are not wireless?

Does a cable go from the dlink to the linksys? If so you would of had a loop, and I would assume the switches would of turned one of the interfaces off.. That is if they support STP (spanning tree protocol)

So the one that comes from the router to the dlink -- plug it into the linksys vs the dlink.. Then have 1 wire from each pc run to the linksys -- then you can remove the dlink switch.

You only need 1 connection from the router to the switch your going to use, and then 1 connection from each pc to that switch.

edit: btw that was a typo in my other post, I meant to say 2 different switches, not routers ;)

[Danny D]

I will be at the office tomorrow and will try to get the information you guys are asking for.

[Danny D]

Hello,

I am getting the hang of this :). I will be connecting 3 printers tomorrow. Any idea how I can do this?

[lnmnky]

Do they have Lan ports? Some can go straight onto a switch, and some might need to go into a print server. Or they can connect to a PC and then be shared in Windows.

[+BudMan MVC]

What are the printers? Are they network printers? Or just usb/lpt printers?

If network -- just plug them into your switch.. And setup their IPs following their instructions to be on your network..

Then you can either connect to them from your "server" and share them - then connect the clients to this printer share, or you point each client to the printers IP directly setting up the printer on the client.

The server method is easier and has advantages. But you might have issues with XP as your server, if you have any vista clients, etc.

If you give us the details of what printers you have -- we can help more.

[Danny D]

BudMan thanks for the help. The printer problem is very low right now a problem I am having is people getting kicked out of the network. Basically they are working on something and when they try to save it its not going to let them. Sometimes i have to click like 50 times to get into the server. The guy that built this network could not solve this issue either so I am turning to you guys for help.

thanks again for all of the help you gave me so far!

[ncoday]

Yeah your not going to want to jump right into a CCNA course book if your sketchy on even what a switch is ;)

This might be a better starting point ;)

http://www.amazon.com/Networking-Dummies-S...e/dp/0764516779

http://www.amazon.com/Networking-All-Refer...7348&sr=1-1

http://www.amazon.com/Networking-Beginners...6932&sr=1-4

http://www.amazon.com/Sams-Teach-Yourself-...7162&sr=1-9

I am no network master by any means, but my recommendation is the same as Budman, you've got some learning/reading to do.

Ask the big bossman if he would pay for the books. If he asks why, say that he is getting off lightly as most experienced and certified Network Admins are not cheap.

I think you might be better-off building the network back up from scratch, though that is just my personal opinion

That way you can know it is being done right.

[Danny D]

I am no network master by any means, but my recommendation is the same as Budman, you've got some learning/reading to do.

Ask the big bossman if he would pay for the books. If he asks why, say that he is getting off lightly as most experienced and certified Network Admins are not cheap.

I think you might be better-off building the network back up from scratch, though that is just my personal opinion

That way you can know it is being done right.

They are constantly working on it otherwise i would of done that. Its very weird :s

[Danny D]

Any idea guys?

[+BudMan MVC]

"Sometimes i have to click like 50 times to get into the server. The guy that built this network could not solve this issue either so I am turning to you guys for help."

How many users do you have again? XP pro is limited to 10 concurrent connections from other machines to file shares. Home is only 5

Is this the error your getting?

http://support.microsoft.com/kb/314882

Inbound connections limit in Windows XP

[Danny D]

"Sometimes i have to click like 50 times to get into the server. The guy that built this network could not solve this issue either so I am turning to you guys for help."

How many users do you have again? XP pro is limited to 10 concurrent connections from other machines to file shares. Home is only 5

Is this the error your getting?

http://support.microsoft.com/kb/314882

Inbound connections limit in Windows XP

Well that solves that. Budman I dont know your name, but again THANK YOU for the great help! There is no way to raise the limit correct?

[+BudMan MVC]

No there is no way to raise the limit - which why you don't use XP as a file/print server if you have more than a couple of users ;)

There are CHEAP/FREE alternatives to windows based OSes -- You could run something like Clark Connect, which can act as Domain.. Central userbase, file server, print server, email server, etc. etc. etc..

http://www.clarkconnect.com/

Or for soho setups - you could take a look at Microsofts SBS.. Cheapest way to setup a Active Directory with tools to make it easier to manage from microsoft, etc. You will have to purchase the number of cals to support the number of users you have, etc. It maxes out around 75 users I do believe - atleast the older 2k3 versions did.

http://www.microsoft.com/sbs/en/us/default.aspx

If your on a budget, I would really suggest you look at the clarkconnect option -- there is a FREE version to use.. Another option other than the microsoft SBS or CC is SME Server http://wiki.contribs.org/SME_Server:About

There is really is little need to resort to using XP boxes as your file server when there are FREE options that don't have such limits of how many window users can access your file shares at the same time, etc.

To be honest any linux distro running SAMBA can provide file shares to windows boxes or printers without any limit connections. But SME and CC are designed for the novice to linux user, with simple to setup interfaces and specifically designed linux distros to replace a many aspects of a windows Active Directory Domain without the MS price tag ;) Don't get me wrong its not a true 100% replacement for AD -- but for the soho business its quite often a perfect solution. And more than likely will far exceed your feature requirements -- especially if you are use to use a XP box as your "server" ;)

Edited October 1, 2009 by BudMan

[Danny D]

Today I have been going wild i connected my laptop to the network and one of the people here could not connect because there was already 10 people connected. So i disconnected my laptop and it let them connect after 30 min. Money is not an issue as long as it fixes this issue im getting tired of it. How does Clark Connect work? How would I set it up? I dont want to mess anything up with the current set up. Thanks again BudMan.

No there is no way to raise the limit - which why you don't use XP as a file/print server if you have more than a couple of users ;)

There are CHEAP/FREE alternatives to windows based OSes -- You could run something like Clark Connect, which can act as Domain.. Central userbase, file server, print server, email server, etc. etc. etc..

http://www.clarkconnect.com/

Or for soho setups - you could take a look at Microsofts SBS.. Cheapest way to setup a Active Directory with tools to make it easier to manage from microsoft, etc. You will have to purchase the number of cals to support the number of users you have, etc. It maxes out around 75 users I do believe - atleast the older 2k3 versions did.

http://www.microsoft.com/sbs/en/us/default.aspx

If your on a budget, I would really suggest you look at the clarkconnect option -- there is a FREE version to use.. Another option other than the microsoft SBS or CC is SME Server http://wiki.contribs.org/SME_Server:About

There is really is little need to resort to using XP boxes as your file server when there are FREE options that don't have such limits of how many window users can access your file shares at the same time, etc.

To be honest any linux distro running SAMBA can provide file shares to windows boxes or printers without any limit connections. But SME and CC are designed for the novice to linux user, with simple to setup interfaces and specifically designed linux distros to replace a many aspects of a windows Active Directory Domain without the MS price tag ;) Don't get me wrong its not a true 100% replacement for AD -- but for the soho business its quite often a perfect solution. And more than likely will far exceed your feature requirements -- especially if you are use to use a XP box as your "server" ;)

[Sophism]

If money is not an issue I would go with MS Small Busines Server and the number of needed Cals.

[+BudMan MVC]

If your a MS shop - and what you understand more is windows.. Then yeah I would agree the SBS route might be better for you.. But linux is a very nice option as well.. ClarkConnect has a supported version for very little dollars.. And the management interfaces are very novice friendly, etc.

So its up to you -- either way you go.. Your going to want to get a new machine for your server most likely - so that you can leave your current setup in place and just bring the new server online in parallel.

I would suggest you look into a entry level server piece of hardware vs PC type. But if you have a spare PC you could use that as a test for either option. Both CC (enterprise edition) and SBS have free trials.

But in a nutshell -- bring the new server online. Copy all the files from the current XP server to the new one.. Create the shares - create your users on the new server and then join your computers to the new domain you will create.

Worse case -- is since your not changing anything on the current server is you could always go back to how your setup now for access.

If you need help -- neowin is always here ;) No matter which option you go with, and if you need help picking out a entry level server hardware to use -- again just ask.. Lots of people here to help.

edit: Just my 2 cents is since you can try both for FREE.. Do that -- and then go with the one you like better!

[Danny D]

Thanks BudMan, but how does that Clark thing work? Do i install it on windows or is it like an OS?

[+BudMan MVC]

CC is its OWN OS (linux) Just like Windows is an OS.. Download it and try it out on a PC or virtual machine.

[Danny D]

well if its an OS then i rather install linux as its much easier to work with i think i have not tried CC yet but i think I will.

[+BudMan MVC]

Im pretty sure you will love it -- its a great distro for the soho, and you can not beat the price ;) Get yourself a nice entry level server, with a backup power supply, setup your disks in a raid and you would be rockin compared to what you have now.