Oddly enough, my first reply didn't make it. Here it is again: > Some random thoughts: > > - Ping is ICMP traffic, not UDP, so that doesn't prove UDP is working.
Sorry, I knew that. Brain fart. > - I would get tcpdump or wireshark loaded on that box, and see if it shows > some attempt at traffic. If possible, do the same on the firewall (BTW, what > kind of firewall are you running? Your options for troubleshooting might > increase if we know what kind it is) The firewall is an older Netgear ProSafe VPN Frewall FVS114. > - Does it have IPv6 enabled? That might also be an issue. Yes it does. > - Is the Default Gateway correct? Yes it is. > - Is your domain subnetted or use multiple routers? If so, try moving the > box to another spot on the network. That's a good idea. I have a classic choke/bastion firewall setup, and there's a different domain in the DMZ. I will ask them to plug it into the DMZ and see if it gets out. I was also thinking it might be the switch, which I don't administer. They put in a new fancy high speed switch in the building, and I think can do some filtering itself. I'll ask them to swap ports on the switch and see what happens. > - Try a different NIC. I'll talk to the hardware guys about doing that. > - Can it do DNS resolutions? try "dig www.google.com" or "dig www.yahoo.com". > If it can't resolve those dns names, there is no hope of it working. you can > also try opening a website by IP. You already listed google's address. Yes, though it does not run named itself, but talks to a local nameserver. > > Just some thoughts, take them for what they are worth. I am a Network > Security guy and deal with firewall troubleshooting alot. It's tough trying > to diagnose this problem cause I am not there, but I will do what I can. I > am sure others here will help as well. > > Jeremiah E. Bess > Network Ninja, Penguin Geek, Father of four > Hey! Thanks for the ideas. I'll keep you informed. billo On Aug 29, 10:25 am, "Jeremiah Bess" <[EMAIL PROTECTED]> wrote: > what is the firewall you are running on the network? > > Jeremiah E. Bess > Network Ninja, Penguin Geek, Father of four > > On Fri, Aug 29, 2008 at 7:52 AM, billo <[EMAIL PROTECTED]> wrote: > > > My previous reply doesn't seem to have made it here yet. I'll repost > > it if necessary, but here's some more info. The tcpdump looks OK. > > Here's a telnet attempt: > > > 08:45:27.779256 myplace.com.32849 > otherplace.com.telnet: SWE [tcp > > sum ok] 3162274411:3162274411(0) win 5840 <mss 1460,sackOK,timestamp > > 73038709 0,nop,wscale 0> (DF) [tos 0x10] (ttl 64, id 286, len 60) > > 08:45:30.781473 myplace.com.32849 > otherplace.com.telnet: SWE [tcp > > sum ok] 3162274411:3162274411(0) win 5840 <mss 1460,sackOK,timestamp > > 73041782 0,nop,wscale 0> (DF) [tos 0x10] (ttl 64, id 287, len 60) > > ... > > and on and on > > > I don't know how to check to make sure it's hitting the gateway, but I > > do know that it is set correctly. netstat -rn shows the correct > > gateway, and /etc/sysconfig/network-scripts/ifcfg-eth0 is: > > > DEVICE=eth0 > > ONBOOT=yes > > BOOTPROTO=none > > TYPE=Ethernet > > NETMASK=255.255.255.0 > > IPADDR=10.20.30.37 > > USERCTL=no > > PEERDNS=yes > > GATEWAY=10.20.30.1 <---- correct ! > > DOMAIN=myplace.com > > > netstat -rn shows: > > > Kernel IP routing table > > Destination Gateway Genmask Flags MSS Window > > irtt Iface > > 10.20.30.0 0.0.0.0 255.255.255.0 U 0 0 > > 0 eth0 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > > 0 eth0 > > 0.0.0.0 10.20.30.1 0.0.0.0 UG 0 0 > > 0 eth0 > > > Both of these are identical to that in machines that work (with the > > exception of the box ip address, of course). > > > billo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [EMAIL PROTECTED] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
