• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

@home and Local Networking

C

Crabapple

Member
Just a question...
At my house i have 3 computers with seperately purchased IP's -a -b -c ... they are all connected through a hub that is connected to my Cable Modem. 🙂.. Now.. about 2-3months ago i was able to share Files, printers, play games at LAN speeds etc.. now however the highest transfer rate i can get from comp to comp is about 30kb/s. Does anyone know why @home changed this. 🙂
 
If you're talking about your transfer rate between your computers, nothing @home does can change that. It's all going on between the computers and your hub.

Why it could be...well, could be something with the cabling or the hub I suppose...
 
I've never personally had this problem but a co-worker of mine has. Check to see if all your @Home issued IP addresses are the same for the first 3 blocks (ie 1.2.3.x where all your IPs are 1.2.3.x). If the first 3 blocks don't match up, then certain protocols, like Windows filesharing may be going through your cable modem and coming back to the other machine where you'd be limited by the cable modem caps rather than your LAN.

Now I don't know for sure whether this happens or not, but a rather knowledgable coworker of mine did have a similar sounding problem, specifically with windows filesharing on his LAN with @Home where his paid for IPs were from different address spaces.

Gaidin
 
I don`t think they would throw 3 different IP's from 3 different subnets at you.

Since you aren`t really running a LAN, it sounds as though you are going through
the @Home network between each IP first, not just across the room. Therefore, you
are restricted to there bandwidth cap. I may be wrong, though.

Buy a nice Cable router (Netgear RT314) and then you`ll have 100Mbs transfers within
your LAN.
 
No, because then it wouldn't be able to resolve the IP. I would suggest CANCELLING your extra IPs fom @home considering they're wasted money, then buy a SOHO gateway (NetGear RT314 for example) and share your cable modem at 100mbits per second and not have to pay @home for extra IPs.
 


<< No, because then it wouldn't be able to resolve the IP. I would suggest CANCELLING your extra IPs fom @home considering they're wasted money, then buy a SOHO gateway (NetGear RT314 for example) and share your cable modem at 100mbits per second and not have to pay @home for extra IPs. >>

I SECOND this.. Saving $$$ is always preferable to me.

Keep in mind that some types of applications (notably, certain Internet gaming services and videoconferencing apps) don't work through NAT routers (like the NetGear, Linksys or SMC [my favorite] SOHO routers) without special configuration and support for port range forwarding and other little extras.

P.S. I have a brother-in-law in TX who flatly refuses to do this, even tho he doesn't game or vid-conference. He's a Mac user, so no big shock.
 
No, because then it wouldn't be able to resolve the IP

Why would the IP matter? If they're on the same subnet and workgroup I thought it doesn't matter. Or does the @home setup wizard jack up the settings somehow?
 


<< No, because then it wouldn't be able to resolve the IP

Why would the IP matter? If they're on the same subnet and workgroup I thought it doesn't matter. Or does the @home setup wizard jack up the settings somehow? >>

Err...if you unbind IP and bind NetBLOOEY, then the machines could talk to each other (via NetBLOODY), but you'd have NO Internet connectivity (no IP address, no talkie).
 
Not to bandwagon, but don't buy the extra IP addy's. There really is no advantage since @Home prohibits servers. Take the money you're laying out monthly ($5/IP IIRC) and buy an SMC Barricade to share the connection. It has 10/100 connectivity and you can also share a printer with it.
 
The reason the (LAN) traffic is going to @home (assuming that is the problem, which seems highly likely).

W2K by default sets up TCP/IP as the sole network protocol, and binds NetBIOS to it. (&quot;Enable netbios over TCP/IP&quot😉. So all the netbios traffic is carried across IP, which needs DNS (or some sort of resolution) to find the other machines.

Solution:
Install a second protocol, NetBEUI, on all the workstations, and make it the default protocol.
Then go to TCP/IP properties, and disable NetBIOS over TCP/IP.
Also unbind all the MS clients from the TCP/IP protocol--the OS will burp at this, but it's ok.

Internet tools only talk IP, so they'll go right to the TCP/IP stack. All other applications will hit nbt, and do a local network broadcast to find the other computers, without routing it out the @home.

Other gurus: double-check, I often put in NetBEIU instead of NetBIOS, even though they're not quite the same.

--Woodie
 
Err...if you unbind IP and bind NetBLOOEY, then the machines could talk to each other (via NetBLOODY), but you'd have NO Internet connectivity (no IP address, no talkie).

I think Woodie is backing up what I'm trying to say. You are installing Netbui and unbinding it from TCP/IP for File and Print Sharing and Client for Microsoft Networks. Since Netbui isn't routable (and it's not IP) the modem will have nothing to do with it. This is how I have my LAN setup and it works just fine with @home...

 


<< I think Woodie is backing up what I'm trying to say. You are installing Netbui and unbinding it from TCP/IP for File and Print Sharing and Client for Microsoft Networks. >>

Aaaaack! I screwed the pooch on that one. 😱
You and Woodie are right.

Although, in my defense, your original explanation was not nearly as clear as Woodie's. The highlighted &quot;it&quot; is where I'm getting confused. In fact, just to clarify what you're saying...

Installed Network Components
Client for Microsoft Networks
NIC (whatever you are using)
NetBEUI -> NIC (On Bindings Tab, &quot;Client for Microsoft Networks&quot; and &quot;File and Printer Sharing&quot; ARE checked)
TCP/IP -> NIC (On Bindings Tab, &quot;Client for Microsoft Networks&quot; and &quot;File and Printer Sharing&quot; are NOT checked)
File and Printer Sharing for Microsoft Networks

In other words: You are installing NetBEUI and unbinding TCP/IP from File and Print Sharing and Client for Microsoft Networks.

Personally, I hate NetBEUI. Wouldn't have it loaded, even for a home LAN.
If an application requires IP within your local LAN--like a LAN game or NetMeeting (my 18 month old thinks it's funny to see Daddy in a window on her Mommy's laptop in another room, and then likes to go run and see Mommy in a window on Daddy's machine, ad infinitum)--wouldn't that still go through the modem and @Home's 'bone?
 
crabapple,

please post the IP address, subnet mask and gateway for each PC. I'm guessing they are on different subnets and this is causing your problem because you're addresses have to get routed through @home's network.

If they are then no biggie...just install netbeui and you'll be fine. If however they are on the same subnet then this is very peculiar.
 
TallGeese has a point about using IP based appls from one machine to another. Basically, @home is screwing things up by providing IP addy's from different subnets to devices on a single subnet.

The more elegant (and cheaper 🙂) solution is to do the NATing thing behind a router or fw or something. That way, web-browsing to the &quot;server&quot; on the local LAN it doesn't go through @home.

--Woodie
 
Subnets are all the same..

255.255.252.0

but when i do a tracert from one comp to the other it goes first to my gateway 24.112.196.1 and then to my other IP
 


<< TallGeese has a point about using IP based appls from one machine to another. Basically, @home is screwing things up by providing IP addy's from different subnets to devices on a single subnet.

The more elegant (and cheaper 🙂) solution is to do the NATing thing behind a router or fw or something. That way, web-browsing to the &quot;server&quot; on the local LAN it doesn't go through @home.

--Woodie >>



Why not to choose this option
#1. @Home Doesnt Support It. (and with their constant downtime -- whos gonna help me)
#2. They don't allow it -- cable cops will come knockin at your door one day.
#3. I like the separate ip's.
#4. its only 9.95$ (Canadian)
#5. I also have my tenants in my basement hooked up this way which saves me a lot of money..
since i make them pay the entire $39.95 🙂 🙂 😱


 


<< Subnets are all the same..

255.255.252.0

but when i do a tracert from one comp to the other it goes first to my gateway 24.112.196.1 and then to my other IP >>




actually wait... one is
255.255.252.0
the other is
255.255.254.0


ha.... i found our problem
 
<< #1. @Home Doesnt Support It. (and with their constant downtime -- whos gonna help me) >>

You don't have to tell them you're using a gateway router, they would never know. They can't tell the difference.

<< #2. They don't allow it -- cable cops will come knockin at your door one day. >>

See above comment. There is no way to know that @Home will know you're using a router to share your connection. And besides, who are they to say that you can't share your connection that you PAID for amongst several computers?

<< #3. I like the separate ip's. >>

Uhh...why? 😕

<< #4. its only 9.95$ (Canadian) >>

It would be only $0/month (Canadian) if you had a router

<< #5. I also have my tenants in my basement hooked up this way which saves me a lot of money since i make them pay the entire $39.95 >>

You can still make them pay the entire $40, they're still getting internet access...
 
crabapple
please post IP address, subnet mask and gateway of each machine.

just because subnet mask is the same does not mean IP subnet is the same. we're very close to fixing your problem here.crabapple

what at home is doing to your network is considered extremely poor design

<edit> get a small soho router and fix all your problems.
 


<< crabapple
please post IP address, subnet mask and gateway of each machine.

just because subnet mask is the same does not mean IP subnet is the same. we're very close to fixing your problem here.crabapple

what at home is doing to your network is considered extremely poor design

<edit> get a small soho router and fix all your problems. >>


okay here they are

PC1 - IP: 24.112.169.119
SUBNET: 255.255.254.0
Gateway:24.112.196.1
PC2 - IP: 24.112.198.38
SUBNET: 255.255.252.0
Gateway: 24.112.196.1

 


<< << #1. @Home Doesnt Support It. (and with their constant downtime -- whos gonna help me) >>

You don't have to tell them you're using a gateway router, they would never know. They can't tell the difference.

<< #2. They don't allow it -- cable cops will come knockin at your door one day. >>

See above comment. There is no way to know that @Home will know you're using a router to share your connection. And besides, who are they to say that you can't share your connection that you PAID for amongst several computers?

<< #3. I like the separate ip's. >>

Uhh...why? 😕

<< #4. its only 9.95$ (Canadian) >>

It would be only $0/month (Canadian) if you had a router

<< #5. I also have my tenants in my basement hooked up this way which saves me a lot of money since i make them pay the entire $39.95 >>

You can still make them pay the entire $40, they're still getting internet access... >>




I thought that you were talkin about that 3com router/gateway that takes the IP you have and makes several new ones... But if thats not the case then i have already tried that and the problem is that me being the Avid gamer like to play games on my LAN so one IP would not do the Job. 🙂
 
if you are adament about not getting a router 😕 then there is not much we can do to help you in terms of IP applications. By definition you have to go to your gateway to reach remote ip networks. problem is you have two separate IP networks running on the same broadcast domain/physical cable. (this is about the worst thing you can do in networking called multinetting) Maybe your provider is in the middle of an upgrade or switch and they have to multinet during the swapout?

If you just need microsoft based file and printer sharing then load netbeui on your machines and that will solve that problem.

As far as the IP addresses are concerned, see if you can get your provider to give you static addresses from the same IP subnet. That is the only way I can see to fix your problem. You could try to expand the subnet masks to 255.255.128.0, but man that is cutting out a lot of address and really the wrong way to go.

hope this helps

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top