• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

.bin files

W

who

Weaksauce
Joined
Jan 23, 2005
Messages
72
ok is there a proggy or can someone tell me how to create a .bin file. i want the file when opened to run command>ipconfig/release then ipconfig/renew straight from my desktop can some one please tell me how to do this
 
This is about as vague as it gets, but I'm going with Ice Czar thinking you want a .bat file.

Just open notepad, type in the DOS commands you want to run, and save it as a .bat. Then store it on your desktop if you want.

On a somewhat related note, why do you need to run a release/renew everytime you boot? Sounds like you're either not understanding something about a network, our you're having some network problem.
 
djnes said:
This is about as vague as it gets, but I'm going with Ice Czar thinking you want a .bat file.

Just open notepad, type in the DOS commands you want to run, and save it as a .bat. Then store it on your desktop if you want.

On a somewhat related note, why do you need to run a release/renew everytime you boot? Sounds like you're either not understanding something about a network, our you're having some network problem.
Click to expand...

Im thinking along the same lines, or...maybe hes using a proxy and thinks he needs to do this to change back to original IP for some reason or another. Either way your right, pretty vague on the needs there :confused:
 
thanks for the help. also i have to run this every once in a while cause i have a crappy modem and this is all i can do to get on net
 
who said:
thanks for the help. also i have to run this every once in a while cause i have a crappy modem and this is all i can do to get on net
Click to expand...
If it's a broadband connection, you should have a router on it....and this problem would be solved.
 
If the modem itself is having issues with assining Ip address to the pc then a router will not fix the problem.. the modem is having ip issues so it wont be able to provide the needed ip addressing info to the router and then the router will not be able to allow him internet access.. As far as pc to pc networking goes it would solve that issue but not his internet which I think hes maybe suggesting hes having a issue with since hes not using a router to begin with ...
 
None of the modems assign an IP address to the PC, that's the job of a DHCP server, either in the router or on the broadband network. If the modem isn't "talking" to the ISP's network, then a release / renew isn't going to solve that problem anyway, so it would be a side issue of this thread. If release / renew does fix the problem, a router would solve this.
 
modems do assign ip address to the pc..there generally refered to as a gateway ( By the ISP company's)...If hes using just a chaepo modem with no type of dhcp services on it then the computers dhcp service is assigning the ip info. which would lead me to believe he may have a network protocol thats needs reinstalled or is configured incorrectly..



to the original thread stater give some more info next time you post a problem in need on help.. we here can be of more assistance.... :D
 
djnes said:
None of the modems assign an IP address to the PC, that's the job of a DHCP server, either in the router or on the broadband network.
Click to expand...

But a modem can lose the signal for some reason or another, and once it gains the signal back, it may pick up a new IP, in which place he would need to release/renew on the PC.

If the modem isn't "talking" to the ISP's network, then a release / renew isn't going to solve that problem anyway, so it would be a side issue of this thread.
Click to expand...

True, the modem needs to have a signal and be able to communicate with the ISP.

If release / renew does fix the problem, a router would solve this.
Click to expand...

Just having a router will not change anything. Modem-->Router-->PC....modem loses IP, router still uses IP, and if modem picks up new IP, router has wrong IP until restarted/renewed. Correct?
 
sounds like another possibility to me.. :D ... we dont have alot of details to work with here so its anyones guess at what needs diagnosed here..
 
PaHick said:
Just having a router will not change anything. Modem-->Router-->PC....modem loses IP, router still uses IP, and if modem picks up new IP, router has wrong IP until restarted/renewed. Correct?
Click to expand...
I was under the impression the router holds the IP from the ISP, so if the modem loses connection, when it's restored, the router will go out and get the new address. Modems typically have nothing to do with the IP addressing in general. Since the router will obtain the new WAN IP, he won't have to release / renew on his own computer because his internal LAN NAT'd address will remain the same.

That's what I meant about the router solving the problem. As long as his connection to the touer from his PC is fine, he won't have to change anything on his own PC. The router handles all of the "work". Back when I had Comcast, and my connection would go down, it would be restored all the way to my PC automatically. I don't have downtime anymore since switching to RCN, but that's how it used to work with the Linksys routers.
 
djnes said:
I was under the impression the router holds the IP from the ISP, so if the modem loses connection, when it's restored, the router will go out and get the new address. Modems typically have nothing to do with the IP addressing in general. Since the router will obtain the new WAN IP, he won't have to release / renew on his own computer because his internal LAN NAT'd address will remain the same.
Click to expand...

A router doesnt "seek" an IP from the ISP. Think about it..what is in front of the router? The modem. The ISP sends an IP, which goes to the modem, which is where the router gets the IP from.

That's what I meant about the router solving the problem. As long as his connection to the touer from his PC is fine, he won't have to change anything on his own PC.
Click to expand...

And we arent sure, but I think thats the problem, he is dropping his connection. Need more details but his signal strength may be too high/weak and his modem dropping connection. As long as the IP is the same,, his router will "resume" function. But in alot of cases your IP will change once the modem loses signal from the ISP.

The connection from PC to router can remain great, but if the modem loses connection he has no service. And if the IP changes, the router and PC need reset.
 
An ISP doesn't just send an IP address to a cable modem. The cable modem is little more than a bridge. The client(whether it is a PC or a router) sends a dhcp discover out over the wire. Any dhcp servers seeing the discover will send a dhcp offer to the client. The client chooses an offer(should only get one if everything is configured properly) and sends a dhcp request. The respective server then sends an acknowledgement, and all is good. All the cable modem is doing during all this is bridging an ethernet network and a docsis network. So the client does indeed "seek" an IP address from the ISP.

And if the connection to the cable network is being dropped at random, a cable tech should investigate to see what is happening, because obviously it shouldn't be happening. Might be a signal strength/quality issue. Though if it is at random it might be a bit difficult to track down.
 
jpmkm said:
An ISP doesn't just send an IP address to a cable modem. The cable modem is little more than a bridge. The client(whether it is a PC or a router) sends a dhcp discover out over the wire. Any dhcp servers seeing the discover will send a dhcp offer to the client. The client chooses an offer(should only get one if everything is configured properly) and sends a dhcp request. The respective server then sends an acknowledgement, and all is good. All the cable modem is doing during all this is bridging an ethernet network and a docsis network. So the client does indeed "seek" an IP address from the ISP.

And if the connection to the cable network is being dropped at random, a cable tech should investigate to see what is happening, because obviously it shouldn't be happening. Might be a signal strength/quality issue. Though if it is at random it might be a bit difficult to track down.
Click to expand...

I was trying to simplify things, but we are almost on the same page..lol. The router doesnt have to be there to get an IP. The modem is in charge of getting the IP from the ISP. The router "distributes" the IP. Correct? Last I knew routers didnt have MAC address's, modems and NIC's do. The router is the bridge.
 
The router is not a bridge; it is a router(of sorts). Bridges convert from one network type to another; there is no routing involved. A router can connect one network type to another, but it's main purpose is to route. Granted, the main purpose of most home routers is to provide NAT, but there's still an amount of routing going on. Cable modems do indeed have MAC addresses. So do routers. That's how the router is able to get the IP address. The router itself is what requests the IP address from the ISP, and it is what gets the IP address. You obviously don't need a router to get an IP address, but you need a client in there somewhere to get an IP address. If you just hook up a cable modem to the line, you aren't going to have an IP address(it might have something internal to the cable network, but nothing that would be accessible to the outside world).

So, in other words: the cable modem is the bridge. The router is the router.
 
jpmkm said:
The router is not a bridge; it is a router(of sorts). Bridges convert from one network type to another; there is no routing involved. A router can connect one network type to another, but it's main purpose is to route. Granted, the main purpose of most home routers is to provide NAT, but there's still an amount of routing going on. Cable modems do indeed have MAC addresses. So do routers. That's how the router is able to get the IP address. The router itself is what requests the IP address from the ISP, and it is what gets the IP address. You obviously don't need a router to get an IP address, but you need a client in there somewhere to get an IP address. If you just hook up a cable modem to the line, you aren't going to have an IP address(it might have something internal to the cable network, but nothing that would be accessible to the outside world).

So, in other words: the cable modem is the bridge. The router is the router.
Click to expand...

OK, I stand corrected. Either way we dont even know if he has a router...lol. The main point is if hes losing the connection at the modem, a router will not help.

EDIT**

What im saying is I can unplug my PC, go out in the garage and reset my modem and router, which 9/10 times will give me a new IP. Assuming it did, and my PC wasnt turned off, when I hook the Cat6 cable back into the NIC I will have limited/no connectivity until I release/renew my IP.
 
You must log in or register to reply here.
Back
Top