Win7 Internet Connection to the web Failing
We are unable to connect to the internet via our new Windows7 box.
We have 4 other computers on the network, which we can see fine, we just cannot get out to the web.
In services.msc, we have these set to automatically load:
SSDP Discovery
Computer Browser
TCP/IP NetBios Helper
Server
We have a static IP address assigned in the network card, and netbios over TCP/IP is on.
We have manually hooked a cable from a different network to this box, and it hits the internet fine. It's just going through this hardware/firewall router that it fails. We are using Netgear. All of our settings are the same for this box, as they are on the other 4 boxes that connect fine.
Our Outgoing settings on the netgear firewall are set to ALLOW ALL and there are no other settings to turn off anything outgoing.
We have tried with both the Windows Firewall on and off, with no differences.
We are using our AT&T T1 service privider's DNS IP Resolver addresses on the network card and in the firewall.
Can someone please help? Our globe is disabled.
Thanks!
We have 4 other computers on the network, which we can see fine, we just cannot get out to the web.
In services.msc, we have these set to automatically load:
SSDP Discovery
Computer Browser
TCP/IP NetBios Helper
Server
We have a static IP address assigned in the network card, and netbios over TCP/IP is on.
We have manually hooked a cable from a different network to this box, and it hits the internet fine. It's just going through this hardware/firewall router that it fails. We are using Netgear. All of our settings are the same for this box, as they are on the other 4 boxes that connect fine.
Our Outgoing settings on the netgear firewall are set to ALLOW ALL and there are no other settings to turn off anything outgoing.
We have tried with both the Windows Firewall on and off, with no differences.
We are using our AT&T T1 service privider's DNS IP Resolver addresses on the network card and in the firewall.
Can someone please help? Our globe is disabled.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
if I type in ipconfig /all and provide you with all that information here in a public forum, isn't that messing with my security?
Also, since I'm trying to get OUT on the network and not allowing people IN, how does my publishing that here help answer the question?
I assigned a local address, such as 192.168.10.x to the card, static.
I didn't assign a static DNS. I assigned the DNS of our resolver IP's:
>>We are using our AT&T T1 service privider's DNS IP Resolver addresses on the network card and in the firewall.
I put those resolver IP's both on the card in the DNS area and on the router for the DNS spot.
Also, since I'm trying to get OUT on the network and not allowing people IN, how does my publishing that here help answer the question?
I assigned a local address, such as 192.168.10.x to the card, static.
I didn't assign a static DNS. I assigned the DNS of our resolver IP's:
>>We are using our AT&T T1 service privider's DNS IP Resolver addresses on the network card and in the firewall.
I put those resolver IP's both on the card in the DNS area and on the router for the DNS spot.
ASKER
IP: 192.168.10.8
Gateway: 192.168.10.1
DNS server:
12.127.16.67
12.127.17.71
Gateway: 192.168.10.1
DNS server:
12.127.16.67
12.127.17.71
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
subnet mask:
255.255.255.0
255.255.255.0
ASKER
>>Let your second dns server as is but change the first one 12.127.16.67 for your gateway adress: 192.168.10.1
On the card, I changed the first one to the 10.1 address. However, it did not fix the problem.
On the card, I changed the first one to the 10.1 address. However, it did not fix the problem.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
>>You initially said that pinging the gateway failed. So I just want to verify that if you ping 192.168.10.1 from that machine, you get a time-out. Try pinging the same gateway from another machine on the network. If it works from other machines, but not from that specific one, the firewall device is blocking the connection. Try loggin into the Netgear firewall and see what is shows regarding that PC.
yes, from this box it fails (192.168.10.1)
From the other boxes it pings fine.
I have looked at every single page of the firewall, and the Langroups has this box on it, but there is nothing else specific to 10.8. The outgoing firewall options are all Open by default and I have no options set up.
yes, all other working computers use the same IP range, DNS Ip's and gateway.
We bought two new boxes, one is windows7 and another is windows2008 web server, and both have the same problem getting out on the internet.
Our other boxes, Vista, Windows 2008 web server, Windows 2000 web server OS's-- none have any problems reaching the web.
Just the new ones we are trying to add. We've swapped their cables with the working one's slots and that does nothing.
yes, from this box it fails (192.168.10.1)
From the other boxes it pings fine.
I have looked at every single page of the firewall, and the Langroups has this box on it, but there is nothing else specific to 10.8. The outgoing firewall options are all Open by default and I have no options set up.
yes, all other working computers use the same IP range, DNS Ip's and gateway.
We bought two new boxes, one is windows7 and another is windows2008 web server, and both have the same problem getting out on the internet.
Our other boxes, Vista, Windows 2008 web server, Windows 2000 web server OS's-- none have any problems reaching the web.
Just the new ones we are trying to add. We've swapped their cables with the working one's slots and that does nothing.
ASKER
BTW, these boxes DO recognize and access other computers on the network. They just don't recognize getting out on the internet.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My new computer is in the same Group1 Langroup.
I setup the computer and put in the mac address and on save, it automatically updates it if I typed it wrong. But I get the mac address from the physical address of ipconfig /all
So yes, I've done that.
I setup the computer and put in the mac address and on save, it automatically updates it if I typed it wrong. But I get the mac address from the physical address of ipconfig /all
So yes, I've done that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes, 209.85.225.99 times out on ping.
I can't even ping my own gateway, so didn't figure it would work. :)
yes, I know it's a firewall router issue, because, as I said:
>>We have manually hooked a cable from a different network to this box, and it hits the internet fine. It's just going through this hardware/firewall router that it fails. We are using Netgear. All of our settings are the same for this box, as they are on the other 4 boxes that connect fine.
I need to know what to do to fix the situation on this firewall/router. We have turned off the software firewall and that does nothing.
Let me give a little background:
About 4 days ago, our mail server stopped sending mails. For no apparent reason. Just every single mail server in the world, it connects, then loses connection,and doesn't send the mail. Period. So we've been looking at why that is happening. Decided maybe the old Win2000 OS and old machine and old version of mail server was the problem, so we bought a new machine, new merak icewarp mail server, new OS, and now we can't get the machine to find the web.
Now on the old mail server, it can find the web, it can relay pop3 (we can receive mails), it can even send SMTP to anyone with an addy on our own mail server, just nowhere else in the world. But connecting to the web wasn't a problem.
On the new box, connecting to the web is our problem. We bought another new box for a web server, and same problem (it is Windows 2008 web server). So yeah, we are at a quandry what is going on with our firewall/router that we can't get SMTP on our mail server and now this. And we had made absolutely no changes to our network, mail server, firewall, or anything. Just out of the blue!
Any ideas?
Thanks.
I can't even ping my own gateway, so didn't figure it would work. :)
yes, I know it's a firewall router issue, because, as I said:
>>We have manually hooked a cable from a different network to this box, and it hits the internet fine. It's just going through this hardware/firewall router that it fails. We are using Netgear. All of our settings are the same for this box, as they are on the other 4 boxes that connect fine.
I need to know what to do to fix the situation on this firewall/router. We have turned off the software firewall and that does nothing.
Let me give a little background:
About 4 days ago, our mail server stopped sending mails. For no apparent reason. Just every single mail server in the world, it connects, then loses connection,and doesn't send the mail. Period. So we've been looking at why that is happening. Decided maybe the old Win2000 OS and old machine and old version of mail server was the problem, so we bought a new machine, new merak icewarp mail server, new OS, and now we can't get the machine to find the web.
Now on the old mail server, it can find the web, it can relay pop3 (we can receive mails), it can even send SMTP to anyone with an addy on our own mail server, just nowhere else in the world. But connecting to the web wasn't a problem.
On the new box, connecting to the web is our problem. We bought another new box for a web server, and same problem (it is Windows 2008 web server). So yeah, we are at a quandry what is going on with our firewall/router that we can't get SMTP on our mail server and now this. And we had made absolutely no changes to our network, mail server, firewall, or anything. Just out of the blue!
Any ideas?
Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It's a netGear ProSafe VPN Firewall FVX538.
Firmware version 3.0.3-13. Secondary firmware version 2.1.0.7
Thanks!
Firmware version 3.0.3-13. Secondary firmware version 2.1.0.7
Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
>>Our Outgoing settings on the netgear firewall are set to ALLOW ALL and there are no other settings to turn off anything outgoing.
Mac Address filtering: None
Everything has been running fine on this firewall for two years, until two days ago the SMTP stopped sending mails and now we can't hook up an additional computer.
Tomorrow we're going to call Netgear first thing, and maybe even run out and buy a new one.
Mac Address filtering: None
Everything has been running fine on this firewall for two years, until two days ago the SMTP stopped sending mails and now we can't hook up an additional computer.
Tomorrow we're going to call Netgear first thing, and maybe even run out and buy a new one.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We purchased a new firewall. It allows the connections for the two new boxes as well as it now fixes the SMTP problem for the mailserver.
However, we had to send the 10,000 mails that had been accumulating and hook back up the old firewall that didn't send the SMTP because the new one gives an error everytime we try to hook up HTTP to multiple boxes. It says that you're only allowed to assign to a port only once. (something like that anyway).
What's that all about? Do some firewalls only allow one port assignment per firewall? Like HTTP, we allow it on one web server. But when we tried to assign it to a second web server, it said it was only allowed to assign a port just the once. Same with the DSNSQL port, and the all the ports.
Our old firewall didn't have that problem. This one was cheaper by about a third, but entirely useless if that's the case. (We have upgraded our firmware to the latest version).
However, we had to send the 10,000 mails that had been accumulating and hook back up the old firewall that didn't send the SMTP because the new one gives an error everytime we try to hook up HTTP to multiple boxes. It says that you're only allowed to assign to a port only once. (something like that anyway).
What's that all about? Do some firewalls only allow one port assignment per firewall? Like HTTP, we allow it on one web server. But when we tried to assign it to a second web server, it said it was only allowed to assign a port just the once. Same with the DSNSQL port, and the all the ports.
Our old firewall didn't have that problem. This one was cheaper by about a third, but entirely useless if that's the case. (We have upgraded our firmware to the latest version).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My problem with not being able to assign multiple ports (and yes, I have multiple public IP addresses)... was because the Netgear Prosafe firewall box we purchased doesn't support it. It's a cheap version.
ASKER
Ok, this is fixed.
Here's the scoop:
We purchase another identical netgear firewall to what we have. Installed it, updated the firmware, reloaded the config file, and it failed too.
So we reset it to factory settings, updated the firmware and manually put in all of our config settings. That did it. It was apparentl a bad config file.
I had even used a backup version from over a month ago, and still it was bad. So go figure. It didn't break down a month ago, only a week ago, so why the month old config file failed too, who knows. But all is well now.
Thanks all!
Here's the scoop:
We purchase another identical netgear firewall to what we have. Installed it, updated the firmware, reloaded the config file, and it failed too.
So we reset it to factory settings, updated the firmware and manually put in all of our config settings. That did it. It was apparentl a bad config file.
I had even used a backup version from over a month ago, and still it was bad. So go figure. It didn't break down a month ago, only a week ago, so why the month old config file failed too, who knows. But all is well now.
Thanks all!
ASKER
No I get a request timed out.