Topic: Client computer not able to wire connect, but connects fine wirelessly.

[turtle2472]

I'm really puzzled by this little challenge.  One of my systems is normally wirelessly connected to the network with it's IP statically assigned based on MAC in Hostnames and addresses.  no problem connecting wirelessly but fails to connect with ethernet connection.  The MAC for the ethernet connection is also established in the Hostnames and addresses.

It gets an IP address fine and it's even the correct subnet and IP i assigned.  I've changed the IP to be something totally different and unused just in case there was a conflict but nothing seems to be able to get this computer connected via ethernet.

My SME was originally installed as 7.1 and tonight I updated it to 7.4 thinking it would fix the issue.  It's been failing to connect to the ibays and internet for at least a month or so now.  I don't mind as much that it isn't working through the ethernet since it's normally wireless.  However, this really should be fixed and I don't know where to look now.

SME is running in Server Gateway.  Thanks for any help in figuring this out.  My first thought is that my MAC for wire connection has been blocked on my server somehow like an IP gets blocked when it floods a web server.  That's really what this is like, I get an IP but that's as far as it goes.

[electroman00]

I'm really puzzled by this little challenge.

My SME was originally installed as 7.1 and tonight I updated it to 7.4 thinking it would fix the issue.

Did you update 7.1 to 7.4 or did you update 7.1,7.2,7.3,7.4 ?
There were issues that needed to be resolved along the update path.

It's been failing to connect to the ibays and internet for at least a month or so now.

It's suggested to always resolve any existing issues or problems before you update/upgrade.

I don't mind as much that it isn't working through the ethernet since it's normally wireless.
However, this really should be fixed and I don't know where to look now.

Without any system and network configuration info it's going to be very difficult to diagnose and fix anything.

SME is running in Server Gateway.

Is SME on a Lan or DMZ of the firewall/router?

My first thought is that my MAC for wire connection has been blocked on my server somehow like an IP gets blocked when it floods a web server.  That's really what this is like, I get an IP but that's as far as it goes.

Not likely, seems more of a network config issue, however without config info it's impossible to tell.

To summarize:

Did you update 7.1 to 7.4 or did you update 7.1,7.2,7.3,7.4 ?
Is SME on a Lan or DMZ of the firewall/router?
Also is the wireless part of your modem?

[turtle2472]

Sorry for the lack of details in my original post.

Yes, I have run updates along the way and at least twice a week check for updates and install them when they arrive.

My network is pretty tough to quickly explain.

Code: [Select]

HSI - Linksys RV042 - SME Server - Linksys SD2008 - Linksys SD2008 - MB
                     `- WRT54G                     `- AP Express    \- G4 Mini Server
                                                                     \- C2D Mini
                                                                      `- WRT54G The first WRT54G is for a public access WiFi hotspot.  The RV042 controls it and I've put the SME Server in the DMZ.  RV042's network is 192.168.2.1 and SME's is 192.168.4.1.  This map isn't showing everything on my network but gives the overall idea.

RV042 is the DHCP controller with 50 assignable addresses.  The WRT54G and SME are statically assigned IP addresses.  SME is the DHCP controller for the network on this side.  The second WRT54G and Airport Express are both in bridge mode to prevent DHCP conflicts.  All IP addresses are statically assigned in Hostnames and addresses.  There is a block of 25 IPs that are open for dynamic assignment for when I wire connect systems for testing/servicing my client's computers.  All access points on SME's side are configured with whitelist only access.

The MB on the right and top is the MacBook in question. There is another MB that's only wirelessly connecting via the inside WRT54G.  I also have 4 PCs that are wire connected but not in the map above.  All of them are behind SME.  Oh, and there's a PS3 wire connected and a Wii wirelessly connected to the shared WRT54G.

[electroman00]

Any chance the wrt54g's are on the same channel?

wrt54g stock firmware?

[electroman00]

Hey scratch the same channel that shouldn't matter.

Think I see the problem.

What if you disconnect the wii and reset the 54g and try the MB?

[electroman00]

turtle2472

Did you ever resolve this issue.
Also are you using the stock WRT54g firm?

[CharlieBrady]

no problem connecting wirelessly but fails to connect with ethernet connection.

What exactly do you mean by "fails to connect"?

[electroman00]

Usually means your not able to obtain an IP.

[turtle2472]

turtle2472

Did you ever resolve this issue.
Also are you using the stock WRT54g firm?

I did get it resolved but I'm sure it was because I replaced the WRT54G and my Airport Express with a Time Capsule and also upgraded my server to a new Dell and did a clean install.  So I did, but not really.  The original issue was never resolved, only worked around.

Hey, it all works now.   Thanks for checking back though!

What exactly do you mean by "fails to connect"?

It got a valid IP address, but failed to connect to the server to file sharing or to the internet through the server.

[electroman00]

Good to hear.
If you still have hardware wrt54g you might want to try the DD-WRT firmware.
Much better then the stock firm.

[CharlieBrady]

It got a valid IP address, but failed to connect to the server to file sharing ...

That would be because the IP address is not on a local network, or there is not connectivity between the IP address and the local network of the SME server.

or to the internet through the server.

That would be because the default GW of the client computer does not point back through the SME server, or there is not connectvity between the client compter and the SME server.

I've put the SME Server in the DMZ.

That's probably the root of your problems. SME server is not designed to operate in a DMZ.

[electroman00]

That's probably the root of your problems. SME server is not designed to operate in a DMZ.

So to be clear, sme server should not be deployed on a DMZ, so that leaves only a Lan or direct to a Wan.

Is that correct?

So what is it about SME's design that makes it unlike all other servers, not operate on a DMZ.

The reason I ask is because, if one searches the net, everyone recommends that servers be deployed on the DMZ not on a Lan.

[cactus]

So what is it about SME's design that makes it unlike all other servers, not operate on a DMZ.

AFAIK it can perfeclty run in a DMZ, but configured as server-only, not as gateway.

[electroman00]

it can perfeclty run in a DMZ Server-only or Gateway.

Preference Gateway

[cactus]

Preference Gateway

Why? AFAIK computers in a DMZ have only one connection to the net, see also the illustrations in http://en.wikipedia.org/wiki/Demilitarized_zone_(computing)