How to speed up network share

[ell]

Hi, I'm not too good with networking skills, but heres the scenario: We have two new win 7 pc's, networked together by single ethernet, one is connected to the net and is the host for the other which has no net access or firewall, it only is used to access the host's shared folder. This shared folder is very large holding inventory files. The software installed gave me simple set-up so I got that running ok. The files are accessed from the work station fine, but they are extremely slow opening, its getting so bad my customer has called saying its taking almost 5 min to open the shared folder from the host, I assume this is because of the shared folder getting so large. These pc's are only 10 ft apart. Ideas?

 

[numnutz]

I am not network genius either but is this a new setup that has always been slow or older that has gotten slow over time? everything connect to a GB ports? how much memory is in each workstation?

 

[Knightsman]

When you say the other doesnt have network access, what exactly is it plugged into?

I would

setup router, then a gigabit switch, connect both computers to that switch and you should have very fast speeds. If the customer doesnt want internet on the other machine, then I wouldnt take the job. To me that shoots red flags, because these days there isnt a good reason for it not to be connected, as long as there isnt a Good reason the software cant be connected. But it sounds like it can.

If they are strict about it not being on the internet, they probably will be more of a hassle than anything.

 

[ell]

I am not network genius either but is this a new setup that has always been slow or older that has gotten slow over time? everything connect to a GB ports? how much memory is in each workstation?

they are identical new towers, 4 gb ram each, all new set-up and sharing, unless maybe having the same folder open on both at the same time has something to do with it???

 

[ell]

When you say the other doesnt have network access, what exactly is it plugged into?

I would

setup router, then a gigabit switch, connect both computers to that switch and you should have very fast speeds. If the customer doesnt want internet on the other machine, then I wouldnt take the job. To me that shoots red flags, because these days there isnt a good reason for it not to be connected, as long as there isnt a Good reason the software cant be connected. But it sounds like it can.

If they are strict about it not being on the internet, they probably will be more of a hassle than anything.

I didn't hook the second up cuz they use a verizon usb wireless adapter to get on the net and they only use the net on the host for email. The ethernet cable between them is what is used for the 2nd pc to access the shared host folders. So a gigabit switch would increase the speed even with a existing direct ethernet connection between them even though they are both already gigabit compliant adapters?

 

[YeOldeStonecat]

OK...so if I am drawing the picture of this setup correctly...you have 2x computers. They are connected to each other using a patch cable from NIC to NIC. Assuming the patch cable is CAT5e minimum..and properly put together...factory made?

One of the PCs has a USB cellular modem...which should be irrelevant of the two computers connecting together so we'll leave that alone.

You should not need a switch in between the computers...they're just doing a direct connection to each other. Part of the gigabit standard is auto MDI-X...so a crossover cable is not needed either...the NICs do it themselves, just a standard CAT5e patch cable is all you need.

Are the computers set on static LAN IP addresses?
Is netbios over IP enabled in the advanced TCP/IP settings on each?

Firewalls rules set on both for workgroup file 'n print sharing?
Any 3rd party software firewalls/security suites installed which is bloating things up?
Speaking of antivirus....set exclusions in the real time scanner on the host PC for the directory which is shared. And on the client PC...set exclusions on network drives/folders...including this folder it's reading on the "server".

What network cards? Intels are best..Broadcoms OK, I don't like realtecs...but for only 2 computers it shouldn't matter much...it's not like you're trying to serve up files to dozens of clients.

Have tried turning on jumbo frames on each computers NIC? Try setting to 9,000.

 

[ell]

OK...so if I am drawing the picture of this setup correctly...you have 2x computers. They are connected to each other using a patch cable from NIC to NIC. Assuming the patch cable is CAT5e minimum..and properly put together...factory made? Yes, exactly right

One of the PCs has a USB cellular modem...which should be irrelevant of the two computers connecting together so we'll leave that alone. yup

You should not need a switch in between the computers...they're just doing a direct connection to each other. Part of the gigabit standard is auto MDI-X...so a crossover cable is not needed either...the NICs do it themselves, just a standard CAT5e patch cable is all you need.

Are the computers set on static LAN IP addresses? no, does it matter with only 2 pcs?
Is netbios over IP enabled in the advanced TCP/IP settings on each? no

Firewalls rules set on both for workgroup file 'n print sharing? I think so, I'll have to check it again
Any 3rd party software firewalls/security suites installed which is bloating things up? no, in fact the client pc has no antivirus at all since it does not go on the net.
Speaking of antivirus....set exclusions in the real time scanner on the host PC for the directory which is shared. good idea. And on the client PC...set exclusions on network drives/folders...including this folder it's reading on the "server".

What network cards? Realtek RTL8103EL Intels are best..Broadcoms OK, I don't like realtecs...but for only 2 computers it shouldn't matter much...it's not like you're trying to serve up files to dozens of clients.

Have tried turning on jumbo frames on each computers NIC? Try setting to 9,000.I will check on this! don't know if the cards have the option. thanks great info!

 

[YeOldeStonecat]

I would set the IP of each computer manually....and I would enable netbios over IP. This may not impact speed of browsing shares and file copies.....but it helps eliminate the need for locating. If IP leases change, may cause hiccups now 'n then.

I also forgot to ask...
What model of hard drives? 7,200rpm minimum? Size of cache?
What kind of files are these? Size of files? Database driven? If it's database driven, I'd exclude those directories in the antivirus real time scanner list too.

 

[ell]

I would set the IP of each computer manually....and I would enable netbios over IP. This may not impact speed of browsing shares and file copies.....but it helps eliminate the need for locating. If IP leases change, may cause hiccups now 'n then.

I also forgot to ask...
What model of hard drives? 7,200rpm minimum? Size of cache?
What kind of files are these? Size of files? Database driven? If it's database driven, I'd exclude those directories in the antivirus real time scanner list too.

I don't know the hd speeds, he's using a custom commercial inventory program, they have a large commercial frozen food storage business the data base file is constantly changing and both pcs are usually accessing the data folder at the same time. The software had separate installers for the host & clients so I know thats installed right. I do have cobian backup installed on the host which also runs a daily backup to a external drive, wonder if that could be slowing things up too, but its critical he has a current backup.

 

[jbartlett323]

I would set static like StoneCat said. If they are not, and there is no DHCP server (and theres clearly not) then windows will be setting its auto config, which can cause everything from IP overlap to constantly trying to get a new addy. Actually, from the sounds of it, thats whats happening, both machines are flooding your network with broadcast data constantly trying to locate a DHCP server. that coupled with them renewing the IP automatically every few minutes, is an utter recipe for disaster!
For ease of use though, I think I would put in a cheap router with DHCP capability. Just connect the 2 machines, no connection to the net. That way, any new machine ever, you dont have to fight this again.

 

[ell]

I would set static like StoneCat said. If they are not, and there is no DHCP server (and theres clearly not) then windows will be setting its auto config, which can cause everything from IP overlap to constantly trying to get a new addy. Actually, from the sounds of it, thats whats happening, both machines are flooding your network with broadcast data constantly trying to locate a DHCP server. that coupled with them renewing the IP automatically every few minutes, is an utter recipe for disaster!
For ease of use though, I think I would put in a cheap router with DHCP capability. Just connect the 2 machines, no connection to the net. That way, any new machine ever, you dont have to fight this again.

I'm making an apt to go over and do it! Thanks everyone!

 

[YeOldeStonecat]

For 2 computers, no need for a router to run DHCP. The current setup of having them self assign APIPA won't storm your network..it's 2 computers connected to each other. Arps won't amount to a single grain of sand on a huge beach.

 

[ell]

For 2 computers, no need for a router to run DHCP. The current setup of having them self assign APIPA won't storm your network..it's 2 computers connected to each other. Arps won't amount to a single grain of sand on a huge beach.

yeah, I'm not getting the router, the old man there will complain if I buy hardware and it doesn't help, but I will try setting static ips

 

[ArtemusComputerTechnology]

I agree with Knightsman...

 

[Knightsman]

I didn't hook the second up cuz they use a verizon usb wireless adapter to get on the net and they only use the net on the host for email. The ethernet cable between them is what is used for the 2nd pc to access the shared host folders. So a gigabit switch would increase the speed even with a existing direct ethernet connection between them even though they are both already gigabit compliant adapters?

That definitely changes things.

I would do it a different way than just having them connected via a cable. There are ways to share the internet connection and then share the files, and I would do it that way. But it doenst sound like your client wants to do it that way.

After you set static IP's, and go away. What happens if your client gets a new ISP, and setups a modem and a router. its going to be a nightmare for the client (if they dont call you first, and a lot of times they dont) depending on how you set it up, and then they might think you didnt do it right. I would remove any chance of them changing it down the road and making you look bad (even when you did it right). There are a couple of ways to do it right in this situation, but really only one way of making sure its strategic setup down the road. IMO

 

[YeOldeStonecat]

Client doesn't want 2nd PC to even touch the internet. We have lots of setups this way. Literally...physically, no way for a PC to get to the gateway. Thus..a router isn't needed to connect these two computers.

The first computer is the so called "server"..and with businesses...it's very common (usually preferred) to have your "server" set on a static IP address. Granted this is just a desktop OS, and not a true server...but still. The ISPs techs are usually (99.9% of the time) never allowed by their employer (the ISP) to touch a businesses computers.

A static IP takes about 30 seconds or less per computer.
Network adapter settings...TCP/IP..192.168.10.10/255.255.255.0 for one and 192.168.10.11/255.255.255.0 for the second..there, done. That was quick! Go check netbios 'n jumbo frames...another 15 seconds each. Phew!

Gotta change network settings again down the road a year or two due to something changing..takes another 30 seconds or so...it's no biggie! Mention it to client if you think they won't call you when things change in a year or so. Leave business card taped to side of computer tower...solves the problem, gets you business in a year or two. It's not the goal of settings things up this way..setting it up properly is the way to go. Servers should be static. Without a domain controller to manage DNS, you want to avoid master browser issues and poor name resolution resulting from no DNS...so static IPs and enabling netbios is a "best practice".

If two computers (or more) have to share an internet connection, a router is my preferred method. But in this case...2nd PC doesn't even touch the internet...there's no reason for a router.

For just 2 computers...both of the same make/model...thus same NIC...a direct connection is actually ideal. A switch will complicate things, and will add zero..nothing..nada...for benefits. It'll probably even perform slower than direct NIC to NIC.

 

[jbartlett323]

Client doesn't want 2nd PC to even touch the internet. We have lots of setups this way. Literally...physically, no way for a PC to get to the gateway. Thus..a router isn't needed to connect these two computers.

The first computer is the so called "server"..and with businesses...it's very common (usually preferred) to have your "server" set on a static IP address. Granted this is just a desktop OS, and not a true server...but still. The ISPs techs are usually (99.9% of the time) never allowed by their employer (the ISP) to touch a businesses computers.

A static IP takes about 30 seconds or less per computer.
Network adapter settings...TCP/IP..192.168.10.10/255.255.255.0 for one and 192.168.10.11/255.255.255.0 for the second..there, done. That was quick! Go check netbios 'n jumbo frames...another 15 seconds each. Phew!

Gotta change network settings again down the road a year or two due to something changing..takes another 30 seconds or so...it's no biggie! Mention it to client if you think they won't call you when things change in a year or so. Leave business card taped to side of computer tower...solves the problem, gets you business in a year or two. It's not the goal of settings things up this way..setting it up properly is the way to go. Servers should be static. Without a domain controller to manage DNS, you want to avoid master browser issues and poor name resolution resulting from no DNS...so static IPs and enabling netbios is a "best practice".

If two computers (or more) have to share an internet connection, a router is my preferred method. But in this case...2nd PC doesn't even touch the internet...there's no reason for a router.

For just 2 computers...both of the same make/model...thus same NIC...a direct connection is actually ideal. A switch will complicate things, and will add zero..nothing..nada...for benefits. It'll probably even perform slower than direct NIC to NIC.

I agree, I only said router for plug-and-play. Your right though, this setup is pie and no networking gear is required. And I have seen APIPA cause issues on nets like this. Set static all is good. Like the frames ides too though...

 

[Knightsman]

Client doesn't want 2nd PC to even touch the internet. We have lots of setups this way. Literally...physically, no way for a PC to get to the gateway. Thus..a router isn't needed to connect these two computers.

The first computer is the so called "server"..and with businesses...it's very common (usually preferred) to have your "server" set on a static IP address. Granted this is just a desktop OS, and not a true server...but still. The ISPs techs are usually (99.9% of the time) never allowed by their employer (the ISP) to touch a businesses computers.

A static IP takes about 30 seconds or less per computer.
Network adapter settings...TCP/IP..192.168.10.10/255.255.255.0 for one and 192.168.10.11/255.255.255.0 for the second..there, done. That was quick! Go check netbios 'n jumbo frames...another 15 seconds each. Phew!

Gotta change network settings again down the road a year or two due to something changing..takes another 30 seconds or so...it's no biggie! Mention it to client if you think they won't call you when things change in a year or so. Leave business card taped to side of computer tower...solves the problem, gets you business in a year or two. It's not the goal of settings things up this way..setting it up properly is the way to go. Servers should be static. Without a domain controller to manage DNS, you want to avoid master browser issues and poor name resolution resulting from no DNS...so static IPs and enabling netbios is a "best practice".

If two computers (or more) have to share an internet connection, a router is my preferred method. But in this case...2nd PC doesn't even touch the internet...there's no reason for a router.

For just 2 computers...both of the same make/model...thus same NIC...a direct connection is actually ideal. A switch will complicate things, and will add zero..nothing..nada...for benefits. It'll probably even perform slower than direct NIC to NIC.

The point of the router isnt for the internt, its for a DHCP server. The benefit it adds, is if he goes away, and the client goes to add real internet to the mix, he probably will not know what to do, and blame him. Seen it happen.

If it was my own setup, id run a wire too, but customes are crazy, and you have to accommodate for that.

 

[Vicenarian]

The real question is, why aren't you running 10Gb fiber between the two hosts and Solid State Drives?

 

[ell]

The real question is, why aren't you running 10Gb fiber between the two hosts and Solid State Drives?

LOL- if you saw my customers you would know why....we're talking a trucking/storage family owner biz here, a little porn and grease on the host pc, this is why the client doesn't need to be on the net! (and thats the way THEY want it) When I got him to buy the new systems they were on one circa '98 tower and a 50 lb CRT.