Hi all, This is for all you network gurus out there. I'm having a weird problem, and I need your help in solving it. Any help is greatly appreciated! I have 2 machines, 1 is my firewall ("fortress") and the other is my main workstation ("lancelot"). Currently, lancelot is my machine that is connected to the net and handles all of my server/workstation duties. I'm trying to integrate the new machine, and make lancelot go through it to see the net, providing some protection to my workstation. Hardware-wise, there are 2 known-to-be working ethernet cards in both machines. I have disabled eth1 in lancelot, and ran the network cable that was going from eth0 to my DSL gateway to port 2 of my Intel 8port 10/100 fast hub. I ran a 2nd cable from eth1 of fortress to port 1 of the same hub, and ran a 3rd cable from eth0 of fortress to the DSL gateway. I configured lancelot's eth0 to have IP address 192.168.0.2, added the nameservers (216.227.49.36 and 216.227.80.36) and made the default route to be 192.168.0.1. I configured fortress' eth0 to have a DHCP assigned IP address, and eth1 to be 192.168.0.1. So far, fortress can pull a valid IP from the gateway, and see the Internet just fine. The problem is that I can't get fortress and lancelot to "see" each other through the LAN hub. When I ping lancelot from fortress, I see the light blinking on the hub, but I get 100% packet loss. The same goes for lancelot when I ping fortress... 100% packet loss, and I can see the light blinking on the hub. When the light is blinking for the machine that I'm pinging FROM, the light for the machine that I'm pinging TO does not blink in unison. I've tried cycling power on everything -- the hub, the gateway, and both machines, just to see if it was some kind of residual memory in the hardware. When I run "ifconfig", everything looks as it should. Why can't they see each other? Thanks for any help, Steven
fortress can see the internet, but not lancelot, right? what does the routing table look like? That is usually the culprit in these cases. You should have an entry like 192.168.0.0 255.255.255.0 eth1 Regards Anders On Saturday 07 July 2001 17:42, Steven Hatfield wrote:
Hi all, This is for all you network gurus out there. I'm having a weird problem, and I need your help in solving it. Any help is greatly appreciated!
I have 2 machines, 1 is my firewall ("fortress") and the other is my main workstation ("lancelot"). Currently, lancelot is my machine that is connected to the net and handles all of my server/workstation duties. I'm trying to integrate the new machine, and make lancelot go through it to see the net, providing some protection to my workstation.
Hardware-wise, there are 2 known-to-be working ethernet cards in both machines. I have disabled eth1 in lancelot, and ran the network cable that was going from eth0 to my DSL gateway to port 2 of my Intel 8port 10/100 fast hub. I ran a 2nd cable from eth1 of fortress to port 1 of the same hub, and ran a 3rd cable from eth0 of fortress to the DSL gateway.
I configured lancelot's eth0 to have IP address 192.168.0.2, added the nameservers (216.227.49.36 and 216.227.80.36) and made the default route to be 192.168.0.1.
I configured fortress' eth0 to have a DHCP assigned IP address, and eth1 to be 192.168.0.1.
So far, fortress can pull a valid IP from the gateway, and see the Internet just fine.
The problem is that I can't get fortress and lancelot to "see" each other through the LAN hub. When I ping lancelot from fortress, I see the light blinking on the hub, but I get 100% packet loss. The same goes for lancelot when I ping fortress... 100% packet loss, and I can see the light blinking on the hub. When the light is blinking for the machine that I'm pinging FROM, the light for the machine that I'm pinging TO does not blink in unison. I've tried cycling power on everything -- the hub, the gateway, and both machines, just to see if it was some kind of residual memory in the hardware.
When I run "ifconfig", everything looks as it should.
Why can't they see each other?
Thanks for any help, Steven
On Saturday 07 July 2001 11:49 am, Anders Johansson wrote:
fortress can see the internet, but not lancelot, right?
what does the routing table look like? That is usually the culprit in these cases. You should have an entry like 192.168.0.0 255.255.255.0 eth1
Ok, I've tried everything I can think of, but it still isn't working. I've attached a file called 'route.txt' that contains as much info as I can think to give. Any help is truly appreciated! Thanks, -Steven
Regards Anders
On Saturday 07 July 2001 17:42, Steven Hatfield wrote:
Hi all, This is for all you network gurus out there. I'm having a weird problem, and I need your help in solving it. Any help is greatly appreciated!
I have 2 machines, 1 is my firewall ("fortress") and the other is my main workstation ("lancelot"). Currently, lancelot is my machine that is connected to the net and handles all of my server/workstation duties. I'm trying to integrate the new machine, and make lancelot go through it to see the net, providing some protection to my workstation.
Hardware-wise, there are 2 known-to-be working ethernet cards in both machines. I have disabled eth1 in lancelot, and ran the network cable that was going from eth0 to my DSL gateway to port 2 of my Intel 8port 10/100 fast hub. I ran a 2nd cable from eth1 of fortress to port 1 of the same hub, and ran a 3rd cable from eth0 of fortress to the DSL gateway.
I configured lancelot's eth0 to have IP address 192.168.0.2, added the nameservers (216.227.49.36 and 216.227.80.36) and made the default route to be 192.168.0.1.
I configured fortress' eth0 to have a DHCP assigned IP address, and eth1 to be 192.168.0.1.
So far, fortress can pull a valid IP from the gateway, and see the Internet just fine.
The problem is that I can't get fortress and lancelot to "see" each other through the LAN hub. When I ping lancelot from fortress, I see the light blinking on the hub, but I get 100% packet loss. The same goes for lancelot when I ping fortress... 100% packet loss, and I can see the light blinking on the hub. When the light is blinking for the machine that I'm pinging FROM, the light for the machine that I'm pinging TO does not blink in unison. I've tried cycling power on everything -- the hub, the gateway, and both machines, just to see if it was some kind of residual memory in the hardware.
When I run "ifconfig", everything looks as it should.
Why can't they see each other?
Thanks for any help, Steven
Your routing tables look ok, aside from that lancelot doesn't have a default gateway, but that shouldn't stop it from seeing fortress. I assume you've tried this with fortress's firewall turned off. I have almost exactly the same setup that you have, and that's what burned me at first. I had set up the firewall so it blocked everything from the inside LAN including pings. If all else fails, I'd try to get a crossed TP cable and connect the computers straight through, without the hub, and see if they see each other then. On Saturday 07 July 2001 18:50, Steven Hatfield wrote:
On Saturday 07 July 2001 11:49 am, Anders Johansson wrote:
fortress can see the internet, but not lancelot, right?
what does the routing table look like? That is usually the culprit in these cases. You should have an entry like 192.168.0.0 255.255.255.0 eth1
Ok, I've tried everything I can think of, but it still isn't working. I've attached a file called 'route.txt' that contains as much info as I can think to give.
Any help is truly appreciated!
Thanks, -Steven
Regards Anders
On Saturday 07 July 2001 17:42, Steven Hatfield wrote:
Hi all, This is for all you network gurus out there. I'm having a weird problem, and I need your help in solving it. Any help is greatly appreciated!
I have 2 machines, 1 is my firewall ("fortress") and the other is my main workstation ("lancelot"). Currently, lancelot is my machine that is connected to the net and handles all of my server/workstation duties. I'm trying to integrate the new machine, and make lancelot go through it to see the net, providing some protection to my workstation.
Hardware-wise, there are 2 known-to-be working ethernet cards in both machines. I have disabled eth1 in lancelot, and ran the network cable that was going from eth0 to my DSL gateway to port 2 of my Intel 8port 10/100 fast hub. I ran a 2nd cable from eth1 of fortress to port 1 of the same hub, and ran a 3rd cable from eth0 of fortress to the DSL gateway.
I configured lancelot's eth0 to have IP address 192.168.0.2, added the nameservers (216.227.49.36 and 216.227.80.36) and made the default route to be 192.168.0.1.
I configured fortress' eth0 to have a DHCP assigned IP address, and eth1 to be 192.168.0.1.
So far, fortress can pull a valid IP from the gateway, and see the Internet just fine.
The problem is that I can't get fortress and lancelot to "see" each other through the LAN hub. When I ping lancelot from fortress, I see the light blinking on the hub, but I get 100% packet loss. The same goes for lancelot when I ping fortress... 100% packet loss, and I can see the light blinking on the hub. When the light is blinking for the machine that I'm pinging FROM, the light for the machine that I'm pinging TO does not blink in unison. I've tried cycling power on everything -- the hub, the gateway, and both machines, just to see if it was some kind of residual memory in the hardware.
When I run "ifconfig", everything looks as it should.
Why can't they see each other?
Thanks for any help, Steven
You're the man! It was the firewall script! Thanks! You ever need anything, just ask :) -Steven On Saturday 07 July 2001 12:56 pm, Anders Johansson wrote:
Your routing tables look ok, aside from that lancelot doesn't have a default gateway, but that shouldn't stop it from seeing fortress.
I assume you've tried this with fortress's firewall turned off. I have almost exactly the same setup that you have, and that's what burned me at first. I had set up the firewall so it blocked everything from the inside LAN including pings.
If all else fails, I'd try to get a crossed TP cable and connect the computers straight through, without the hub, and see if they see each other then.
On Saturday 07 July 2001 18:50, Steven Hatfield wrote:
On Saturday 07 July 2001 11:49 am, Anders Johansson wrote:
fortress can see the internet, but not lancelot, right?
what does the routing table look like? That is usually the culprit in these cases. You should have an entry like 192.168.0.0 255.255.255.0 eth1
Ok, I've tried everything I can think of, but it still isn't working. I've attached a file called 'route.txt' that contains as much info as I can think to give.
Any help is truly appreciated!
Thanks, -Steven
Regards Anders
On Saturday 07 July 2001 17:42, Steven Hatfield wrote:
Hi all, This is for all you network gurus out there. I'm having a weird problem, and I need your help in solving it. Any help is greatly appreciated!
I have 2 machines, 1 is my firewall ("fortress") and the other is my main workstation ("lancelot"). Currently, lancelot is my machine that is connected to the net and handles all of my server/workstation duties. I'm trying to integrate the new machine, and make lancelot go through it to see the net, providing some protection to my workstation.
Hardware-wise, there are 2 known-to-be working ethernet cards in both machines. I have disabled eth1 in lancelot, and ran the network cable that was going from eth0 to my DSL gateway to port 2 of my Intel 8port 10/100 fast hub. I ran a 2nd cable from eth1 of fortress to port 1 of the same hub, and ran a 3rd cable from eth0 of fortress to the DSL gateway.
I configured lancelot's eth0 to have IP address 192.168.0.2, added the nameservers (216.227.49.36 and 216.227.80.36) and made the default route to be 192.168.0.1.
I configured fortress' eth0 to have a DHCP assigned IP address, and eth1 to be 192.168.0.1.
So far, fortress can pull a valid IP from the gateway, and see the Internet just fine.
The problem is that I can't get fortress and lancelot to "see" each other through the LAN hub. When I ping lancelot from fortress, I see the light blinking on the hub, but I get 100% packet loss. The same goes for lancelot when I ping fortress... 100% packet loss, and I can see the light blinking on the hub. When the light is blinking for the machine that I'm pinging FROM, the light for the machine that I'm pinging TO does not blink in unison. I've tried cycling power on everything -- the hub, the gateway, and both machines, just to see if it was some kind of residual memory in the hardware.
When I run "ifconfig", everything looks as it should.
Why can't they see each other?
Thanks for any help, Steven
participants (2)
-
Anders Johansson -
Steven Hatfield